Windows Forum

Ask something
Discussion Locked

NT upgrade to Win2K Server

0 helpful
5 replies

by daniel

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Win2K Server install on NT domain
Most of the articles I reviewed refer to upgrading an existing NT PDC to Windows 2000 Server - however we want to replace the existing PDC and BDC with new servers that have Windows 2000 Server installed. Our network is currently running Exchange 5.5, File Server, Proxy, and a few other stand alone servers on Windows NT 4.0. In addition, I have just introduced an IIS standalone server running Win2K server. The current PDC also acts as our print server and theBDC acts alone.

I know I should take a BDC offline in case their is a problem with the Win2K upgrade, and I have full backups of all the servers. I want to find out the proper procedure for replacing the existing NT domain controllers with Win2K(without upgrading the actual NT machine with Win2K, if possible). We plan to go to Win2K on the PDC and BDC soon, and eventually upgrade the rest of the NT servers, so I figure we would have to run in mixed mode until that time.

Lastly, how does the Win2K server DNS naming scheme fit into our current domain name? For example, if our current domain is called ALPHA, how do I name the Win2K server (I was under impression it would be called something like alpha.org, and so forth with child domains, although I dont see how it would communicate with existing NT servers under ALPHA domain). I installed the Win2K web server under the ALPHA domain, and I get an error message in Event Viewer stating the domain name isn't DNS type and some Win2Kfeatures won't be fully utilized with the current naming convention.

I appreciate your help,

Dan

5 replies

by jeremy the it guy

The proper upgrade process has been listed here in the republic before. Microsoft also has a guide to upgrade a PDC from NT 4.0 to Win 2K Server. You are correct about having to run in mixed mode. As far as DNS goes, Windows 2k Server is heavily reliable on DNS. When you set up DNS on your machine, it will ask you for your DNS name for your network. I chose intranet.starprecision.com. and it's been working perfectly. Windows 2K Server just wanted to see a xxxxx.xxxxx.com or .org, etc. Ihave completed this process and I have had no problem. I upgraded the PDC, set it to run in mixed mode, set up DNS and tested it thoroughly and I have had no problems in 6 months. If you need any help, jwhitlock@starprecision.com is my email. Take it easy, Jeremy

by shanghai sam

i just got done with upgrade NT 4 server to W2k server.
First, if u wanted to replace PDC with newer server that is simple, here what u should do first.
on the newer server let name "ABC computer name" install as BDC controller so u can get latest and greatest SAM then unplug the network cable. take ABC computer to private network promote to PDC now u have all the SAM. next do DCPROMO, this new server it will become your first AD, make sure u have DNS install under NT 4 server first before upgrade to W2k AD. on TCP/IP go to DNS setting point your primary DNS to yourself this because u need DNS server. First AD server require DNS server on itself.
As for your print server, if u are using TCP/IP printer i wouldn't use print server. i would just force all computers to connect directly from their computer using TCP\IP.

Jimmy Wang

This discussion is closed to new replies.