Upgrading WinNT 4.0 LAN to Win2K

[DZuroff]

I am looking for tips on upgrading my WinNT network to Win2K. A buddy of mine told me a good way to start this process is to connect the new Win2K Server box to the network and run DCPROMO. He told me the Win2K server will demote my current PDC and take over the role as PDC, along with migrating all user and security settings. Does this sound like a good plan? I have played around with Win2K server a bit, but I am still learning how it works. Is there anything I should know before trying this? How should I initially setup Win2K server? When I run DCPROMO, will that automatically create the domain forest in active directory? So many questions, I know... but I want to be comfortable when I do this. Moving up from NT is a big step! The bottom line is if something goes sour, I want an easy way out. From what I understand all I would have to do is disconnect the win2K box and promote my original PDC back to PDC again and everything would be back to when I started.

 

[DZuroff]

I should also mention I am running Exchange 5.5 on another server so I will have to upgrade that to Exchange 2000. This is a little off topic, but is that a pretty smooth transition from 5.5 to 2K?

 

[JackyZhang]

Check this Microsoft Knowledge Base Article - Q316886

MCSE, MCP+Internet, CNE

 

[jamesch]

I was in the same boat. What I did was get a server/computer and put NT4.0 server, set as a BDC to your domain, replicate the security stuff, and all the computer Sid’s or leave it on your network for a couple of days, and let it replicate normally. Then take it off your network and create a small test bed, with a test network, i.e. hub/switch, and some computers/laptops. Upgrade the server to W2K. Play with this and get comfortable.
Also the computers that you hookup to on the test bed, do not hook back up to the main network, the SID’s change and will have to redo the software (we just use Ghost). Also do not use the same server that you upgraded to W2k on the main network, this will freak thing out. Pick the main server that is going to be the ONE, and clean up any junk on the server. After your test bed runs ok, then upgrade the main server on the network to W2k. Another good ideal is to also take the main server to upgrade first off the network, then upgrade it, then after the upgrade put it back on the network. The test bed server needs to be formatted afterwards. Make sure you have a plan for DNS, Internal or External. Active Dir. Lives and runs off of your DNS configuration. Microsoft has an upgrade to W2k from NT4 class. I took this and it is very helpful. All of this worked out great for me!

 

[GlenJohnson]

Before you do anything, make sure you've got a valid backup working and make sure you can restore. Make sure you have a plan for DNS, Internal or External. Active Dir. Lives and runs off of your DNS configuration jamesch is right on the money about this. Good luck. Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com


"What really happens is trivial in comparison to what could occur."
Robert von Musil (1880-1942); Austrian author.

 

[jamesch]

P.S. I really don't know about the Exchange portion, but when I attend that upgrade class for W2k, the other guy (there was only two of us) was running exchange 5.5, and was going to 2000. I didn't pay too much to the conversation (because we use GroupWise 6) but I did hear that it was another ball park, and the instructor told him he better study on the upgrade of exchange, or take some classes.

 

[GlenJohnson]

We use I-Mail becuase of ease of use, and less costly, but I've heard exchange 5.5 is a pretty heavy hitter. jamesch is right, REALLY do your homework on that. Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com


"What really happens is trivial in comparison to what could occur."
Robert von Musil (1880-1942); Austrian author.