I am just now setting up a Windows 2k3 domain (we are currently just using a workgroup) for about 50 users. I have started giving folks domain accounts instead of their old local accounts and have started transferring their profiles to the domain accounts. I would like for the secretaries to have roaming profiles, but all of them have pretty big My Documents folders (>5Gb) and so I set the My Documents folder up to be redirected instead of roaming using Group Policy. I did this for one of the secretaries by logging her in with her new domain account and then copied the contents of her old My Documents folder into the new redirected one. It took a very long time to do it (I assume because it had to transfer it all over the network) and then took forever to log her off while it was synchronizing files. Now she goes to log back on and it is taking forever again! I look at the status of the file server and in the "Open Files" list it seems to be going through every single one of her 2500 files, most of which are decent sized image files. Is this the offline files feature killing the performance? I thought the whole point of redirecting the folder instead of just including it in the roaming profile was to avoid this kind of thing. In the share settings for the profiles share on the server I don't have it configured specifically to do offline files, by the way. Any advice for how to set this up correctly? I basically followed the whitepaper recommendations that I was able to find at microsoft.com, and am seeing this result. Also, any suggestions for good references on how to move lots of users profiles from local ones to domain ones? I have not found many books that describe how to do it. The "Copy Profile" function in the profile manager doesn't seem to work because the ntuser.dat file is still for the local account, not the domain one. Should the domain one log in once to make a new ntuser.dat, then save that one, then copy the profile over, then replace the ntuser.dat?