Forum Discussion
Server 2016 - Publisher Unknown - Certificate Issues - KB5000803
Sounds good, quite simple solution.
I'd use dcdiag / repadmin tools to verify health `correcting all errors found` before starting `any` operations. Then stand up the new 2016, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
Fixing these one-offs are not even worth spending any time or trouble. I'd simply stand up a new one for replacement then decommission / demote the broken one.
Thanks for your response. We are currently contemplating this option as well.
Regards,
David
Sounds good, quite simple solution.
I'd use dcdiag / repadmin tools to verify health `correcting all errors found` before starting `any` operations. Then stand up the new 2016, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
- Hi Dave,
Thank you for the additions suggestions. We've discussed in internally, and will be proceeding with standing up a new system over the weekend.
Regards,
DavidSounds good, you're welcome. It is the much safer / cleaner / quicker solution.