Hello All, I am getting ready to put in place a new Server with Windows Standard Server 2008R2. The new server and domain will have the same name as the old server and domain. There are 20 users, and do not wish to go to every station and quit the old domain and then join the new domain. This will require that all local printing and email accounts and misc. other configurations have to be done again. This is extremely time consuming. Is there q quick and dirty way of using the old workstation profile from (Server 2003) existing server and domain to have it work on the new server and domain? Thank you for the courtesy of a reply. Vito

Consider migration. Look for conditions and prerequisites which are mainly the functional level and application of AD schema changes. Here is article from Technet that will give you more info http://technet.microsoft.com/en-us/library/upgrade-domain-controllers-to-windows-server-2008-r2(WS.10).aspx

If you do not want to have to rejoin the workstations to a new domain, then I would suggest promoting the 2008R2 system to a domain controller in your exisiting domain, and following the usual migration procedures. http://support.microsoft.com/kb/555549

I would suggest that you choose a new server name, and as D.L.Hannah said promote the new server as a domain controller. Configure static IP addressing on the new server. Insert 2008 R2 CD into old server, run ADPrep: <CD Drive Letter>\Support\Adprep\Adprep32.exe /forestprep <CD Drive Letter>\Support\Adprep\Adprep32.exe /domainprep /gpprep Promote the new server as a Domain Controller (Start > Run > DCPromo.) This is a good time to point any devices with static addressing configurations to the new server. It will also allow you to test before taking down the old system. Configure DHCP scope on the new server. Don't just copy, remember, the options will be different for the new server. (If applicable) Disable DHCP services on original, enable scope on new server. Migrate WINS to the new server. (If applicable). WINS is going to go away, if you don't need it then I wouldn't bother. Migrate shares. If you want to make this more automated, look into the File Server Migration Toolkit: http://support.microsoft.com/default.aspx?scid=kb;en-us;255690 Migrate printers. Transfer FSMO roles from old server: http://support.microsoft.com/kb/255504 (Follow Transfer FSMO Roles section) Demote old server (Start > Run > DCPromo). Make sure not to check that this is the last server in the domain. This is important. I have seen too many instances where people just remove the old server without "telling" Active Directory that it is no longer existent. Disjoin the old server from the domain, or leave it as a member server. Something to consider: It won't do any harm to leave the old server running as a second domain controller, unless there are other reasons such as power. This will give you some redundancy should one of the servers fail. Please note that the Print Migrator tool is no longer supported in 2008 R2: http://technet.microsoft.com/en-us/library/cc722360.aspx. Unless you have a massive amount of printers, I would simply re-create the shares on the new server as this is a cleaner approach, and often much faster in the end. A+, Net+, Sec+, MCP, MCTS, VCP4, VCP5

If you do not want to have to rejoin the workstations to a new domain, then I would suggest promoting the 2008R2 system to a domain controller in your exisiting domain, and following the usual migration procedures. http://support.microsoft.com/kb/555549