Problem with mapped drives & grou policy

Spammeh · 15 Sep 2010 at 16:50

I realise that this probably isn't the forum to post this, but I know there's a lot of techy minded people who might be able to help.

In short we have a NAS which we're going to use as slow storage for our users on the domain that we would like mapped as their P: drive on their accounts.

Currently the shares are set up so that the drive would need to be mapped as follows:

\\nas01-MC\%username%

This seems to be working for some users within varying Active directory OU's but for others, does nothing

Currently, in a test OU I've got a .cmd running in the logon scripts part of group policy containing this line:

net use P: \\NAS01-MC\%username%

as far as I'm concerned as long as they have permissions over the relevant folder then that should work.

e.g.
AD username: jbloggs
NAS Share: \\nas01-mc\jbloggs

Is there anything I can run to check why this isn't running or can anyone point me in the direction as to why this isn't working? The particular policy that this script is in is listed at the top of the GP inheriance tab for the specific folder so I honestly cannot get my head around this.

Thanks for any help ladies and gents!

Spammeh · 15 Sep 2010 at 17:01

When logged in as the user, I can easily browser to the web front end of the machine, so I know its not a DNS issue. The permissions have been checked on the box and thats fine as you can log on the front end with the domain username and password without an issue.

Spammeh · 15 Sep 2010 at 17:05

Oh, and once logged on as the user you can map the share manually and it works using \\nas01-mc\<username> without any issues, so its got to be something to do with the group policy side of things

Spammeh · 16 Sep 2010 at 14:23

despite the other users in the the same OU having the same policies applied, theirs maps fine. i'm completely out of ideas! The other users in that OU have had the 'p' drive mapped for a few months now, and have had no issues.

I set up a test OU with only that policy set to apply to it and got the following error:

Code:

C:\Users\yeboah>gpupdate /force
Updating Policy...
User policy could not be updated successfully. The following errors were encount
ered:
The processing of Group Policy failed. Windows attempted to read the file \\XXX\SysVol\XXX\Policies\{771FC3E5-FE2B-4668-A825-844
7F43538B5}\gpt.ini from a domain controller and was not successful. Group Policy
 settings may not be applied until this event is resolved. This issue may be tra
nsient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller
 has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.
Computer Policy update has completed successfully.
The following warnings were encountered during computer policy processing:
The Group Policy Client Side Extension Software Installation was unable to apply
 one or more settings because the changes must be processed before system startu
p or user logon. The system will wait for Group Policy processing to finish comp
letely before the next startup or logon for this user, and this may result in sl
ow startup and boot performance.
To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f
rom the command line to access information about Group Policy results.

This is v. bizzare. I have done a gpresult and it shows that the policy with the login script in is applying to the user account

Spammeh · 16 Sep 2010 at 16:55

I have currently only tested this on a windows 7 machine (as its the standard around our place) but as different logons work with the P drive then I cant believe it'll be a client think surely.

I've left work now so I'll definately give that ago to tomorrow mrbios, cheers mate

Spammeh · 17 Sep 2010 at 09:37

Eulogy said:
But you still haven't answered the question regarding having tried the AD properties as I mentioned in my previous post.

We have home drives mapped from within the AD properties so this isn't possible to use hense why I've been doing it using a logon script.

Edit: I thought I'd mention if I do map the drive via the AD properties it does work fine.