|
How about doing a workaround as in copying
the exe to local %windir% or some other variables? Perhaps an if not exist statement copy, if
not exist %windir%\test.exe copy %logonserver%\share\test.exe Since computer startup is run as system
which should have full access to your machine, this should overcome if it is by
any chance a permission issue… Thank you and have a splendid day! Kind Regards, Freddy Hartono Windows Administrator (ADSM/NT Security) Spherion Technology Group, For Agilent Technologies E-mail: [EMAIL PROTECTED] From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Crawford, Scott I would say that the computer’s
account doesn’t have access to the .exe. Where is the .exe
located? If its in the GPO’s script folder, it should have
inherited the Authenticated Users permission by default. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Creamer, Mark It is a vbs. Actually, though, I found out
a little more. I put a fresh server into the same OU, and rebooted. Turns out
most of the script is successful. The only part that isn’t is a line that
calls an executable file (.exe), which is also located in the same folder as
the vbscript. If I wait until the server is fully logged
in, the script runs the executable with no problem. If I leave it to the
startup script to run, it does not. I’m using the Exec method of the
wscript object, such as: Ws.exec(“myexecutable.exe”) Does that make sense? Thanks again, Mark From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Is it a vbs? If yes, have you tried
calling it from a bat file? Does it work if you do that? What you can do
depends on the outcome of that test. Deji From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Creamer, Mark I have a situation in which startup scripts assigned to
various OUs where different servers are located are not running. If I log in as
a domain admin, browse to the location of the script in the GPO assigned to the
OU where that server is located, I can launch the script with no problem. I’m having trouble figuring out why the script
won’t launch on its own. The only thing I’ve found so far in troubleshooting a
startup script is to look for an entry in the Application log with a source of
Userinit. However, I see no such entries. Can anyone think of what I might need
to look at? What permissions need to be enabled on the Policy itself, just in
case that’s the issue? Thanks, Mark
|
- Re: [ActiveDir] startup scripts not running James_Day
- RE: [ActiveDir] startup scripts not running Creamer, Mark
- RE: [ActiveDir] startup scripts not running Crawford, Scott
- RE: [ActiveDir] startup scripts not running freddy_hartono
- RE: [ActiveDir] startup scripts not running Creamer, Mark
- RE: [ActiveDir] startup scripts not running Creamer, Mark
- RE: [ActiveDir] startup scripts not running deji
