With windows server 2003 losing support in the coming weeks we have upgraded our 2003 servers to virtualized 2008 servers. The only problem we are having at the moment is with Group Policy and mapping drives. Previous to this upgrade we used a logon.vbs which "worked" but was nearing 10 years old and did have faults every once in a while. However since the change the script is a complete bust, broken, no drives map from it and so we have to run to each work station and remap drives manually. We have since removed the logon.vbs from being used and replayed it with the Drive Maps under User Configuration->preferences->Windows Settings. We are using replace with these drives and also Item level targeting to target the security group for different people. We have in total about 20-25 drives however we have some repeated drives (three instances of S:) but they are all to totally different groups that would not coincide with each other. So they should never have to be mapped onto the same computer, this still isn't the problem. Currently (Day 8) we have had 2 computers no grab any of the drives they were supposed to, both users were in the groups, we ran a gpupdate /force followed by a restart and still nothing, I then ran a gpresult /h and couldn't find anything as to why it would fail. DNS checked out fine and no one had any complications there. We also had 2 other computers that grabbed 4-5 drives correctly but missed one. Is there any big reason that sticks out in anyone’s mind why this is happening?
Ran a Report from GPM on one of the computers and it came back with this under the drive maps:
Group Policy Drive Maps: Failed
Group Policy Drive Maps failed due to the error listed below.
The system cannot find the path specified.
Additional information may have been logged. Review the Policy Events tab in the console or the application event log for events between 5/28/2015 8:39:31 AM and 5/28/2015 8:39:31 AM.
All paths are correct and the same policy works on a number of computers. When on their computer I am able to type the exact path mapped VIA the drive maps and it comes up perfectly fine.