I have seen incorrect path statements in the environment settings cause vbs
login scripts to bomb out. Compare the path statements on the ones that work
to the ones that don't. This would especially be indicative if it is a it
used to work and now it doesn't situation. Software installs often
If you are going to stick you toe into Exchange, there are some useful
resources at Swynk.com
-Original Message-
From: Rachui, Scott [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 08, 2002 6:22 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Exchange question (not AD)
The tool you
Have any changes been made to security of these workstations that would
prevent VB scripts from executing? Have any changes been made to the
workstations?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike Tonazzi
Sent: 07 January 2002 06:17
To:
If I double click the vb script (after I have been logged in) it runs
wonderful. The only thing is the script is not executed during the login
process (as it is defined in the group policy). The script is saved in
the \\server\netlogon file://\\server\netlogon directory, but I have
also
