My colleague just left my office - we have jobs to replicate our web image content between Dev, QA, and Prod that run several times a day. I just migrated the process to use Unison. His words - "the old job is running for 15 minutes already... in that time, I've synchronized 5 other sites to 3 environments with the new scripts!" This is why I recommend this tool..

Couple of other reasons to consider Unison over Robocopy
- Speed
- restartable
- fault tolerant (won't change the target until the copy is complete and verified)
- Client only or Client Server modes

Client/Server is DAMN FAST! 8 seconds to compare our 16G data structure and determine that no replication is needed! Easy to use, too. Copy Unison to both systems. On the target, run "unison -socket 1758" - this sets up a server listening on port 1758. On the source system, simply run
 Code:
unison d:\path1\path2 socket://host:1758/D:\path1\path2 -times -batch -force d:\path1\path2

This will copy everything from D:\path1\path2 on the local system to the target, preserving modification times, and forcing the source to be the winner if there are file conflicts.

Since you will be working in groups of users, your script would create the new home folder and set permissions as you want now, instead of matching possibly incorrect perms. Unison works with profiles - simple text files, so you could add -root "username" entries to the profile, and simply run "unison profname" when your script is done deciding what to do, logging off users, closing connections, and making directories.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D