Ansar
Guest
|
Posted:
Fri Jan 21, 2005 12:11 am Post subject:
Difficulty with Upgrade NT4 to MS Win Business Server 2003 |
|
|
Hi all,
I have the following scenario.
We have two servers and a workstation acting as a server
1) Domain Controller-NT4
2) Backup/File Server - Windows Server 2000
3)A workstation which acts as a server with NT4, Exchange Server 5.5 and it
is a primary server.
Now, I want to buy a server with MS Small Business OS 2003. The dilema I am
facing is as follows:
I want the new server to be the primary domain controller and be attached to
the domain. Also, I want the current Primary Domain Controller on NT4 to
become a Backup Domain Controller-BDC. How can I perform the procedure
without a headache and still have the same domain.
Hence, I want to know how can PDC be turned on BDC on NT4. Then, do I plug
the server on the network -in the domain we have and install the OS with the
purpose in building the server as PDC with MS Business Server 2003
Regards,
Ansar |
|
Frances [MSFT]
Guest
|
Posted:
Fri Jan 21, 2005 4:22 pm Post subject:
RE: Difficulty with Upgrade NT4 to MS Win Business Server 20 |
|
|
Hello Ansar,
Thanks for your post.
Unfortunately, it is impossible to make a MS Business Server 2003 PDC in NT
domain.
The way to demote a PDC is to promote a Windows NT 4.0 BDC to the PDC. The
former PDC will be automatically demoted to BDC.
I am not clear about the workstation you mentioned which acts as a server
with NT4, Exchange Server 5.5. Do you mean it is a stand-alone server, not
a BDC? If it is a BDC, you can promote it to demote the current PDC.
To achieve your goal to have a MS Small Business OS 2003 as DC, you can
have the following two methods. They are listed for your reference.
Method 1: Upgrade to SBS2003 domain.
======================================
In an NT domain, you can not have a SBS 2003 server even as a member
server. However, it will take some time to upgrade the domain. If you want
to upgrade to SBS2003 domain and keep your original domain name, please
follow the steps below:
1. Install the new server box with Windows NT on it and join it into the
domain. Make the new box the PDC. Disconnect the old server.
2. Upgrade it to Windows 2000 or 2003.
326209 How To Upgrade a Windows NT 4.0-Based PDC to a Windows Server
2003-Based
<http://support.microsoft.com/?id=326209>
3. Upgrade from Windows 2000 or 2003 to SBS 2003.
<http://www.microsoft.com/technet/prodtechnol/sbs/2003/plan/gsg/chptr3c.mspx
Method 2: Migrate to new SBS2003 domain.
==================================================
Using ADMT, you will have a different domain name and server name. You need
not disconnect the old clients from the old domain. It has a computer
migration wizard to help you move the clients from the old domain (NT) to
the new domain in SBS Server 2003. The user profiles will be kept during
this migration. Please refer to the following article regarding NT 4 to SBS
2003 migration:
Migrating from Small Business Server 4.5 or Windows NT 4.0 Server to
Windows Small Business Server 2003
http://go.microsoft.com/fwlink/?LinkId=16415
Upgrading to Windows Small Business Server 2003
http://www.microsoft.com/WindowsServer2003/sbs/upgrade/default.mspx
Please power on the clients and log out any users in order to prevent any
user profile from being locked. As this process may involve a lot of
process to transfer the data to the new domain, please make sure to
completely back up the critical data in your old domain prior to migration.
Also, it is better to perform some test in a test environment isolated from
your network for test. This will help you migrate the domain and data
smoothly.
If you have any further questions don't hesitate to get in touch!
Best regards,
Frances He
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights. |
|