Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
VBScript mapping slowness issue

Answered VBScript mapping slowness issue

  • Friday, January 11, 2013 5:15 PM
     
     
    Sign In to Vote
    0

    We are mapping drives by calling the listed vbscript in the  user accounts in AD Users and Computers with placing the vbscript in the netlogon folder.

    This works fine and dandy with Windows XP machines.

    But we are having irregular results on our Windows 7 machines. Even though they all have the exact same image on them with the same drivers, we are seeing some of the machines taking an extremely long time to map the network drives. The vbscipt takes an extremely long time to run. I had sat and watched it in task manager for over an hour one time. And that still does not guarantee that all network drives get mapped.

    Sometimes I can get to the locations using the unc path during this time period and sometimes I cannot.

    I have a couple of users who reboot their computers several times or logs off and back on a few times to get the mapped drives to come up quickly.

    I also have a few users who have their drives dropped later in the day. But i also have plenty of users who do not have any problems with their Windows 7 systems.

    Most of the users can manually run the script and it will map their drives immediately, but a few who attempt to run the script manually still have the lag problem.

    I have tried the following: disabling UAC, enter into the registry a setting for enable link connections, sned LM & NTLM as NTLMv2 if negotiated, set to always wait for network, confirmed that Sharing and Secrity Model for Local Accounts is set to Classic-local user authenticate as themselves, removed IPv6, and Updated both BIOS and the NIC drivers.

    Could there be a difference in how a vbscript should be written for Windows XP and Windows 7 machines?

    I am now at a lose. Any ideas?

    Thanks,

    John

     

All Replies

  • Friday, January 11, 2013 7:19 PM
     
     
    Sign In to Vote
    0

    I don't think that his would be vbscript issue.

    Check your computers for "Netlogon" errors.

    Are all of the computers that take long time connected to same switch.

    Do they have same DNS server same DC, etc...

     
  • Friday, January 11, 2013 8:40 PM
     
     
    Sign In to Vote
    0

    I checked three of the computers and none of them have netlogon errors.

    None of the biggest offender computers are on the same switch; but there are some, where the issue is less drastic, located on the same switches as these bigger offenders. We have ones with issues and without issues on all the switches. And the only ones that are problamatic are the Windows 7 boxes. Windows XP is fine.

    We have 8 domain controllers in which several act as DNS servers. the environment is set up so that each computer contacts the closest DC, etc.  Since each of these computers are located across different subnets and in different buildings they are supposed to contact different DCs, DNSs. etc. I am not sure about DHCP, this might be governed at one location. But this might not be the case if they are on different subnets. (VLANs)

    Could this be a network type of problem?

    Thanks,

    John


     
  • Friday, January 11, 2013 9:35 PM
     
     
    Sign In to Vote
    0

    Given the fact the computers are running windows 7 they must be newer machines.

    So i can not see that the logon script should run longer then a minute.

    I do think that this would be some kind of a network issue.

    http://support.microsoft.com/kb/968429?wa=wsignin1.0

    For the computers that don't work compare the DNS Server, Default Gateway verusus a computer that works in the same subnet.

    Try mapping via IP instead of Name, and if that works then you may have problem with the DNS.

    Try deleting the network drives first before mapping.

     
  • Wednesday, January 16, 2013 12:02 AM
     
     Answered
    Sign In to Vote
    0
    The issue was that the server admins never removed some old servers from the DFS settings. They cleaned those servers out and it is all working now.
    • Marked As Answer by YoungJediKnight Wednesday, January 16, 2013 12:02 AM
    •  
     
  • Wednesday, January 16, 2013 2:52 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,


    Glad to hear you have found the solution. Thanks for sharing. We really appreciate your time and efforts. Hope your experience will help other community members facing similar problems.


    Thanks,


    Vincent Wang
    TechNet Community Support