Skip to main content

DFSR Migration for RODC is stuck

By

During a DFSR sysvol migration on Windows Server 2008, problems can occur with the migration of Read Only Domain Controllers.

See the image below.

image

The RODC is stuck trying to move to the Prepared state.  First go to the RODC and type Repadmin /SyncAll /AeD.

 

On the PDC Emulator, run dfsrmig /GetMigrationState.

If the migration completed, continue on.  If not type dfsrmig /CreateGlobalObjects. This will manually create the global objects for DFS replication.

On the PDC Emulator, run dfsrmig /GetMigrationState. You should be ready to move on to the next step in the migration process.

Labels

Labels:

Comments

AlexG said…
RODC in perimeter network was stuck as mentioned, however the repadmin and dfsrmig commands did not get things moving. Turned out to be an issue with the firewall protecting the RODC. Allowed full access between the RODC in the perimeter network and all other domain controllers, and the migration moved right along. Saw a lot of activity over ports 49204, 49155, 49156, etc. after I opened things up. Planning to change the firewall back after this finishes, and try to restrict DFSR replication traffic to specific ports only.
February 16, 2012 at 7:07 AM
Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more