Sign in with
Sign up | Sign in
Your question

Startup scripts not working

Last response: in Windows 2000/NT
Share
April 27, 2005 4:53:20 PM

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Hi all,

I have a startup script that was working fine for a while. Now all of a
sudden it doesn't work anymore. The only thing that I know of that changed
was the server that the .exe file is on. It is now a virtual server.

Here is a sample of the script that I have that used to work.

Option explicit
Dim oShell, FSO, file1,

Set oShell = WScript.CreateObject("WScript.Shell")
Set FSO = createobject("Scripting.filesystemobject")

file1 = FSO.FileExists("c:\Program Files\PatchLink\Update Agent\dagent.exe")

If file1 = True Then
oShell.Run "runas /user:D omain\username ""\\servername\setup.exe -s"""
WScript.Sleep 1500
oShell.SendKeys "password~"
Else
End If

Set FSO = Nothing

WScript.Quit
Anonymous
April 28, 2005 3:15:46 AM

Archived from groups: microsoft.public.win2000.active_directory (More info?)

try to run that script from a logged on user to see what is happening.


--
Andrei Ungureanu
www.eventid.net
Free Windows event logs reports
http://www.altairtech.ca/evlog/

"Jason" <Jason@discussions.microsoft.com> wrote in message
news:9CA3C3C2-BF09-47A5-89A8-3BDA301B5C82@microsoft.com...
> Hi all,
>
> I have a startup script that was working fine for a while. Now all of a
> sudden it doesn't work anymore. The only thing that I know of that
> changed
> was the server that the .exe file is on. It is now a virtual server.
>
> Here is a sample of the script that I have that used to work.
>
> Option explicit
> Dim oShell, FSO, file1,
>
> Set oShell = WScript.CreateObject("WScript.Shell")
> Set FSO = createobject("Scripting.filesystemobject")
>
> file1 = FSO.FileExists("c:\Program Files\PatchLink\Update
> Agent\dagent.exe")
>
> If file1 = True Then
> oShell.Run "runas /user:D omain\username ""\\servername\setup.exe -s"""
> WScript.Sleep 1500
> oShell.SendKeys "password~"
> Else
> End If
>
> Set FSO = Nothing
>
> WScript.Quit
>
>
May 2, 2005 9:04:03 AM

Archived from groups: microsoft.public.win2000.active_directory (More info?)

I can run it as a logged on user and it works fine. I also tested as a local
startup policy using gpedit.msc and that works too. It seems that it just
won't work with the AD startup settings.

"Andrei Ungureanu" wrote:

> try to run that script from a logged on user to see what is happening.
>
>
> --
> Andrei Ungureanu
> www.eventid.net
> Free Windows event logs reports
> http://www.altairtech.ca/evlog/
>
> "Jason" <Jason@discussions.microsoft.com> wrote in message
> news:9CA3C3C2-BF09-47A5-89A8-3BDA301B5C82@microsoft.com...
> > Hi all,
> >
> > I have a startup script that was working fine for a while. Now all of a
> > sudden it doesn't work anymore. The only thing that I know of that
> > changed
> > was the server that the .exe file is on. It is now a virtual server.
> >
> > Here is a sample of the script that I have that used to work.
> >
> > Option explicit
> > Dim oShell, FSO, file1,
> >
> > Set oShell = WScript.CreateObject("WScript.Shell")
> > Set FSO = createobject("Scripting.filesystemobject")
> >
> > file1 = FSO.FileExists("c:\Program Files\PatchLink\Update
> > Agent\dagent.exe")
> >
> > If file1 = True Then
> > oShell.Run "runas /user:D omain\username ""\\servername\setup.exe -s"""
> > WScript.Sleep 1500
> > oShell.SendKeys "password~"
> > Else
> > End If
> >
> > Set FSO = Nothing
> >
> > WScript.Quit
> >
> >
>
>
>
!