Hi guys We have a small domain based network with 6 workstations. Server is Win 2003 Ent SP1, and all workstations are Win XP Pro SP2. AD and DNS servers are running, everything is smooth. All computers can see the internet (routher, DSL). My boss bought a new server machine with no software on it. It is Gateway, pentium 2.8 GHz, 1GB RAM, 80 GB hard disk. He asked me to install a fresh copy of Win 2003 Ent Server on this new machine and replace an old server machine with the new one. I am not very familiar with these things (although, in the company I am the best choice). Everything should stay the same as in old configuration. Just server machine will be replaced (with a fresh copy of Win 2003 Ent). Domain name stays the same (it is "domainname.local" Could someone tell me how to do this (sort of) migration (possible step by step)? If I add all the users (with the same names as on the old server) to the AD on the new serevr, do I have to re-join all the workstations to the new domain (domain name is the same as the old domain name)? And if I re-join all the workstations to a new machine, users will loose all their settings and programs (since these will be brand new users on the new server). How do I copy all the users settings from old server to a new one? I've read this forum, and found some explanations how to migrate between 2000 and 2003, not from 2003 to 2003. Any suggestion is appresiated. Thanks. Zoran

The simplest thing might be to make the new server another DC in the domain. Then, transfer all FSMO roles and the Global Catalog to it and take the other one down. This is a very simplified version of what all would have to be done. More in-depth info available at microsoft's web site. I would highly recommend you start by spending some time reasearching/reading migrations on microsoft's web site.

Thanks for the suggestion. I guess I have to do some serious reading. I was hoping for some easy 2-3 steps solution. I didn't try MSDN site because whenever I was looking for something before there are 2 milion articles on the subject and they all are hard to understand (probably writen by programmers). Well, that's MS.

You could always suggest that he call in a local consultant and you could watch so you understand how in depth it can get for next time.

what if he did this? use Copy commander to copy the entire HD form the one machine to the blank 80GB HD. Then, re-install it back in the "NEW" machine. Before you completely boot up, have the NEW Server 2003 disc in there and allow it to boot up and do a windows "re-install" or repair on the exisiting OS. It will prompt you for the new CD keys, input them, and when done you have to activate, like you would anyway, but the original settings will be the same, just configured properly for the new computer and hardware. Copy commander can be found at http://www.v-com.com website. Works to copy an os to any other HD, even Longhorn and Server 2003.

While that could be tried, a dirty install like that isn't what I would have in mind for something as important as the sole domain controller. Curt_R has probably the best path. When Curt said "put it down", be sure you understand that means dcpromoing it down to a member server before you decomm it. DO NOT SIMPLY UNPLUG IT FROM THE NETWORK! I'm assuming the old server is a DNS server? If so, don't forget to make sure the new server has DNS installed with all the records on it, and that all clients are configed to use this DNS server either through DHCP, or manually configing them. "President Bush is doing everything he can to lower gas prices, including...making the oil companies so rich that maybe they'll get sick of money."

Another thing that should be brought up... If the old server now is the sole domain controller, I would HIGHLY suggest you add this new server as an ADDITIONAL DC! This would provide fault tolerance for logging into the domain, and is best practice. If you do this, once the new DC is online, you should transfer some of the FSMO roles as well. The faster new machine should be the PDC and RID master, while the older DC should be the schema, infrastructure, and domain naming masters. "President Bush is doing everything he can to lower gas prices, including...making the oil companies so rich that maybe they'll get sick of money."