Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 729
  • Last Modified:

SBS2011 migration is failing, looking for some feedback

I ran a Windows SBS2003 to SBS2011 migration today.  I received an error stating that:
Active Directory replication is taking longer than expected.  You can choose whether to continue waiting.

If you choose not to wait, the migration may fail.  Unless you are sure that replication is working correctly, it is recommended that you continue waiting.  Do you want to wait for the replication to finish? (Yes/No).

I checked the FSMO roles and they are all pointing to the destination server, however the destination server is NOT setup as a GC, which I believe is a requirement of the migration.

Looking for some direction on this.
0
creativenetworks
Asked:
creativenetworks
2 Solutions
 
Em ManCommented:
Found this, not sure if you have read it already.:


Key Error or Exception from the Log:
No error in the log (yet), but you receive the following prompt:

Active Directory replication is taking longer than expected. You can choose whether to continue waiting.

If you choose not to wait, the migration may fail. Unless you are sure that replication is working correctly, it is recommended that you continue waiting.

Do you want to wait for the replication to finish? (Yes/No)


Most Common Cause:
You will only get this dialog after we have waited for 25 minutes and the new server has not been able to properly contact the source DC to initialize the file replication service (FRS), this is preventing the new server from becoming a domain controller. Clicking No on this dialog will almost certainly mean a failed setup. The source server is most likely in journal wrap or having FRS issues.


Resolution Summary:
Correct the FRS issues on the source server, do not reboot the new server or close down the setup, leave the popup dialog open, once the FRS issues are corrected on the source server, you can open a command prompt on the new server by using Shift-F10 and restart the Netlogon and FRS services, then confirm that SYSVOL and NETLOGON are shared on the new server by using NET SHARE, only then you should click Yes to continue waiting, after 5 minutes the setup will go on.
0
 
creativenetworksAuthor Commented:
Freakin brilliant response!  Any direction on how to fix the FRS issues would be appreciated.

Thanks again!
0
 
Em ManCommented:
Have you check the internet DNS settings on the source server see if its using the correct settings?

also what's on your Events Log?

What is the output when you run DCDIAG?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Em ManCommented:
*Internal DNS
0
 
creativenetworksAuthor Commented:
Just ran the following solution:
On the source server:
Load regedit and change the following key:
HK_LM\System\CurrentControlSet\Services\NTFrs\Parameters\Backup\Restore\Process at Startup – change the BurFlags key to decimal 4.

On the destination server:
Press CTRL-ALT-DELETE, load task manager, then click on file select run and enter regedit to change the following keys
HK_LM\System\CurrentControlSet\Services\NTFrs\Parameters\Backup\Restore\Process at Startup – change the BurFlags key to decimal 2
HK_LM\System\CurrentControlSet\Services\Netlogon\Parameters – change the SysVolReady key to decimal 1.

Next restart stop and start the File Replication service on both the source and destination machines. (On the destination machine hit CTRL-ALT-DELETE, click on file, select run and enter services.msc)

Will report back.
0
 
creativenetworksAuthor Commented:
System completed that portion and rebooted.  Now 'seems' to be hung on the "Applying computer settings' screen.  Has been there for about 20 min.
0
 
creativenetworksAuthor Commented:
Just found out the server has completed and is ready for migration.  In the past, my experience has been that when transferring mailboxes, you had to remove the send/receive connectors on the source server.  However many documents I have read state this is no longer needed and you can migrate the mailboxes during regular working hours.

Does anyone know if this is true?
0
 
creativenetworksAuthor Commented:
The error was based on an apparent addressing issue.  Two nic's were Teamed and were using a DNS Servers address on response.  I removed the team, disabled one of the Nic's and used the proper static.  Reset DNS to loopback and migration continued properly.

Checked AD and both servers were communicating properly.  All issues resolved.
0
 
creativenetworksAuthor Commented:
excellent feedback
0
 
kgjohnsonCommented:
this worked for me as we

Key Error or Exception from the Log:
No error in the log (yet), but you receive the following prompt:

Active Directory replication is taking longer than expected. You can choose whether to continue waiting.

If you choose not to wait, the migration may fail. Unless you are sure that replication is working correctly, it is recommended that you continue waiting.

Do you want to wait for the replication to finish? (Yes/No)


Most Common Cause:
You will only get this dialog after we have waited for 25 minutes and the new server has not been able to properly contact the source DC to initialize the file replication service (FRS), this is preventing the new server from becoming a domain controller. Clicking No on this dialog will almost certainly mean a failed setup. The source server is most likely in journal wrap or having FRS issues.


Resolution Summary:
Correct the FRS issues on the source server, do not reboot the new server or close down the setup, leave the popup dialog open, once the FRS issues are corrected on the source server, you can open a command prompt on the new server by using Shift-F10 and restart the Netlogon and FRS services, then confirm that SYSVOL and NETLOGON are shared on the new server by using NET SHARE, only then you should click Yes to continue waiting, after 5 minutes the setup will go on.
0
 
analyticalthinkerCommented:
The registry key changes worked for me, also - migrating to SBS 2008 from SBS 2003.  Great info.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now