Forum Discussion

MVP

Apr 16, 2021

Solved

Server 2016 - Publisher Unknown - Certificate Issues - KB5000803

Hi Everyone, Since the release of KB5000803/KB5000808, we have had our fair share of client issues, mostly pertaining to printers, however one of our Windows 2016 servers seems to be suffering fr...

windows server

Dave Patrick
Apr 16, 2021
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.

David_Bradette

MVP

Apr 16, 2021

Hi Dave,

Thanks for your response. We are currently contemplating this option as well.

Regards,

David

Dave Patrick

MVP

Apr 16, 2021

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.

David_Bradette
MVP
Apr 16, 2021
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,

David
- Dave Patrick
  MVP
  Apr 16, 2021
  Sounds good, you're welcome. It is the much safer / cleaner / quicker solution.