Re: Startup Script from AD policy
- From: "david carvalho" <davidcarvalho@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 13 Jan 2006 02:30:02 -0800
Hi !
no luck yet.
the network drive mapping was my next step, but since I would be using
something like net use z: \\my.ip\netlogon and then run cmd /c z:\sdat.exe
/silent,
i would still have the problem because of the cmd shell. I'm new to wscript
so this
objnetwork.matnetworkdrive thing is new to me :), but I don't want to mess
with the registry.
What permissions should I have exactly ? I added the domain computers to the
netlogon folder permissions and share permissions, but I always get an
error "access denied".
code 8070005
source wshnetwork.mapNetworkDrive
I believe I've done the same in SYSVOL folder ?
What am I missing here ?
Thank you very much!
best regards
David
"Richard Mueller" wrote:
> Hi,
>
> This KB article explains the error:
>
> http://support.microsoft.com/?kbid=156276
>
> Per the KB, you need a new cmd.exe, plus registry changes. Another fix would
> be to temporarily map a drive. For example:
>
> Set objNetwork = Wscript.CreateObject("Wscript.Network")
> Set winShell = Wscript.CreateObject("Wscript.Shell")
> objNetwork.MapNetworkDrive "K:", "\\193.136.66.26\NetLogon"
> winShell.Run "cmd /c K:\sdat.exe /silent"
> objNetwork.RemoveNetworkDrive "K:", True, True
>
> --
> Richard
> Microsoft MVP Scripting and ADSI
> Hilltop Lab - http://www.rlmueller.net
>
> "david carvalho" <davidcarvalho@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:58307882-6CB4-4F7E-AA06-0941BC926B09@xxxxxxxxxxxxxxxx
> > hi thanks for the tip. i completly forget that.
> > I have another problem yet.
> > I want the sdatxxx.exe file to be executed, so I put it on the NETLOGON
> > folder.
> > I'm trying to use 2 versions without result:
> >
> > a) vbscript
> > Set winShell = wscript.CreateObject("wscript.shell")
> > winShell.run "cmd /c \\193.136.66.26\netlogon\sdat.exe /silent"
> >
> > b) batch file
> > @echo off
> > \\my.ip.address\netlogon\sdat.exe /silent
> >
> > I always get a "UNC paths are not supported. Defaulting to windows
> > directory"
> > and the software doesn't update
> >
> > How can I do this ?
> > thanks !
> > David
> >
> > "Richard Mueller" wrote:
> >
> >> david carvalho wrote:
> >>
> >> > Hi!
> >> > I'm writing a simple script under some "OU" policy, computer
> >> > configuration\windows settings\scripts
> >> > it runs ok when it's just to write something on screen for example. The
> >> > problem is tha I want to run an executable (when the machine starts up,
> >> > not
> >> > when users log in), and I can't place the executable on the same folder
> >> > as
> >> > the script so I can access it. I get a permission denied. So I put the
> >> > executable on the NETLOGON folder. But I guess that this folder is only
> >> > accessible after some domain user logs on. I get the same problem when
> >> > putting the executable under a shared folder with read/write
> >> > permissions
> >> > for
> >> > everyone.
> >> > How can I force the workstations to execute this remote file ?
> >> > thanks !
> >> > david
> >>
> >> Startup scripts run with System permissions on the local machine and with
> >> the permissions of the computer object in the domain. When I need to
> >> allow a
> >> startup script access to a shared folder, I grant permissions to the
> >> "Domain
> >> Computers" group.
> >>
> >> --
> >> Richard
> >> Microsoft MVP Scripting and ADSI
> >> Hilltop Lab - http://www.rlmueller.net
> >>
> >>
> >>
>
>
>
.
- Follow-Ups:
- Re: Startup Script from AD policy
- From: Richard Mueller
- Re: Startup Script from AD policy
- References:
- Re: Startup Script from AD policy
- From: Richard Mueller
- Re: Startup Script from AD policy
- From: Richard Mueller
- Re: Startup Script from AD policy
- Prev by Date: Re: Mshsnapin (part 1): usage of mshsnapin commands.
- Next by Date: Re: How to impersonate as a different user? (MSH)
- Previous by thread: Re: Startup Script from AD policy
- Next by thread: Re: Startup Script from AD policy
- Index(es):
Relevant Pages
|
