I'm working on converting my users from local machine based profiles to network profiles stored on a centralized fileserver.
The majority of my users are "local", in that they work in the office 75% of the time. I think I will get some resistance from them, but I can minimize the pain using the folder redirection technique.
The real problem is going to be my salespeople, who are in the office 25% of the time, and who really need access to their files. But of course, they really want their files backed up. And of course, they're the most likely to require a loaner machine. Really, I think salespeople might be my problem in general, but that's an entirely different issue.
Anyway, here's the deal. Since my salespeople roam away from the network, they frequently log in using cached credentials, then gain access to network resources via an SSL VPN connection. This seems problematic if I switch them to network-based profiles. They won't have access to many of the profile contents until they connect to the VPN, but they'll probably need something on their network shares (i.e. the contents of their start menu, or desktop?) to do it.
It seems like a catch-22. I know that the profiles attempt to sync at user logoff. If the user is away from the network at logoff, does everything remained cached? When they come back in to the office, will things magically resync and cause a 20 minute login?
What do you do keep your truly roaming users tied into the domain?