I recently started managing a windows network. It has one Win2000 server and 18 WinXP Pro workstations. However, it is setup on a workgroup instead of a domain. Of course, I want it on a domain, but I'm not very experienced with windows network management and need some advice on the best way to get there. We have the CDs here to install Win2003 server which never got upgraded and I also have an extra physical server that isn't currently in use. The current server is pretty much a disaster and I would really like to install Win2003 on this extra server and set it up properly then migrate everything over to it. If you were in my position, how would you handle this? We can't afford any downtime to speak of, so I want to be careful and make sure the transition goes smoothly. Thanks for you advice! BTW the server doesn't have web or email or anything like that on it. It's main function is holding the mail order manager database and file sharing and backups. Thanks for any tips!

Do you, in addition to the 2003 server cd and license, also have 18 2003 client access licenses? If not you would upgrade and not have wkst connectivity. It would also be a mistake to bring up a 2003 server into a domain then expect to move the 2000 server to that domain. User accounts won't xfer that way [two domains even if they have the same name] without additional work/utilities. You really need to go out and buy a server book but I can give you the highlites here. Backup the 2000 server to tape Setup DNS on the 2000 server DCpromo the server to a DC Get all wksts connected and working. Install 2000 on the 2nd server DCpromo to DC [you should always have two DCs for failover] Configure both to have the Global Catalog If/when you want to go to 2003 Consider if the apps you run are supported under 2003 as well as the printers you are using. Get 2003 server licenses and cals Run ADPREP on the 2000 domain Upgrade each server to 2003 That's it in a nutshell. Golly gee wilerkers everyone. Learn to Internet Search

Make sure your main app is supported under a domain configuration and not tied to a workgroup. Some apps want more money if setup in a domain since they were designed for single use which some folks get by since they do peer to peer [workgroup] networking. fYI Golly gee wilerkers everyone. Learn to Internet Search

I'm not expecting to move the 2000 server into the new domain. Once everything is migrated to the 2003 server, the old server would be retired and used for something else. This isn't something that will be happening immediately, just trying to research ahead of time to help me determine the best way to accomplish this. And yes, I am reading everything I can get my hands on and learning a lot along the way. Just need to be sure I'm heading in the right direction at all :) As far as licenses for 2003, we only have 5 currently, but this isn't happening right now and if we choose to go this route we will of course obtain the extra licenses needed ahead of time. If I setup the 2003 server as a domain controller and it's on the same network with the current server/workstations, will it have any effect on them or the current workgroup (assuming I don't attempt to join the workstations to the new domain)? Thanks much for the quick replies!!

It shouldn't affect the other PC's on the same physical network. However, just to avoid problems, I would segment it onto it's own separate subnet to prevent cross communication until you're ready to roll over to the domain infrastructure. That is, unless you have some need to have them all on the same subnet. I'm not expecting to move the 2000 server into the new domain. Once everything is migrated to the 2003 server, the old server would be retired and used for something else. I recommend you reread wanderer's post and pay particular attention to where he talks about having two servers in the domain for redundancy. Good backups are always a must but they don't prevent downtime should your DC fail. A second DC can and will do that, allowing you to take your time rebuilding the other server and reinstalling/restoring. Believe me, if you've never been in a situation where your only DC fails, you don't want to be and redeploying the old server as a second 2003 DC in your domain would be a good/smart thing to do.