Active directory authentication delay?

[Jonathan A]

Hello all, hopefully I can relate my question in a format
that makes sense, here goes nothing...

I'm working on a script (batch file mostly) to uninstall
Nav 7.5 from 1000+ workstations. Unfortunately, the
requirements for the uninstall batch file to run properly
are:
a. must run the files from the local HD
b. must be a local admin (our users aren't)

In attempt to accomplish this, I've done the following
1) added a command in the autoxec.bat to copy the files
from a network source and extract the files locally
2) use wscript to launch another batch file under a
different domain user's credentials (this user has the
necessary rights to uninstall NAV.)

The problem I'm having is that *intermittently*, the
command to login the alternate user and call the second
batch file will hang up and prompt for a password (even
though it is specified in the parameters of the call) My
thoughts are that this may be occurring due to an
inability of Active Directory to authenticate quickly
enough when the script runs the command. I've tried
adding a sleep command prior to the call that uses the
alternate user to ensure that other background events
have finished, but this doesn't appear to have helped. In
every instance where I saw a failed login/prompt for
password, by logging out/logging in the script was able
to successfully authenticate and run.



Here's what I'm running in the autoexec.bat


call [network source]\removnav.bat

Echo Preparing to run Symantec Anti-virus upgrade, please
wait.
c:\temp\nonav\sleep.exe 30

setlocal
path=c:\temp\nonav;%path%
c:\temp\nonav\wscript c:\temp\nonav\runnav.vbs
domain\username password c:\temp\nonav\nonav.bat
endlocal



I realize there are probably several different directions
to attack this issue. For starters, I'd like to know what
it is that is causing the inability to login for the
second user, and then come up with alternatives. Thanks
for the help!

-Jonathan

 

[Herb Martin]

Hello all, hopefully I can relate my question in a format
that makes sense, here goes nothing...

I'm working on a script (batch file mostly) to uninstall
Nav 7.5 from 1000+ workstations. Unfortunately, the
requirements for the uninstall batch file to run properly
are:
a. must run the files from the local HD
b. must be a local admin (our users aren't)

In attempt to accomplish this, I've done the following
1) added a command in the autoxec.bat to copy the files
from a network source and extract the files locally

Why are you still using autoexec.bat? Are these machine
Win98 or NT?

Under Win2000+ (this is an AD list you posted) using
Group Policy and the STARTUP script would be preferable.

Or perhaps building and using a GPO Software package.
IF Nav doesn't have an MSI file you might even build one.

2) use wscript to launch another batch file under a
different domain user's credentials (this user has the
necessary rights to uninstall NAV.)

The problem I'm having is that *intermittently*, the
command to login the alternate user and call the second
batch file will hang up and prompt for a password (even

You really shouldn't be coding passwords into script files
anyway.

Running as a Startup script would solve this whole line
of problems.