We are using roaming profiles for about 50 users that use different machines routinely and everything works fine on our local LAN with a very fast pipe. These users will occasionally go to a remote site where the connection sucks. Even a small 10 MB profile can cause unacceptable login times (> 10 minutes) What I'm thinking of doing is this. 1. Prevent roaming profiles at the remote site by setting the "only allow local profiles" setting via a GPO 2. Since they will still want access to data back at the home office I will redirect their my documents folder to a file server 3. Use the "Do not automatically make redirected folders available offline" setting. I don't want the redirected files to be pinned and slow down their login. The connection at the remote site is slow but seems to be reliable, I'm not worried about them working offline. 4. Use "Allow processing across a slow network connection" for folder redirection I was also thinking about redirecting their desktop since a lot of them seem to save to their desktop too. I'm not going to redirect application data I think this should still allow them to use roaming profiles at the home office like normal and it should solve the problem at the remote site. What do you all think? Is this an OK plan or would you do something different? Thanks Mike