running batch file at logon via GPO

[mjsc]

Hello,

 

 

Can anyone offer advice on the following please ?

 

 

I am looking to run a batch file to install software at logon using GPO.

 

 

I do not wish to use msi, wrapper or zap files; the program to be installed is huge 15 gb and contains multiple msi's.

 

 

The batch file should run the following -

 

 

Img\Setup.exe /W /q /I Img\ECS 2015.ini /language en-us

 

 

I understand I can have a batch file containing "%~dp0Img\Setup.exe /W /q /I Img\ECS 2015.ini /language en-us"

 

 

Is this written correctly ?

 

 

I am also looking to run this batch file just once; can I incorporate within the batch file commands to check that the program has installed and prevent the installer from running again ?

 

 

Thanks...

[ITGuyWestMidlands]

Surely this would be more suited to a startup script. To install once you can use a common method of checking for the existence of a file. If it exists then skip otherwise install and create the file

[mjsc]

Hello and thank for your comments

 

I have discovered a method for checking for an install and then preventing another install.

 

However, I am running into problems with the batch file.

 

I want to install Autodesk Entertainment Suite Ultimate 2015

 

The batch file contains the following line -

 

 

 

"\\image1\dfs\dp\A\Autodesk ECS 2015\Img\Setup.exe" /qb /I "\\image1\dfs\dp\A\Autodesk ECS 2015\Img\ECS2015.ini" /language en-us

 

 

However the setup.exe part does not start. I cannot even see it running under task manager.

 

 

I used the create deployment tool to create the installation files.

 

 

Can anyone shed any light on this ? Are the switches right ?

 

 

Thank you...

[Foresthippy]

Have you tried running the script manually, with a pause at the end, so that you can see what has (or hasn't) happened?

[mjsc]

Yes. I see that within task manager the setup.exe starts, runs for about 3 secs and then stops. The same effect occurs when browsing to the setup.exe and running manually. Earlier in the week, I created a deployment image which existed on a desktop C: drive and this started and installed fine.

[ITGuyWestMidlands]

Do you have any software restriction policies in place? Try as a local admin