New Server

[jimmm33]

I will soon be replacing a Windows 2000 Server with a new Server 2003. The workstations will remain.

Can I simply setup the new server as the domain controller with the same users/passwords and have the existing workstations connect without making changes to those workstations or will new profiles need to be created?

It's a small network in a Dr.'s office of about 10 machines. Nothing fancy like Exchange. Just an application that run across Terminal Services.

Thank you all for any input.

jim

[CCT]

This isn't an area I am knowledgeable in, but here is a first resource:

http://www.microsoft.com/windowsserv...k/default.mspx

http://support.microsoft.com/kb/325379

Just Google ' upgrade windows server 2000 with 2003 '

[jimmm33]

The old server will not be upgraded. It is being replaced with a new machine that is running Server 2003. I'm wondering if I will need to do anything special to the existing workstations to get them to connect to the new (Server 2003) domain controller instead of the old one (2000 Server).

[CCT]

So, then change your Google to: ' replace windows 2000 server with 2003 '

You'll get stuff like this:


http://www.petri.co.il/forums/showthread.php?t=4727

http://www.tek-tips.com/viewthread.c...1410831&page=3

[CCT]

Another GOOD Google is for: ' transfer workstations to server 2003 from 2000 '


http://techrepublic.com.com/5208-623...&tag=rbxccnbd1


http://search.techrepublic.com.com/s...ml?t=4&s=0&o=0

[emr]

You can install the new 2k3, then do a dcpromo and join it to the existing domain; if you can afford to leave the 2k server running for the time it takes.

Then AD will be replicated across to the 2k3 and once you have it setup as the global catalogue you can effectively take the old server offline.

You'll need to move the data across obviously.

Honestly though, and this is not meant in anyway to be disrespectful, if you have to ask how to do this then don't do it. Many things can go wrong here.

Either find time to setup a test environment and run through it yourself or source someone who can do this for you.

[jimmm33]

Thanks for the replies.

Since this is a simple network with only 10 users who just share files and run TS, I wonder if I can kinda start from scratch.

I was considering going in to the existing workstations and unjoining the existing domain. Then shut down the old server. Install the new server and make it the DC, restore the data from backup, and then join the workstations to the new domain.

Can you foresee any problems by going this route?

[slgrieb]

Problems? Sure. Restoring data isn't going to migrate things like Group Policies and any of the hundred other details you find on even a simple server setup. You really should listen to emr, or you're likely to have many unpleasant surprises (instead of several).

[Polymathink]

Thanks for the replies.

Since this is a simple network with only 10 users who just share files and run TS, I wonder if I can kinda start from scratch.

I was considering going in to the existing workstations and unjoining the existing domain. Then shut down the old server. Install the new server and make it the DC, restore the data from backup, and then join the workstations to the new domain.

Can you foresee any problems by going this route?

Starting from scratch sounds like a really bad idea here. Emr is giving you great advice, both technical and otherwise. The added wrinkle here now is that you are running TS, licences which you wil have to migrate to the new server (I suspect by entering the new licence numbers using the TS licencing snap-in). I wonder how many other wrinkles there are. The best advice is to get someone who knows how to do this and has done it plenty of times.

BTW, if SBS (Small Business Server) is involved in any way here (either changing from or to) there are a host of other things to look out for.

Mike Watson
President
Polymath, Inc.
http://polymathink.com