I came across this error the other week while I was running a small business server 2003 to 2008. I thought I would share with you what I did to resolve it.
While running through ‘expanding and installing files’ – the migration wizard gets stuck with the following error message.
“Active Directory replication is taking longer than expected. You can choose whether to continue waiting’
Of course, this obviously means you have AD problem from your source server. Digging a little deeper into this, I looked into the SBS install log. This is located in the programs files folder, inside of the small business server folder. – (if you want to access this, cntrl + alt + delete, task manager and then run – head to the land of explorer).
I found out the culprit.
Setup: DsGetDcName returned: 0
Setup: DsGetDcName returned name: sbs03.domain.local
Setup: Expected name: sbs08.domain.local
Task: There are 0 pending replication operations.
Setup: Attempting LDAP bind.
Setup: Bind successful
Task: Waiting for replication to finish
I checked to make sure the services needed are running. I found this bit from M$. (this is on the source server)
- Computer Browser
- Remote Procedure Call (RPC)
- File Replication Service
after checking this, still no go. I decided to have a look further and discovered that the BurFlags registry key for FPS needed to be changed – and they’re operating incorrectly. This should normally be done by the migration wizard apparently!
Have a look at the following reg key on your source server and make sure it is decimal 4.
HK_LMSystemCurrentControlSetServicesNTFrsParametersBackupRestoreProcess at Startup - Change the BurFlags key to decimal 4
Now on the destination server, head into reg edit. (if you want to access this, cntrl + alt + delete, task manager and then run )
HK_LMSystemCurrentControlSetServicesNTFrsParametersBackupRestoreProcess at Startup – Change the BurFlags key to decimal 2
HK_LMSystemCurrentControlSetServicesNetlogonParameters – change the SysVolReady - Change the key to decimal 1.
Now restart FPS on both source and destination servers. – (services.msc on the destination server from run).
Your migration should then run as normal.