The environment is Server 2012 R2 domain controllers on a windows network. The workstations are Windows 7.
In AD for each user, I am setting the home folder H: to \\networkdevice\home
This network device is actually a synology device, so, the home folders don't actually get created under \home because the synology device is doing some kind of black magic and making a home folder under the \homes folder and naming it \username -random#
That's fine really and everyone is getting an H: drive and can store documents there.
My problem comes in when I try to set up folder redirection.
I set folder redirection to H:\My Documents OF course I get the pop up about if that local drive isn't available, the redirect will fail, but it IS available since I'm setting it in AD.
Folder Redirect is failing.
I think it's because H: isn't mapped yet at login, so I need folder redirection to run AFTER mapping the H: drive so that my redirect to H:\My Docs will work.
It seems I recall a setting somewhere that will put off the application of a redirect until after networking components are loaded but I can't recall where it is.
The redirect to \\networkdevice\home doesn't work because of the way the synology device does it's black magic in creating folders in places other than what is specified in AD. I've tried it seven ways to sunday.
Ideas on how I can make the folder redirect apply only after mapping the H: drive or any suggestions better than the one I'm using?