• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 424
  • Last Modified:

Win 2000 Server w/Exchange and 2000 TS migration to SBS 2008 Prem and RDS

I have a scenario where an office has a Windows 2000 server that is a DC and has Exch 5.5 on it and another 2000 member server running Terminal Server. They client uses their local workstations as dumb terminals and run RDP to the TS and that is where their Desktops live.

I would like to replace the hardware with two new servers, one with 2008 SBS Premium and the other 2008 with Remote Desktop Services. As there is no upgrade path from Exchange 5.5, I’m thinking of backing up each user’s mailbox to a .pst, setting up Exchange on the SBS server, and then importing the .pst’s into the new Exchange store.

As for TS, what is the best way to handle the profiles? Can I join the new SBS 2008 server to the existing Domain, transfer the FSMO roles over (along with the users, security, etc), robocopy over the folders and move the TS profiles to the new TS server? Will that work? Or, do I need to start with a fresh Domain on the new equipment and recreate the security, shares, migrate profiles, etc? There are only 10 users.

1 Solution
I would not import profiles from a 2000 system to a 2008 TS.  Think of it like this.  If you were wanting to replace a windows 2000 workstation with a windows 7 workstation (which is in fact what the server differences are), you would want to create fresh brand new profiles for each user.   Now copying Favorites, documents, etc. would be regular practice in moving a user.  Not much work for 10 users and very much worth having fresh profiles.
I agree with mcrossland With only 10 users, best practices to start everything afresh. Not worth migrating any settings
Again since you moving several products version forward a new setup is recommended. Exporting/importing individual mailboxes to a .pst is probably the best way to move the mail. If you have any public folders be sure to export them too. Robocopy is great for moving the file structures but don't copy any security as you'll have to reset it up on the new server. This includes shares, share permissions, and file permissions. As for RDS user profiles. I created the following batch file:

@echo off
if "%1"=="" goto no_arg
set src=C:\backups\profiles\%1
set dest=c:\users\%1
echo %src% - %dest%
if not exist %dest% goto invalid_user
echo Copying profiles files...
robocopy "%src%\desktop" "%dest%\desktop" /s /e /np /r:0 /w:0
robocopy "%src%\favorites" "%dest%\favorites" /s /e /np /r:0 /w:0
robocopy "%src%\my documents" "%dest%\documents" /s /e /np /r:0 /w:0
robocopy "%src%\my documents\my music" "%dest%\documents\music" /s /e /np /r:0 /w:0
robocopy "%src%\my documents\my pictures" "%dest%\documents\pictures" /s /e /np /r:0 /w:0
robocopy "%src%\my documents\my videos" "%dest%\documents\videos" /s /e /np /r:0 /w:0
md %dest%\outlook_temp
md %dest%\outlook_temp\outlook
robocopy "%src%\Application Data\Microsoft\Outlook" "%dest%\outlook_temp\outlook" /s /e /np /r:0 /w:0
md %dest%\outlook_temp\signatures
robocopy "%src%\Application Data\Microsoft\Signatures" "%dest%\outlook_temp\signatures" /s /e /np /r:0 /w:0
goto exit
echo ERROR - Usage: %0 [username]
goto exit
echo ERROR - No folder for %1

Open in new window

It copies desktop, favorites, documents, music, pictures, videos, outlook settings, and signatures. Be sure to change line 3 to point to the location of the previous user profiles. Note it creates temp folders for the Outlook stuff. This is because you need to open Outlook and create a blank signature with the exact same name.  The name is the same as the folder name within the signatures folder. Then just copy the old profiles signature files/folder to the new signature folder. You also need to set when to use the signature. You also need to make sure the .nk2 file (Outlook name cache) matches the Outlook profile name.

DopherAuthor Commented:
This is great info and I really appreciate you posting the script as an example. Thanks!

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now