Users unable to search redirected profile folders

A suggestion or two..... try using robocopy.. and tell it to ignore the security /COPY:DAT this "should" allow the files to be copied and inherit the permissions based on the parent folders. The problem when I did this was the the previous admin had set permissions for the user on the child folders and I ended up going back and having to reset them by hand.

Another option is to script it. If you have tons of users to move and know you have to reset the ACLs, icacls would be one way to go. Have teh script copy over the users data and then have the script reset the permissions for you.

But more than likely, you'll need to abandon the GUI for a bit to make this easier on yourself.

I've stayed away from using redirected folders and roaming profiles. From my experience they've caused more headaches than they have solved, especially when you add laptops into the mix.

Large profiles tend to cause a lot of extra network traffic, especially if you ever have remote sites with VPNs setup - pulling people's profiles over the VPN is painful. I've also run into problems with some programs which store settings in the user's profile that are machine or location specific, though I can't remember exactly which programs at the moment.

My solution, which may solve some of your concerns is:

• Everyone gets a network drive P:, which is configured in their AD profile to go to one of our file servers. Since it's configured in their profile, it will follow them around to other computers.

• Laptops have offline files enabled for the network drive so they can use them remotely. In windows 7 this works very nicely and files are synced back to the file server as soon as they reconnect. No need to logoff or anything.

• Users are required to save all important company documents to the X: drive. Since our file servers are backed up every night, our documents are safe.

• Personal documents, temporary files and internet downloads are saved on the local hard drive - this saves us a LOT of storage space on the server. I've seen quite a few users store lots of photos/music/whatever in My Documents, not realizing it's actually taking up space on our fileserver. With this setup it's clearer to users what is stored locally and what is stored on the fileserver.

• Backups work just fine even if people don't logout, since the only files in use will be documents people are actively working on (and a good backup program should be able to backup most in use files anyways).

The only downside is that users need to be trained to save things to their network drive. I haven't found this to be much of an issue with most users.