R2 roaming profile migration from 2003 x86

[snootalope]

We currently have a server 2003 x86 terminal server/citrix farm that 90% of the users in our company use. They all have roaming profiles setup.

I've been working with a new farm that consists of server 2008 R2/Xenapp 6. Works well and we like it.

The biggest issue we're running into, is that we have to completely rebuild each user that we'd like to migrate to the new system. We can have them login to the new setup and we can copy over their desktop items, favorites, etc. However, this isn't going to fly when trying to bring over hundreds of users.

I've experimented with folder redirection from the new v2 profile to the older 2k3 profile. Works ok I guess, but it's not really good solution in my mind as their still left with two sets of profile info on our storage box. I'm curious if anyone else out there has been through this or is planning on the same migration? What did you do or what are you going to do with the roaming profiles and what about getting it set so all their settings stick around? Are you planning on starting each user from scratch?

Sure wish there was a tool or even something built in to MS that we could just keep the standard roaming profiles and "upgrade" them to the V2. Doesn't look like anything will ever exist though...

 

[hydruid]

I've found the best solution is to have all the users login to the new system (I did this with a macro program, winmacro)

Then take a list of usernames and set them up like this in a batch file with the variable option and robocopy their stuff from the old location to the new:


set var=user123
robocopy "F:\Redirects2\staff\home\TS\%var%\Favorites" "E:\redirects\staff\favorites\TS\%var%\Favorites" /MIR /R:2 /NP
set var=user456
robocopy "F:\Redirects2\staff\home\TS\%var%\Favorites" "E:\redirects\staff\favorites\TS\%var%\Favorites" /MIR /R:2 /NP

Then once you're sure you have everyone's stuff out of the old location, delete it (highly suggest archiving it somewhere)

Correctly asked questions will receive a better answer.

 

[snootalope]

Brilliant. I never thought of a batch.

Still doesn't take care of the Outlook and it's registration and all, but that definitely helps. thanks man

 

[hydruid]

what version of outlook are you running?

shouldn't be too tough to deploy with office options, gpo's, and or vb scripts to customize it.

My personal favorite though is to give them a handout that says if you want your email to work do this lol.

Correctly asked questions will receive a better answer.

 

[snootalope]

Running Office 2007.. Yeah, saying their email won't work gets their attention real quick like.

 

[hydruid]

yikes, for me office 2007 is the hardest to customize to work properly without manual editing.

your best best is to either do it by hand or macro logins and outlook setups

Correctly asked questions will receive a better answer.