General discussion

Locked

Upgrade Server from NT to SBS 2000

By robertp ·
I have a small network (approx 28 workstations). I have one server running NT 4.0 Server sp6a and Exchange 5.5 sp3 and configured as a PDC. I will be upgrading both the server software (sbs 2000) and the Box. I need the new box to be the PDC and theold box to be the BDC. I am looking for some hints, tricks, and advice of things to be careful of from some of people who have some experience with this. Should I set up the new box seperately first, then demote the current PDC? What is the best wayto get the mailboxes from Exchange 5.5 to Exchange 2000? Any advice would appreciated

This conversation is currently closed to new comments.

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

All Comments

Collapse -

Upgrade Server from NT to SBS 2000

by timwalsh In reply to Upgrade Server from NT to ...

Some issues you will have to work with:

1. There is no upgrade path from NT4 Server to SBS 2000. If you want to migrate your users, you will need to upgrade to Win2K Server (and Active Directory (AD)) and then upgrade to SBS2K. Note 1: Since SBS 2000 is based on Win2K (and AD) there is no PDC/BDC relationship as there is with NT4. Note 2: Since you will have to upgrade to Win2K before you can upgrade to SBS 2000, you will have to follow the normal rules for migrating from an NT4 domainto a Win2K domain

2. Since Exchange 2000 server as included with SBS cannot be a part of a larger Exchange organization, the easiest way to move mailboxes is to move individual user's saved mail, contacts, etc., from the their Exchange mailbox to individual Personal Folders Files (.pst files). Once you get Exchange 2000 setup and functioning, you can then move the mailbox info back into the Exchange mailboxes from the user's .pst files. This is the method recommended by Microsoft. This should be done BEFORE any other steps are taken to upgrade/install SBS.

Problem: With the upgrade path you will need to follow, and your wanting to put SBS on a new server, you would need to accomplish the following steps:
1a. Install Win2K on your current PDC creating a Win2K AD Domain Controller(DC); Install Win2K on your new server; Run dcpromo (which installs AD) to create a second Win2K DC; Transfer all FSMO roles from your first DC to the new DC; Install SBS on the new server.
or,
1b. Install NT4 on your new server as a BDC; Synchronize the PDC with the BDC; Demote your present PDC to BDC (which will of course promote your new server to PDC; Install Win2K on your new PDC creating a Win2K AD Domain Controller (DC); Install SBS on the new server.

As you can see, this will be very time intensive (and of course have many potential areas for problems).
(continued)

Collapse -

Upgrade Server from NT to SBS 2000

by timwalsh In reply to Upgrade Server from NT to ...

Recommendation: Only you can make this determination, but in my mind, it would be easier (and less time consuming) to simply install SBS clean on the new server; Recreate all your user accounts on the SBS server; reconnect the client workstations to the new domain; To connect the old box as either an additional AD DC or as an NT4 BDC, do a fresh install of the appropriate OS once you have moved data to the new SBS server.

Hope this helps.

Collapse -

Upgrade Server from NT to SBS 2000

by robertp In reply to Upgrade Server from NT to ...

Poster rated this answer

Collapse -

Upgrade Server from NT to SBS 2000

by curlergirl In reply to Upgrade Server from NT to ...

Ok - first of all in a Win2K domain (even SBS), there is no such thing as a PDC and BDC - just DC's. Although there are some differences in roles between the first controller in a new forest/domain and the others, these are negligible in a small network such as yours. So, what you want to do is, first, upgrade your current PDC to Win2K and run dcpromo to install AD. This is the recommended migration path from WinNT4 Server to SBS 2000. This will migrate all of your user and computer accounts, etc., and this machine will be the first DC in your forest. Normally, you would then proceed to install SBS on the same box. However, because you want your new box to be the SBS 2000 server, you can take your new box and install SBS 2000 on it fresh and join the same domain, making it a second DC in the same forest. SBS 2000 is a slightly different animal from SBS 4.5, in that it can co-exist with other DCs in the same domain, whereas SBS 4.5 HAD to be the PDC of the domain and other servers could only be member servers, no other domain controllers allowed. The only thing you will need to be careful about is your Exchange migration. Here are a few good articles on this that will help you decide how to migrate from your Exchange 5.5 toExchange 2000 - Q316886 and Q324218. READ THESE ARTICLES CAREFULLY before you even start your SBS 2000 install, because it will affect how you go about installing the Exchange 2K component of SBS. You should be able to do a direct migration instead of the export to .pst and re-import deal, which is OK but a little clumsy. You also might want to go to this web site:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sbs/deploy (remember to remove any spaces)

This is a wealth of info on how to deploy SBS 2000 and covers lots of different possibilities. Hope this helps!

Collapse -

Upgrade Server from NT to SBS 2000

by robertp In reply to Upgrade Server from NT to ...

Poster rated this answer

Collapse -

Upgrade Server from NT to SBS 2000

by robertp In reply to Upgrade Server from NT to ...

This question was closed by the author

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

Related Discussions

Related Forums