[konchif]

Hi, I am intrested in writing a script that allows to me install software on any machine with a Restricted User logged on.
I built an OU and added a machine to it. Then I added a GP and edited it on LOCAL MACHINE - Startup - script:

123.bat file in script directory

call \\server\program file\program\setip.exe

I can see that the machine is running the policy but it is not installing it.
What shoud I do?
Thank you

[Dumber]

first, check you're eventlogs. (client side)

[konchif]

I don`t see nothing related
BTW, scriped is replicated in AD
SE?

[Dumber]

check youre client with gpresult..
check logs..
etcetc.

there must be something about errors if it doesn't work..

[konchif]

Hi, I seems , i found something in Logs:

The GP client -side extansion Application Managment was passed flages(1) and reterned a failure status code of (1612)

previose was event 108

that sends me to the first and tells that:

"Verify that the source exists and that you can access it"

as I told before I have full access to the installation folder and from a machine its running OK, the batch file is very simple:
"call \\server\program files\program\setup.exe"

any idias, please?
Thank you

[Dumber]

"Verify that the source exists and that you can access it"

as I told before I have full access to the installation folder and from a machine its running OK, the batch file is very simple:
"call \\server\program files\program\setup.exe"

but does the batchfile work when you run it manually?

maybe this will work better:

call "\\server\program files\program\setup.exe"

[guyt]

It's not enough that YOU have access to the \\server\program files\program\setup.exe file.
As it is a startup script, it is executed in Local System account of the computer it runs on context.

The easy way to check is by running at the client machine:

at 12:07 /INTERACTIVE "cmd.exe"

(change the time so it will run in a minute after you submit the job)
and trying to access the file \\server\program files\program\setup.exe manually. If you get "Access denied" the problem is the permissions (the cmd will run under Local System account)