willson
asked on
Windows NT 4.0 server and Windows Server 2003.
Dear Experts,
I am having a windows NT 4.0 server running in my company and we bought a new server for windows server 2003.
I am thinking of doing a fresh server(windows server 2003) for the company. I would like to do testing on my new server 1st. How do i go about doing this so that i can easily replace the existing server? can i have "windows 2003 server" and Windows NT 4.0 server running at the same time? Conflicts?
For your advice pls.
I am having a windows NT 4.0 server running in my company and we bought a new server for windows server 2003.
I am thinking of doing a fresh server(windows server 2003) for the company. I would like to do testing on my new server 1st. How do i go about doing this so that i can easily replace the existing server? can i have "windows 2003 server" and Windows NT 4.0 server running at the same time? Conflicts?
For your advice pls.
ASKER
Hi leew,
But the thing is that my company has two servers. the primary which is running win nt 4.0 while they want to setup the new server to run on windows server 2003.
My job is to make sure that the windows server 2003 (new server) can be configured to replace the old win nt 4.0 as its having hell lot of problems that is why upgrading is not recommended in this phase.
How do u think i can proceed?
But the thing is that my company has two servers. the primary which is running win nt 4.0 while they want to setup the new server to run on windows server 2003.
My job is to make sure that the windows server 2003 (new server) can be configured to replace the old win nt 4.0 as its having hell lot of problems that is why upgrading is not recommended in this phase.
How do u think i can proceed?
willson,
> My job is to make sure that the windows server 2003 (new server) can
> be configured to replace the old win nt 4.0 as its having hell lot of
> problems that is why upgrading is not recommended in this phase.
What problems? Crashing? What is crashing? The whole server? Services? I thought you said you wanted to TEST this first?
Will you answer my first question? Workgroup or domain?
> My job is to make sure that the windows server 2003 (new server) can
> be configured to replace the old win nt 4.0 as its having hell lot of
> problems that is why upgrading is not recommended in this phase.
What problems? Crashing? What is crashing? The whole server? Services? I thought you said you wanted to TEST this first?
Will you answer my first question? Workgroup or domain?
ASKER
leew,
If i did not interpret wrongly, I am doing a fresh domain on win2k3.
I am assigned by my company to replace the old server.
I hope you can guide me on this. I still have alot to learn on this.
Thanks for your patience and support.
If i did not interpret wrongly, I am doing a fresh domain on win2k3.
I am assigned by my company to replace the old server.
I hope you can guide me on this. I still have alot to learn on this.
Thanks for your patience and support.
You can migrate to the new server, preserving domain, user account and other information easily using a Virtual machine software and upgrade plan.
1. Setup new server as member server in the domain.
2. Download virtual software mentioned before (VMWare or Virtual Server (both Free) and install on the server).
3. Install on Windows NT 4.0 as a BDC on a Virtual Machine running on the new server.
4. BACKUP the virtual Server hard drive onto a DVD (this is your backup in case anything goes wrong; I've never seen anything go wrong with this, but if you're the first, wouldn't it be great to have a backup?
5. Change the Virtual Server NT4 system into a PDC through Server Manager.
6. UPGRADE the virtual server NT4 system to Windows 2003. This will effectively upgrade the domain to Active Directory and allow (but not initiate) the new PHYSICAL server to be the domain controller.
7. Remove the old failing PDC from the network (it MUST never be powered on again, so if there's anything on it you need, move it to the new server before this)
8. If you want the new server to have the same name as the old server, remove the old PDC domain account from the domain and rename the new physical server to the old name. (I advise against this, but you CAN do it).
7. Run DCPROMO on the PHYSICAL server - this will make it a Domain Controller.
8. Transfer the FSMO master roles, GC, DNS, DHCP if necessary from the Virtual Server (NT4 upgraded to 2003) to the physical server.
9. Shutdown the virtual server for 2 weeks. If all works well, start it, run DCPROMO, and remove it from the domain. If all doesn't work well, start it up and troubleshoot (you probably have a setting or two off or misconfigured DNS). Once you can shut off the Virtual DC for 2 weeks without issues, start it and, as said, run DCPROMO to remove it from the domain. One thing, don't leave it off more than 60 days or you'll have a more complicated job of removing it.
10. Done. Enjoy the new network.
1. Setup new server as member server in the domain.
2. Download virtual software mentioned before (VMWare or Virtual Server (both Free) and install on the server).
3. Install on Windows NT 4.0 as a BDC on a Virtual Machine running on the new server.
4. BACKUP the virtual Server hard drive onto a DVD (this is your backup in case anything goes wrong; I've never seen anything go wrong with this, but if you're the first, wouldn't it be great to have a backup?
5. Change the Virtual Server NT4 system into a PDC through Server Manager.
6. UPGRADE the virtual server NT4 system to Windows 2003. This will effectively upgrade the domain to Active Directory and allow (but not initiate) the new PHYSICAL server to be the domain controller.
7. Remove the old failing PDC from the network (it MUST never be powered on again, so if there's anything on it you need, move it to the new server before this)
8. If you want the new server to have the same name as the old server, remove the old PDC domain account from the domain and rename the new physical server to the old name. (I advise against this, but you CAN do it).
7. Run DCPROMO on the PHYSICAL server - this will make it a Domain Controller.
8. Transfer the FSMO master roles, GC, DNS, DHCP if necessary from the Virtual Server (NT4 upgraded to 2003) to the physical server.
9. Shutdown the virtual server for 2 weeks. If all works well, start it, run DCPROMO, and remove it from the domain. If all doesn't work well, start it up and troubleshoot (you probably have a setting or two off or misconfigured DNS). Once you can shut off the Virtual DC for 2 weeks without issues, start it and, as said, run DCPROMO to remove it from the domain. One thing, don't leave it off more than 60 days or you'll have a more complicated job of removing it.
10. Done. Enjoy the new network.
ASKER
I believe its a very good suggestion you are giving but due to my low knowledge. I am very confused in some parts.
step 1: setup the new server as member server? win2k3 or win nt4.0? how do i go abt doing it?
Do you have any good sites i can read about all these... ?
I just started learning server.. and really appreciate your help.
step 1: setup the new server as member server? win2k3 or win nt4.0? how do i go abt doing it?
Do you have any good sites i can read about all these... ?
I just started learning server.. and really appreciate your help.
How large is your organization? How many users?
Is this new server Windows Small Business Server 2003?
You would make the Windows Server 2003 system a member server simply by joining it to the domain just like you'd join any other workstation to the domain.
By the way, the thing about this solution, it can easily be reverted back to the old network if necessary and it can, for the most part, be done transparently to the users with little, if any significant interruption. There are other solutions, but they tend to require more user interruption and can be more difficult to troubleshoot and go back in the event of problems.
Is this new server Windows Small Business Server 2003?
You would make the Windows Server 2003 system a member server simply by joining it to the domain just like you'd join any other workstation to the domain.
By the way, the thing about this solution, it can easily be reverted back to the old network if necessary and it can, for the most part, be done transparently to the users with little, if any significant interruption. There are other solutions, but they tend to require more user interruption and can be more difficult to troubleshoot and go back in the event of problems.
ASKER
My organization mid-range enterprise total users abt 70 - 100.
As for the new server, the windows server 2003 bought should be either windows server 2003 standard / enterprise.
>>"You would make the Windows Server 2003 system a member server simply by joining it to the domain just like you'd join any other workstation to the domain." ~~ thanks
can you explain in more details for this
"5. Change the Virtual Server NT4 system into a PDC through Server Manager.
6. UPGRADE the virtual server NT4 system to Windows 2003. This will effectively upgrade the domain to Active Directory and allow (but not initiate) the new PHYSICAL server to be the domain controller.
7. Remove the old failing PDC from the network (it MUST never be powered on again, so if there's anything on it you need, move it to the new server before this)"
Do you mean that all these can be done during office working hours and will not affect my users at work?
As for the new server, the windows server 2003 bought should be either windows server 2003 standard / enterprise.
>>"You would make the Windows Server 2003 system a member server simply by joining it to the domain just like you'd join any other workstation to the domain." ~~ thanks
can you explain in more details for this
"5. Change the Virtual Server NT4 system into a PDC through Server Manager.
6. UPGRADE the virtual server NT4 system to Windows 2003. This will effectively upgrade the domain to Active Directory and allow (but not initiate) the new PHYSICAL server to be the domain controller.
7. Remove the old failing PDC from the network (it MUST never be powered on again, so if there's anything on it you need, move it to the new server before this)"
Do you mean that all these can be done during office working hours and will not affect my users at work?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
A 2003 server can join an NT 4 domain without issue. You CANNOT have a 2003 domain controller in an NT4 domain though. For testing purposes, I would strongly recommend you download a copy of Virtual Server/Virtual PC/VMWare and setup a virtual network for your tests.
I also do not (in most cases) believe "starting fresh" from an NT4 domain to a 2003 domain makes much sense. NT4 domains are basic with little that can REALLY go wrong. Instead, I would do an upgrade of the domain to 2003. This is relatively easy and safe and can be done using Virtual Machines if your existing hardware is too old to support 2003 and/or you don't have any spare machines or NT4 compatible network cards.