Map Network Drives do not always Map through Group Policy Site Policy

We have 3 different sites/locations and recently changed the way users map network drives.  Depending on what site a user is in, determines the logon script that will run.  However, sometime the logon script does not run.  WHY?

This is how I set it up...

In GPMC, I assigned a policy to each Active Directory Site.  For each policy I enabled a logon script for that site/location under...
User Configuration -->Windows Settings -->Scripts --> Logon
The logon script is a VBS.

For some reason, I have been getting calls from users saying that their drives are not mapping.  All of these users experiencing the issue are running windows XP.  Any Ideas?
LVL 1
ohmErnieAsked:
Who is Participating?
 
Kevin HaysConnect With a Mentor IT AnalystCommented:
have yet set this setting perhaps?  It seems as though the network may not be fully loaded when the user logs in.  Something that xp does, fast user login.

computer configuration/administrative templates/system/logon/always wait for the network at computer startup and logon.

0
 
bhnmiCommented:
Are you sure the script itself is not running? Or is it not completing due to an error?
0
 
ohmErnieAuthor Commented:
After looking in the event log -- application I can tell it is looking for the script, but failing with these errors:

Event Type:      Error
Event Source:      UserInit
Event Category:      None
Event ID:      1000
Date:            11/29/2007
Time:            1:58:40 PM
User:            N/A
Computer:      COMP
Description:
Could not execute the following script \\domain.com\NETLOGON\logon.vbs. Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.



Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1058
Date:            11/29/2007
Time:            1:58:15 PM
User:            domain\user
Computer:      COMP
Description:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=home,DC=domain,DC=com. The file must be present at the location <\\domain.com\sysvol\domain.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. ). Group Policy processing aborted.

Sometimes if the user restarts their computer a couple times it works.  do I have something configured incorrectly?
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

 
bhnmiCommented:
Is the script located locally at each site? and is each site the same domain or do you have a top level and child domains?
0
 
ohmErnieAuthor Commented:
Bhnmi, yes the script is located at each site and we only have 1 domain.

Kshays, I have not set that setting. Think that will help?
0
 
Kevin HaysIT AnalystCommented:
It wouldn't hurt that's for sure.  Instead of the user getting the login screen really quick they are forced until everything is loaded (network wise).  This is why some single site domains will not run login scripts.

This is for xp machines only.

Kevin
0
 
ohmErnieAuthor Commented:
Kevin, What will happen to laptops that users take off the network?  Will they still be able to logon when they are disconnected from the network?
0
 
Kevin HaysIT AnalystCommented:
Nothing should happen if you apply that policy.  It just waits for the network connections to get fully load(part of OS) is all.  Let me see if I can find you a link :)

0
 
ohmErnieAuthor Commented:
Kevin,

Any ideas why all of a sudden this issue is happening.  I know have about 10-15 people that are complaining about having to restart a couple times daily to maybe get the drives to map.  Nothing in my organization has changed accept possible windows updates that may have installed.
0
 
Kevin HaysIT AnalystCommented:
Not right off hand I don't.  It sounds like it just isn't making sure the network connections are available before running the login scripts.  Are the DC's replicated with each other (i assume so).  Are these the same people over and over?

Have you tried having them login to a different workstation or tried a different user on their workstation.
In the meantime I would probably create a small batch file that the user can just launch from their desktop to map their drives if the login scripts don't run.

There shouldn't be a permissions issue since it was all working fine before.

Have you ran netdiag /v on each dc assuming it's hosting dns service to test funcionality of your DNS service?

Kevin
0
 
ohmErnieAuthor Commented:
I now remember the following group policy setting was changed about the time the issue began...

Network security: LAN Manager authentication level

Symantec Endpoint Protection recommended changing it to: "Send NTLMv2 response only"
0
 
Kevin HaysIT AnalystCommented:
Ahhhhh.  I've got mine set at "send LM & NTLM responses"
Why did they suggest you just use NTLM responses for?
0
 
Kevin HaysIT AnalystCommented:
0
 
Kevin HaysIT AnalystCommented:
Much better explanation.

http://kb.iu.edu/data/atvn.html

Kevin
0
 
ohmErnieAuthor Commented:
Im trying to find the symantec article that recommended the change, but I cannot.  They probably removed it because it was causing problems.  I changed my setting back to default and will monitor for the next day or so and will post back.
0
 
Kevin HaysIT AnalystCommented:
Ok, good luck!

Kevin
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.