We help IT Professionals succeed at work.

Multiple domain controllers running Windows Server 2003 for Small Business Server have been detected in your domain.  Migration Gone Bad

jtrabert asked
Our SBS 2003 has bene running fine but just under two weeks ago we tried to migrate to SBS 2008.  Through the migration process we ran into a snag and had to put it on hold until we figure out the problem.  Since then our SBS 2008 has been removed from the network but we are still receiving the message in the picture.  I know its from the migration process (and in theory we have 21 days to rectify it).  My question is, do we have to do a restore from two weeks ago (our last backup before the we tried migrating) or can we just transfer FSMO roles using this kb article http://support.microsoft.com/?id=255690  ? The message appears once a day.  I am aware that once the 21 day time limit is up our server will start shutting down, which of course we arer trying to avoid.  Thanks for your time and help Warning Message
Watch Question

Sr IT Support Engineer
Are you talking about trying to transfer the FSMO roles back to the SBS 2003 Server?

That particular article is for Server 2000.   Here is the one for Server 2003 http://support.microsoft.com/kb/324801/en-us   

It's not just a matter of the FSMO roles, you really need to restore system state, etc.

Ideally if this were me, I'd take snapshots of data folders, Exchange (maybe even export mailboxes to pst files), etc now  then restore backup to before the migration. and then restore and updated files that are needed, import emails and so forth

That's the only way to be truly sure.


Thanks for the reply.  Unfortunately SBS 2003 isnt my forte'.  By just restoring the System State prior to when we tried the migration what actually gets restored?  Will that affect exchange as well?  Or should I make a new backup just of exchange than restore the system state than restore the exchange backup?  Not worried about the user files because they are stored on a NAS.  
Cris HannaSr IT Support Engineer

Exchange Restores can be a pain ;-) so how you back it up I'll leave up to you.  I think Exmerge is easier if I need to bring something in but that's me.

I wouldn't expect System State restore to affect Exchange but people do get testy if email goes bye bye, so I prefer to be safe.
Distinguished Expert 2018
Since the SBS 2008 server is no longer in the picture, here is what I'd do:

1) SEIZE (not transfer, there is a difference) all FSMO roles on the 2003 server. That will resolve the immediate problem and stop the 21-day clock.

2) Use ntdsutil to remove any references to the SBS 2008 server. More about that is documented here: http://support.microsoft.com/kb/216498
Use the metadata/ntdsutil method documented.

3) Download and run the IT Health Scanner and resolve any outstanding issues with AD.

4) Download and run the SBS Best Practices Analyzer (BPA) and resolve any outstanding issues there.

At this point, you should have a completely healthy SBS server with NO risk of data loss or forcing you to revert to a previous backup (which would effectively be data loss) and, even better, you now know your infrastructure is health and are in a better position to re-attempt the migration in the future.
Distinguished Expert 2018

As an aside, (hence the separate comment), to prevent this from re-occuring in the future, I recommend picking up a "Swing Migration" kit. Jeff Middleton is an SBS MVP and has developed a method for migrating that really is top-shelf and adds that extra layer of safety in the event that things do go sideways.


Wow thanks guys for all the advice, ill be heading back to work either tonight or tomorrow.  Ill try the solutions then and report back