• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 977
  • Last Modified:

Group Policy has broken Mapped Drives

Hi,

We tried setting Group Policy to map the drives for users on our network - this was so we could get rid of the logon scripts which were initially mapping drives for users.

We had problems with users drives not always mapping correctly, and as it's a live network, we decided to revert back to the login scripts and disable the Group Policy completely.

However, the N:\ is now stuck as 'in use', despite the Group Policy being disabled for a few days now, and we can't even delete it from the client PCs via CMD.

The drives which the login scripts are mapping are now also showing the names that were setup with Group Policy, ie:

N: used to be "Example1" and we set the Group Policy to name it "Example One" - it is now stuck as "Example One" no matter what we do.

Any suggestions?

Cheers,
0
tetrauk
Asked:
tetrauk
  • 5
  • 3
2 Solutions
 
ChrisCommented:
was this using group policy preferences to map the drives or something different

if not then it might be worth having a go with them to either remove them completely to use a login script or to map them like that
0
 
tetraukAuthor Commented:
Yeah - we were using the GP preferences.

We have tried deleting the drives; we do a net delete * and remap all the drives in the login scripts.

Cheers,
0
 
ChrisCommented:
i would try specifying all the drive letters invidually

net use z: /del /y

on the GP preferences have you tried setting the action to delete?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
tetraukAuthor Commented:
i've set the gpo back with action "replace" and the condition to remove when gpo is removed, i'm going to leave that in place for 24hours to make sure it gets to all users, as its a user preference, and then try removing tomorrow. Once removed from GPO it should leave teh space for the login script mapped drives to take over.
0
 
arnoldCommented:
Disabling a policy does not necessarily reverse the imapct it had. Mapping drives is likely one of those.
The other part is the GPO addition/removal impact usually takes some time for the refresh of the policy and the two or so logins after the change.
Are you certain that the mapped drive is from the GPO and not a persistent map by either the user or a prior login script?
0
 
tetraukAuthor Commented:
Disabling a policy does not necessarily reverse the imapct it had. Mapping drives is likely one of those.
The other part is the GPO addition/removal impact usually takes some time for the refresh of the policy and the two or so logins after the change.
Are you certain that the mapped drive is from the GPO and not a persistent map by either the user or a prior login script?

Yes, they were set to persistent... However the net delete * should still delete them.
0
 
ChrisCommented:
have you used the delete option on the GP Preferences to get rid of them
0
 
tetraukAuthor Commented:
completed by re-adding the mapped drive with a option to remove itself after teh gpo is removed.

once done, waited a day then removed gpo and bye bye drive....have reamapped drive with login scrip.....thank god for .bat files....
0
 
tetraukAuthor Commented:
:-)
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now