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

GPO Drive maps inconsistent

New Server

New Domain

New Users

New GPO

There are from 2-6 drive maps that occur based on Security Groups.

On one of the drive maps that is for every user, some get it mapped, some don't. For the ones who don't get it mapped, they can access it through the path (\\Server\Share) no problem.

So annoying.

It's almost as it tries to map before the network connection is ready.
0
MJCS
Asked:
MJCS
  • 4
  • 2
3 Solutions
 
Cliff GaliherCommented:
This is very likely related to one (or more) of the other questions you've asked recently. You can't expect mapped droves to work if DNS is timing out, for example. Honestly, after looking back at the number of questions you've asked this last week, my opinion is that you are spreading yourself way too thin.

There is more than one right way to do things. But for every right way, there are three wrong ways. And one bad decision early can have a ripple effect and the more you build on.a shaky foundation, the harder it'll be to go back and fix. You need to concentrate on ONE problem at a time. Don't try to fix ten things at once. And based on some of your questions, it may be time to call in some extra help. The cost of one consultant will quickly pay for itself in time saved and long term stability vs having a broken implementation.
0
 
jhyieslaCommented:
The above expert is probably right, especially if you have DNS issues as well. But GPO's don't always work either. And he's right in that there is more than one way to do most things in Windows. For example, in our environment we wrote a simple login script that everyone runs. The login script is responsible for checking for the existences of a mapped drive and then mapping it if it isn't there. This works about 99.999% of the time. Why it's not 100% is anyone's guess.
0
 
MJCSAuthor Commented:
It appears that the main drive map issue that I'm having is related to conflicts with existing drive letters or leftovers from the previous domain.

If there is an issue with DNS, it appears to be minor in nature.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
jhyieslaCommented:
Not sure how to remove the drive letters via a GPO, but in the script we run we have the following logic:

We have an IF statement that goes like:
if not exist "t:\sharename\" then goto CreateShare

Then in the goto statement we'd have:

:CreateShare
If exist "t:\" net use t: /delete
net use t: \\servername\sharename

And then we breakout to another subroutine in the script.  But something like this may solve your issue. The first statement checks for the presence of the mapping you want and if it exists we just continue on.  But it the share mapping don't exist we to to the subroutine where we look for that letter mapped to anything and then delete it and then create the share we want. After this we goto the next statement in the main routine. We have done this for years without issue
0
 
MJCSAuthor Commented:
I like your solution jhylesla. However, the number of affected machines were small enough that I just resolved the issue manually.

To reiterate, there were two causes for the inconsistent drive maps.

Reason #1: Several stations had card readers attached. Several of the drive maps were low enough in the letters that these reserved drive letters for the card readers conflicted with the drive maps letters. I had to look closer at the individual computers in order to determine this because the card reader drives did not shop up in Windows Explorer by default because they were currently empty.

Reason #2: Several stations had had manual drive maps to the previous server which were still in place after leaving the previous domain and joining the new. These showed the right drive letter but were labeled differently and gave a "not accessible" type error message.
0
 
MJCSAuthor Commented:
I should have added:

To resolve Reason #1, I changed the card reader drive letters to non-conflicting letters.

To resolve Reason #2, I manually disconnected the old drive maps and then new ones remapped once the computers were rebooted.
0
 
MJCSAuthor Commented:
Discovered both the cause and the resolution myself.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now