[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 619
  • Last Modified:

Why does my login script not complete on new machines?

We recently upgraded several HP Vectra Machines (very old) with new Dell Optiplex 755 machines.  Since upgrading, on several of the machines we notice a problem.  The login script does not run every day, or it does not run completely everyday.  On some machines it works perfectly, on others it does not map all of the drives.  It maps some, but not all.  There seems to be no logic to the problem, but it started occuring on the new machines.  Any suggestions out there?

All systems, new and old ran Windows XP SP 2, and our network is a Windows 2003 domain with 2 DCs.

Thanks.
0
nebfis
Asked:
nebfis
  • 3
  • 2
1 Solution
 
tsw2000Commented:
just wondering if your script is in a vbs or batch file

if it is a batch file you may want to change your script to

net use z: \\computer\share /PERSISTENT:YES

using GPO, you should put the logon script in \\dc_name\netlogon\scripts

Ensure everyone have read permission to the script
0
 
nebfisAuthor Commented:
It is a batch file, and located in the dc_name\sys vol\domain_name\scripts folder
0
 
Kieran_BurnsCommented:
Are the client workstations using DHCP or static IP addresses?

Have you configured the DNS zone on the new clients correctly in the TCP properties?

If it is intermittant I can't help but think it is a name look up issue and related to DNS in some way.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
nebfisAuthor Commented:
The clients are using DHCP, and I joined them to the domain as created.  If it helps, they were cloned using Ghost and ghostwalker.  I went through the mini setup, so I thought I wouldn't run into DNS issues, but I am open to any possibility.
0
 
tsw2000Commented:
Hi, I suspect that your client network connection is not established properly before they logon and this will not trigger the logon script.
Try to create a GPO to disable the fast logon optomization for the XP clients.

Disable Fast Logon Optimization
http://technet2.microsoft.com/windowsserver/en/library/7d2fc477-5a3a-42b9-94e3-0f0848df2ab91033.mspx?mfr=true
0
 
nebfisAuthor Commented:
Thanks for your help tsw, that appears to have solved the issue.  I'll repost if the issue reappears.  Looks good now though.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

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