Re: Clean Install of SBS 2000 by Chad
Chad
Wed Jul 23 12:31:00 CDT 2003
Brent Hoover wrote:
>> -----Original Message-----
>> Hi Arthur -
>>
>> The only way to migrate your domain (maintain your SID) is to join
>> another
>
>
> So, if I am moving my SBS to a NEW box (not reinstalling
> on the same) is there an easier way? I have tried just
> backing up and restoring the system state, but that just
> kills the new box.
>
> Thanks
>
> --Brent Hoover
> Computer Weasel
> audioMIDI.com
Nope. As you've discovered, restoring the System State doesn't work because
doing so restores the registy, which includes references to your old
hardware which kills the new box. In order to maintain an AD domain in this
type of migration, you have to have another DC preserving the domain (SID &
SAM). SBS2k cannot natively join an existing domain, and you cannot have
more than one SBS on the same network. Therefore, your only option to
preserve the domain is to have a Win2k (or Win2k3) server as a DC. The way
I see it, you've got a few different options:
1) Use the method mentioned in my eariler post - grab a spare box and set
it up as a DC in your domain. Unplug the old SBS from the network, seize
the FSMO roles on the spare box. Load up plain Win2k on the new server,
join the domain & upgrade to SBS. Dcpromo the spare box down to a member
server, unplug & remove from AD. Restore Exchange / network shares etc. to
new server. The primary benefits of this method are that you not only
maintain your existing domain, but you're able to give your new server the
same name as your old server, so client drive mappings, scripts, etc.
continue to work without a hitch.
2) Pretty much the same as #1 above, except you don't use the spare box.
Just load up Win2k on the new server, join it to your domain & make it a DC.
Remove the old SBS, seize the FSMO roles and upgrade to SBS. Down-side is
that the new box cannot be named the same as the old server.
3) Go with a clean install / new domain. Just install SBS on the new
server. Restore Exchange / shares, etc. You'll have to recreate all of
your user accounts and if you have any NT / Win2k / XP clients, they'll have
to be joined to the new domain, and when that happens all new profiles will
be created - so you'll have to manually recover user profiles on each
machine as well.
4) Wait for SBS2003 which will allow you to join an existing domain
(including SBS2k). This will be similar to #2 above, just that it you don't
need a copy of Win2k and it is part of the scripted install . . .
--
Chad A Gross
Lerman's Law of Technology: Any technical problem can be overcome
given enough time and money. Corollary: You are never given enough
time or money.