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
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