Network and Classroom Management Thread, How to use the quiet silent switch to deploy software through group policy in Technical; This may well be a case of summer holiday brain meltdown but hopefully you will be able to assist.
12th August 2008, 06:20 PM #1
- Rep Power
How to use the quiet silent switch to deploy software through group policy
This may well be a case of summer holiday brain meltdown but hopefully you will be able to assist.
I want to install a program on PCs when the computers boot up.
I have a file "setup.msi" that I added to group policy.
The setup requires admin privileges to install so I set it to run from the "Computer Settings" section.
However, event viewer reports that it fails.
I have a feeling that this is because it needs to be told to run in silent mode.
If I log in as an admin and run "setup.msi /qn" then it installs perfectly
I have read about using Orca/WinInstallLE to repackage or create a transform but it seems a really convoluted way to do it.
Am I missing something obvious? If not then what is the best/most reliable way to do it?
12th August 2008, 07:04 PM #2
MSIs should install automatically once workstations have picked up the latest policies. Have you checked the event log (on the workstations) as to why it's failing?
I presume you've placed the MSI (and other files, if applicable) within a share - \\servername\sharename and when deploying the MSI, that you specify the UNC path and not use a local path. \\servername\sharename\msi_file.msi
If all else fails, you could create a startup script which'll install the MSI.
Then remove the script once it's installed on all workstations.
12th August 2008, 07:33 PM #3
Noooooo no no. If you can install it in quiet mode yourself, and it does it properly, this means that the package author has done a Good Job. When you then send it out through group policy it does exactly the same thing, so there is some other problem and only your event logs will help. As Michael says check that you have provided a network path to the package not a local path, this is a common gotcha. Or it could be something like the machine doesn't have permission to see it, etc.
Originally Posted by thom
Thanks to powdarrmonkey from:
13th August 2008, 11:09 AM #4
Whats the MSI error and what is the software called?
13th August 2008, 04:22 PM #5
Thanks to thom from:
powdarrmonkey (13th August 2008)
13th August 2008, 06:31 PM #6
That's useful to know, haven't encountered that before. Although I've never deployed non-EN software before.
By gmiller in forum Hardware
Last Post: 30th November 2009, 09:56 AM
By FN-GM in forum Wireless Networks
Last Post: 2nd August 2008, 01:22 AM
Last Post: 26th June 2008, 09:00 PM
By Lithium in forum Windows
Last Post: 19th February 2008, 11:03 PM
By garym2000 in forum Windows
Last Post: 19th February 2008, 09:18 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)