Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Migrating User Accounts to new SBS 2k Server

Status
Not open for further replies.

InIT4theMoney

IS-IT--Management
Feb 6, 2003
22
GB
We currently run SBS 2000 on a fairly low-spec server
computer and are intending to replace the server computer
with a much more powerful machine, using entirely
different hardware but still using SBS 2000. What we are
unsure of is the best way to migrate all our user
accounts from one server to the other? Backing up the
System State from the old server then using Directory
Services Restore Mode on the new one will not work as
this also 'restores' registry settings relevant to the
old server into the new one and it then won't boot!

What is the best way to do this? Can anyone help?

Ian W
 
There are a number of tools MS provide for AD editing including moving users. Personally I would just re-create them as you can't have more than 50 - but if you want to move/copy I would have a hunt in Technet.
I also recommend the Win2k Server MCP Training Book. Covers this sort of thing in detail. I don't have it with me at the moment, but if you are having problems post back and I'll have it with me then.

Good Luck,




Steve.
 
SBS works a little differently with AD since there can only be the one FSMO DC.

If you are staying with SBS2000, you can use what is called the "spare box" method. Basically you load your new server with Windows2000 server and do not add the SBS components.

Join this new server to the SBS domain, and let AD replicate to it. While it is attached, you can also migrate any date files.

If you are using Exchange, EXMERGE the private mailboxes to PST files, and copy them to the new server.

At this point, disconnect the old server from the domain, and resume adding the SBS components to the new server. With Exchange, you then EXMERGE the PSTs into the new setup.


Plan B: Upgrade to SBS 2003. It allows you to run another SBS server in the domain for migration purposes for 14 days. Probably worth it the cost when you consider the steps involved above.
 
Thanks for the advice concerning the 'spare box' method. I think I'm doing something wrong here though. Loaded just the Win2k server element from our SBS-2000 disk1 and cancelled SBS setup before it started. Then ran DCPROMO (I assume this is how you meant me to join the box to the domain) and selected the 'additional domain controller' option. All then goes well until the 'Summary' dialog then I get an error message saying 'this product option is not available with the Small Business Server Edition of Windows'. The AD installation wizard then unceremoniously dumps me back to the desktop.

Am I just being dumb here or have I missed something?!!!

Ian W
 
Sorry for the delay in responding.

No, you're not missing anything. I forgot that method requires a non-SBS version of the Win2k server disk. I've got an MSDN sub, so I've always got one of those to use.

Another method would be to setup your new server on its own physical network - ie not on the same switch/hub as your present server. This will require you to manually recreate AD objects. You then move workstations from one network to another. If you have a workstation with enough cpacity, you can use it for the migration of data. Just copy data down from the current server to it, move it to the new network, and copy the data back up.

This was one of the big problems with SBS version before 2003 - the 2003 version now permits an additional SBS server to join for 14 days for the purposes of migration.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top