General discussion

Locked

Migrating SBS 4.5 to new server -1of2

By PSX ·
My company recently purchased a Dual AthlonMP box to replace our current PDC. The problem now is how to safely and successfully migrate all users, data, and policies over to the new server.

The new server will replace the current PDC. There is also a BDC on our network and the data on the old PDC will not be erased.

The steps that I have taken on the old server(according to a guide provided my Microsoft-Q228980) are:
1)Backup Existing Server to tape using BackupExec.
2)Create Emergency Repair Disk (ERD)
3)Use Migrate User Wizard to export current user.
4)Go into Exchange Administrator and do a directory export. (this exports all mailboxes but not the data they contain).
***No need to back up RAS, DNS, HDCP, Fax service, MS SQL, and Web service***

On the new server, these items have been performed:
1)Complete installation of SBS 4.5 (all components installed, except for Fax server).
***Gave the new server the same name but different IP address and set it to control a different domain so that it won't conflict with the current PDC. I opted not to add the new server to the existing domain because it might cause problems or SBS will not allow two SBS servers running on the same license to function. Don't know if this is true but just to be safe, I went with a new domain. I figured that I can change it back to the original domain after everything is complete***
2)Migrate users from the users.txt (step 3 above) file to the new server.
***skipped restore of RAS, DNS, DHCP, Fax service, and web service***
3)Copied shares with permissions intact.
--------------------------------------------

[please see part 2of2]

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Migrating SBS 4.5 to new server -1of2

by PSX In reply to Migrating SBS 4.5 to new ...

[continued from part 1o2]

Steps that needs to be done:
- On the old server, stop Exchange services and back up (copy) all copies of priv.edb and pub.edb files and document their paths.
- On the old server, backup WINS database and document static mappings.
- Document shared printers and permissions on those printers.
- On the new server, remove Exchange. Restart, then re-install Exchange with Correct Organization name and Site name.
- Re-copy data in shares folders (as some users might be making changes to these data)
- Take down old server after all users leave. Make the swap, then change the domain name to the original domain name.
--------------------------------------------

I don't know if there are any flaws with the steps that I have outlined or if I am missing anything important. That is why I am decided to post this question on Tech Republic.

Feel free to add any comments, advice, or anything else that you think might help.

- Khai Vuong
khai@smseafood.com

Collapse -

Migrating SBS 4.5 to new server -1of2

by PSX In reply to Migrating SBS 4.5 to new ...

Point value changed by question poster.

Collapse -

Migrating SBS 4.5 to new server -1of2

by curlergirl In reply to Migrating SBS 4.5 to new ...

There is a great major flaw in your plans - you cannot change the domain name of a server once it is installed into a domain. You cannot simply "join" a new domain, you have to completely reinstall NT. There may be a way around this, but it involves a 3rd party (freeware) application that Microsoft does not support. I have used it successfully on standard NT servers, but never on an SBS server. Go to www.sysinternals.com and look for a utility called NewSID. This is a SID changer utility that is capable of synchronizing the SID of an NT domain controller with an existing domain, thus making it a member of the new domain. The only flaw I see with this is that SBS is configured so that it HAS to be the PDC in its own domain. Therefore, you may have a problem when you take your old PDC offline and the old BDC wants to become the PDC for the domain. If you have your new PDC all set up and ready, though, you may be able to bring it on line and synchronize the SID before the old BDCobjects. Remember again, this is NOT supported by Microsoft, so if it fails they won't be able to give you any help and you'll have to start all over again. As far as your users, security database, etc., since you have a BDC, you could simply disconnect your old PDC, leaving the BDC on-line, promote it to PDC, and then connect the new SBS server and install it as the PDC for the domain (which will automaticalliy demote the old BDC (now PDC) back to BDC), and it would synchronize itself to theBDC for all user info, etc. Then the rest of your plan would work - as far as your Exchange databases, and any other data, this could be restored from backup provided that you new server name is the same as your old server name. Hope this helps!

Collapse -

Migrating SBS 4.5 to new server -1of2

by curlergirl In reply to Migrating SBS 4.5 to new ...

PS Skip any backup/restore of your WINS database - this will recreate itself automatically when you bring the new WINS server online. The only thing you need is to document any static mappings that you will have to recreate on the new server.

Collapse -

Migrating SBS 4.5 to new server -1of2

by PSX In reply to Migrating SBS 4.5 to new ...

Poster rated this answer

Collapse -

Migrating SBS 4.5 to new server -1of2

by PSX In reply to Migrating SBS 4.5 to new ...

This question was closed by the author

Back to Windows Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums