D
DanKipping
Guest
Hi all.
Here's something interesting. I have had a group of users call (three or four users) from one of our sites, reporting that all of their mapped drives connect as usual when they boot to Windows- except one. All of them are having trouble with just the one!
I have verified that the relevant GPO which facilitates the mapping (it just executes a script) is Enabled, and the users affected are in a Security Group which grants them access to that mapping.
I have ran a 'gpresult /r' on one of the client systems, and it showed no errors; the results didn't show that it mapped- nor did it list that the mapping was blocked! It's as though the client systems aren't aware that the GPO exists anymore...
To test, I grabbed a spare laptop from our office, logged in to Windows using an affected users' account credentials, and the drive mapped! So it doesn't appear to be an issue with regard to a change made in Group Policy or Active Directory...
It's as though it is something affecting the systems on site that usually have the mapping processed; like something has all of a sudden broken.
I'm running out of ideas here, so I'm hoping somebody can point me in the right direction?
- Dan.
Continue reading...
Here's something interesting. I have had a group of users call (three or four users) from one of our sites, reporting that all of their mapped drives connect as usual when they boot to Windows- except one. All of them are having trouble with just the one!
I have verified that the relevant GPO which facilitates the mapping (it just executes a script) is Enabled, and the users affected are in a Security Group which grants them access to that mapping.
I have ran a 'gpresult /r' on one of the client systems, and it showed no errors; the results didn't show that it mapped- nor did it list that the mapping was blocked! It's as though the client systems aren't aware that the GPO exists anymore...
To test, I grabbed a spare laptop from our office, logged in to Windows using an affected users' account credentials, and the drive mapped! So it doesn't appear to be an issue with regard to a change made in Group Policy or Active Directory...
It's as though it is something affecting the systems on site that usually have the mapping processed; like something has all of a sudden broken.
I'm running out of ideas here, so I'm hoping somebody can point me in the right direction?
- Dan.
Continue reading...