I’m splitting this entry into two deliberately, as there are two seperate batch files involved + it’ll become messy.
We’ve had a problem recently with our sites getting out of synchronisation + therefore being unable to replicate and I’ve been searching for the least disruptive/ dangerous fix so have come up with the following automated system. You’ll need this download from my public Windows folder:
- You will need to modify some of the configuration of the following batch files to match your Active Directory set-up; I haven’t had time to investigate whether I can create wildcard batch files that will pick up FQDNs etc, nor can I tell what other people’s servers are called.
- The contents of the "AD Replication" folder (http://cid-580b459491ef225f.skydrive.live.com/self.aspx/Useful%20Windows%20Downloads/Computers/AD%20Replication (psexec.exe is part of SysInternals suite- http://technet.microsoft.com/en-us/sysinternals/0e18b180-9b7a-4c49-8120-c47c5a693683.aspx; if you’re a Windows server administrator and haven’t used the SysInternals suite before then take a look- they’re brilliant Windows tools.)
- Copy the entire "AD Replication" folder to the netlogon share of a domain controller- preferably a stable one.
- There are two batch files in the above folder. The first one you need is "start.cmd" which takes two parameters: the first is a domain controller, the second is an old-style (NT4) username. So type in the path to the cmd file followed by the two parameters, like this:
- \\YourDomainController\FolderName\start.cmd DomainControllerYouWantToFix.YourDomain.dot.com YourDomain\AnyDomainAdminUser
- The path I’m using in the two batch files is \\DomainController\netlogon\ServerApps\NtfrsRep\ but these can easily be changed as long as you modify all the paths in both cmd files (otherwise this system will (a) not work and (b) could mess things up badly !)
- This cmd file start psexec with domain admin rights (a bit dangerous !) and runs a remote command line with drive Z: mapped to the path you put in above(\\YourDomainController\FolderName\) on the server you want to fix.
- Now read part two !