I'm dumb with scripting....

[Clockworks]

I'm trying to create a number of mapped drives for our company's users. Being a total newbie to this, I decided to keep it as simple as possible with a batch file. Here's the code:

@echo off
net use H: /delete
MD \\ruffles\rnfile\Users\%USERNAME%
net use H: \\ruffles\rnfile\Users\%USERNAME%

net use I: /delete
net use I: \\ruffles\rnfile\Working 

net use J: /delete
net use J: \\ruffles\rnfile\Reference

net use K: /delete
net use K: \\ruffles\rnfile\Music

net use L: /delete
net use L: \\ruffles\rnfile\Software 

net use M: /delete
net use M: \\ruffles\rnfile

net use N: /delete

net use O: /delete

When users log into their machines, it takes 10 minutes from password input to getting a desktop (only a black screen in the middle). When I log into their machines, I get it right away. This seems to only be happening in our Windows 7 machines. Even log produces this error:

The winlogon notification subscriber <GPClient> is taking a long time to handle notification even (startshell). - Error 6005

The winlogon notification subscriber <GPClient> was unavailable to handle a notification event. - Error 6006

Booting into safe mode works though....

[SYNACK]

Do your users have create permissions for the folder you are MDing to?

It does not look like your script has issues, from the error it looks more like you have a corrupted policy or something. Sometimes the old ones used for XP can have weird settings and such left in them that break 7. You should be using WMI filtering and a seporate policy for 7 if you are not already for the most reliable implementation.

[cbrasga]

Sounds like they do not have proper permissions to one or more shares. Additionally, if you have their Active Directory user accounts setup with a Home Directory and Drive Letter you could just use "NET USE /HOME" instead of "net use H: \\ruffles\rnfile\Users\%USERNAME%".

[nephilim]

Net Use home is much better in this case if a drive letter and home drive is already set, however they also need create permissions for the script you're using.

We had a similar issue on ours with our 2008R2 and W7 set up, once we set create permissions the problem went away and log in times dropped to around 20-30 seconds.