Migrating SBS to new hardware

Tech-Archive recommends: Speed Up your PC by fixing your registry

I was following the article "Migrating Windows Small Business Server 2003 to
New Hardware"

http://technet2.microsoft.com/WindowsServerSolutions/SBS/en/library/4082d695-2075-4ca0-8af8-99fd04b78b2d1033.mspx?mfr=true

and along the way my destination server stopped booting. It would get stuck
at "applying personal settings" Same thing under safe mode with networking,
desktop never appeared. In my haste I decided to scrap my new destination
server installation and reload Windows from scratch and start over.
Problem now is I had already promoted that first destination server as a
global catalog server and transfered the operations master roles.
So now when I got to that point on my second run through I get "ERROR" where
my source server should be and below that it says "the current operations
master is offline. this role cannot be transfered." in the Operations Masters
dialog.
If I click change I get "the current FSMO cannot be contacted" etc and
clicking help from there talks about siezing the role.
So my question is this the only way to procede? This is the help text I get;

"The domain controller currently acting as the RID master is not available.
This could be caused by network problems or by a failure of the RID master
computer.

There should be a RID master in each domain. Temporary unavailability of a
RID master is not visible to network users. Seizing the RID master role is a
drastic step that should be considered only if the current RID master will
never be available again.

Before proceeding with the role seizure, you must permanently disconnect the
current RID master from the network.

Important

After the RID master role has been seized, the boot drive for the original
RID master must be completely reformatted and the operating system
reinstalled before that computer can be returned to the network. "


This is ok with me because that first destination server is already formatted.
Is this the best way to go or should I try something else? Can't I just
revert my original source server to being the operations master and transfer
it to my new destination server somehow?




.

Relevant Pages

  • Re: Migrating SBS to new hardware
    ... > I was following the article "Migrating Windows Small Business Server ... > There should be a RID master in each domain. ... > RID master is not visible to network users. ... > After the RID master role has been seized, the boot drive for the> original ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating SBS to new hardware
    ... and along the way my destination server stopped booting. ... This could be caused by network problems or by a failure of the RID master ... RID master is not visible to network users. ... After the RID master role has been seized, the boot drive for the original ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating SBS to new hardware
    ... For the record, I know the MS method involves transferring FSMO and the swing involves offline seizing, but my point is problems can still occur whenever you are messing with domain roles, online or off. ... Since his problem occurred during the role-transfer step, which even in a swing migration still has to happen, the problem would still exist. ... Had you spent the money and gotten the swing migration kit, you're old server would still be there until you were ready to cut over. ... "The domain controller currently acting as the RID master is not available. ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating SBS to new hardware
    ... There is extra legwork to make them play nicely with a swing migration (or there was when I last bought the documentation. ... And this will become even more common with SBS 2008 premium actively using a second server. ... TempDC is then told to sieze the FSMO roles, while disconnected from OriginSBS, leaving the FSMO roles intact on OriginSBS. ... "The domain controller currently acting as the RID master is not available. ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating SBS to new hardware
    ... and along the way my destination server stopped booting. ... This could be caused by network problems or by a failure of the RID master ... RID master is not visible to network users. ... After the RID master role has been seized, the boot drive for the original ...
    (microsoft.public.windows.server.sbs)