New server wit previous domain name

B

bburks85

We recently had to replace a Windows Server 2011 with Windows Server 2019. This was done by building a new server rather than doing an upgrade. When building the new server, it was given the same computer name and domain as the previous server. We removed workstations from the domain and then added them back in top the domain. Now the network drives that are connected on the workstations using Group Policies don't always appear. Running gpupdate / force gives the error:

Computer policy could not be updated successfully. The following errors were encountered:

The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
User Policy could not be updated successfully. The following errors were encountered:

The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).

To diagnose the failure, review the event log or run GPRESULT /H GPReport.html from the command line to access information about Group Policy results.


What can we do to get these systems to communicate properly with the new domain controller?

Continue reading...
 
Back
Top Bottom