Skip to main content

Windows - Set Logon Server

How To change Logon server Name through Command Line:

echo %logonserver%
set  logonserver=\\server1

set logonserver

 open Command Prompt
*******************************************************
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\user>echo %logonserver%
\\ServerName1

C:\Users\user>set logonserver
LOGONSERVER=\\ServerName1

C:\Users\user>set logonserver=\\ServerName2

C:\Users\user>set logonserver
LOGONSERVER=\\ServerName2

C:\Users\user> echo %logonserver%
\\ServerName2

 

It is likely that DC2 is running your PDC Emulator role, which is why those messages are appearing on DC1.

Basically, what's happened is that the domain has reached a time period where it is no longer feasible to reconcile/merge all the USN (Update Sequence Numbers - i.e. they denote the versioning/changes on all of your AD objects) with the other DC, because it has been unavailable for replication for so long.

Here's the first few steps on TechNet: 

Technet: Forcing the Removal of a Domain Controller

To complete this task, perform the following procedures:

  1. Identify Replication Partners . Use this procedure to identify a domain controller that is a replication partner of the domain controller that you are removing. Identify a replication partner in the same site, if possible. You will connect to this domain controller when you clean up server metadata.

  2. Force Domain Controller Removal

  3. Clean Up Server Metadata

Then, you'll need to seize FSMO roles:

Petri: Seizing FSMO Roles  

After that, you can try to re-promote that DC.

Ensure that on DC1:

  • Primary DNS IP on NIC is pointing to DC2

  • Secondary DNS IP on NIC is pointing to 127.0.0.1

Ensure that on DC2:

  • Primary DNS IP on NIC is pointing to DC1

  • Secondary DNS IP on NIC is pointing to 127.0.0.1

 

Any new objects (computer/user accounts) that appear on DC1 and not DC2 will need to be recreated once you've got your replication back in order (or you could recreate them on DC2...either way, they'll need to be recreated).  Honestly, I would export a list of user and computer objects from your DC1 that were created after the date of last replication and then go from there.  There are various scripts out there that can do this.

Back to top