• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1989
  • Last Modified:

SBS 2008 Migration - Replication Problem

I am migration my SBS 2003 server to SBS 2008. I get a message saying "Active Directory replication is taking longer than expected. ..." I pulled up the logs from C:\Program Files\Windows Small Business Server and I found that the section below keeps being repeated in the logs.

This is very confusing since it seems that the BIND is going well, but I still get the replication error every time I select "Yes" to wait longer.

Any ideas?

LOG Snippet:

Setup: DsGetDcName returned: 0
Setup: DsGetDcName returned name: sbs03.mydomain.local
Setup: Expected name: sbs08.mydomain.local
Task:       There are 0 pending replication operations.
Setup:       Attempting LDAP bind.
Setup:       Bind successful
Task: Waiting for replication to finish
0
Rickggoalie3
Asked:
Rickggoalie3
1 Solution
 
Alan HardistyCo-OwnerCommented:
Which migration guide are you following?  I use this one which other EE Experts have used successfully:
http://blog.mpecsinc.ca/2009/06/sbs-2003-to-sbs-2008-migration-guide.html
Have you checked the health of your SBS 2003 server before you started the migration?
Did you run the Microsoft IT Environment Health Scanner and the SBS Best Practises Analyzer too?
0
 
Rickggoalie3Author Commented:
I'm using the Microsoft authorized migration guide:
http://www.microsoft.com/downloads/details.aspx?FamilyID=52b7ea63-78af-4a96-811e-284f5c1de13b&displaylang=en

Admittedly, I did neglect to run the SBS Best Practice Analyzer prior to migration.

Any ideas on what causes this error?
0
 
Alan HardistyCo-OwnerCommented:
To be honest, I started with the MS guide and then abandoned it in favour of the one I posted.

I also faced the exact same errors and never solved them in the timescale I had.  I allowed 3 days for the migration and spent 6 overall, giving up on the migration half-way through on favour of a new build.

Essentially the problem is almost certainly down to AD problems on the SBS 03 server.

Have you run all the dcdiag checks etc mentioned in the document I linked to and also checked your AD replication?

Have you got the netlogon and sysvol shares setup and working?

If they are not there, you will have AD replication problems.  But do not manually create them.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
Rickggoalie3Author Commented:
dcdiag comes up all passed. netlogon and sysvol share seem to be working fine.
0
 
Alan HardistyCo-OwnerCommented:
Have you run ALL the pre migration checks outlined in the article I posted?  If not, please do so and report back.

You will have to start the SBS08 server build again and will have to undo the AD changes that the 08 partial migration has performed.

Do you have a pre migration AD backup?
0
 
Rickggoalie3Author Commented:
Resolved problem via my own research. For others having this problem, try this:

Quoted from
http://prezweezy.wordpress.com/2009/03/26/sbs-2008-migration-tips-tricks-and-troubleshooting/

"Before I tell you how to fix this, if you are ever going to do a migration, I highly recommend you find your way to Jeff Middletons site SBSMigration and order his book.  Even if you are going to do the Microsoft migration every time, you can still learn most about how migrations work and whats going on from his book than you will anywhere else.  It is a great resource to have and reading through it will provide you with a lot of good troubleshooting ideas and places to start when it goes wrong.
This one happens sometimes.  You will install, the AnswerFile gets picked up, and after a few reboots you get a message stating that the AD replication is taking longer than normal, do you want to wait for replication?  You have two problems now.  First, the Source isnt replicating properly and you need to fix that problem, and secondly, many times the Destination server has stopped trying to replicate because of the failure.
Source server:
Check that these services are running, this is the most common cause of failure to replicate:
Computer Browser
File Replication Service
Remote Procedure Call (RPC) (and I always start the Locator too, dont know if it helps but I do)
Server
Workstation
Disable Firewall!  If you dont make a habit of doing so already, the Firewall can really muck up a migration.  You probably have a better firewall in your AV program already anyway.

So now you have the problem figured out, lets get the two to start talking again.  There is one registry key on the Source, and two on the Destination which need to be fixed.
Source:
HK_LM\System\CurrentControlSet\Services\NTFrs\Parameters\Backup/Restore\Process at Startup
Change the BurFlags key to D4 on the old server
Dest:
Obviously there is no run, so you need to bring up either Task Manager or a command prompt.  I know there is another hotkey for CMD but I dont remember what it is most of the time, so I just use CTRL+SHIFT+ESC, which brings up Task Manager.  File>New Task will get you a run so you can open up the registry. Now change the same BurFlags key to D2 on the new server and also go find the key HK_LM\System\CurrentControlSet\Services\Netlogon\Parameters and make sure the SysvolReady key says 1, if not change it.  Now stop the NTFrs service on both servers, and start the Source first, then the Destination, and on the Destination server click Yes to wait for the AD replication.  If it worked, you should see almost immediate results."
0
 
Alan HardistyCo-OwnerCommented:
Well done - I wish I had found that 3 months ago!
Duly bookmarked in case I ever come up against that one again.
0
 
axismicroCommented:
I ran into the same issue and this worked perfectly.. Thank you!!
0
 
keytechausCommented:
Rickggoalie3, thank you very much for your post. I've spent hours and hours trying to fix this and this is the only post that has helped.
0
 
michaellhixCommented:
Dude, you rock.  I wish everyone would actually post in detail like that when they figure it out on their own.  Thanx!!
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

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