Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

logon script (.vbs) partly working

Status
Not open for further replies.

felix27

Technical User
Jul 22, 2004
23
AT
hello,

i have a weird problem. i am using a vb-script as logon script in my AD.
network drives and printers are mapped during logon.
this has been working fine for a while.
now the script sometimes runs, sometimes not.
if i start the script again after logon by hand, everything get´s connected as expected.

therefore i am thinking about any kind of timing problem during the logon which leads to the result that the wscript.exe process is not started.
users are logging on to windows 2003 terminal servers with citrix installed.

has anybody encountered a similar problem?

kind regards,

Felix

 
Yes we had the same problem on a 2003 ad network it turned out to be a network speed issue but was resolved by changing the settings on the problem pc's NIC changing them for Auto negotiate to 100 full duplex and re starting them
 
Have you run RSOP.MSC on the offending PC's to make sure that the policies you assigned are being pushed? Once you know that, then the possibility could be that the Policies are not being applied due to a "speed" issue. Have you tried turning on the "Group Policy slow link detection"? This could be happening if your sysem is dropping below 500Kps. Not unheard of in a busy domain....
 
still could not figure out why the script is running sometimes and sometimes not.
test with rsop difficult beacause i am not able to reproduce the error.

at the moment i have entered the script as logon script for each user in the properties of the user and disabled the policy. this seems to be working until now.

it is not a solution but i had to get the script running.

it really seems to be a performance problem with the policy.
thanks for your tips.

 
Do you have more than one DC? Sounds to me like you may have problems with replication if you do. I'd dig a little deeper into your DC logs to make sure all replication is taking place.

If you are in a single server environment, then I'd agree with turning off Slow Link Detection. There is also a setting to wait for the network to initialize before running scripts, you may need to look at that as well.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top