|
Mark, trying calling the vbs from a bat
file and see what happens. So, instead of putting the name of the vbs directly
as the startup script, put the name of a bat file. In the bat file, you just simply
need to do something like: Set ScriptPath=\\%logonserver%\NETLOGON Call %ScriptPath%\myscript.vbs Deji From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Creamer, Mark Good point Joe, I don’t know.
I’m basing the “not working” assumption on the end result not
being there, namely that the group has not been added to the RDP permissions.
However when I run it manually after logging in, the group is added. Next I tried adding a Do Until loop in the
script, looking for the executable to return a 0. That never happens. The
startup script runs forever J So based on that, and what you said, I guess
I need to ask the programmer (this app is home-grown) what error is thrown if
it doesn’t work. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe Ok, do you know for a fact that the exe
isn't running or is it simply not outputting an error if it fails? The reboot
issue I mentioned before appeared to be that shutdown wasn't being run, it was
running, it was hitting a device not ready error and wasn't outputting it. Once
I wrote a tool that definitely output errors when it ran into them, it was
crystal clear that something was preventing shutdown from working when running
in a startup script. It goes back to a type of error handling some programs
use. Some will encounter an error and dump out with any errors it doesn't know
how to handle. Some will dump out only with errors it knows how to handle. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Creamer, Mark It adds a group to the RDP permissions so
our off-hours operators have TS access into the servers. It’s in the
startup script because we wanted to make sure that if that ever got changed
manually by someone, a reboot would cure it From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe What exactly is the EXE doing? Not all
system services are not available when the startup script runs. For instance,
try to shutdown a server from a startup script. If you ever really need to do
that, let me know, I have an exe that will do it. Dean told me about issues
doing it and I got interested enough to look at it and it pissed me right off
so I "fixed" it. 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 Creamer, Mark
