Solved

Deploying MSI via group policies

Posted on 2012-03-19
8
761 Views
Last Modified: 2012-03-21
I want to deploy a software package [MSI], via group policy.

Right now it is:  assigned / Computers in a test OU.

When I apply this does the test computer have to be rebooted for the GPO to take affect?

Windows Server 2008 R2.

Thanks
0
Comment
Question by:techgenious
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
8 Comments
 
LVL 3

Expert Comment

by:IT-Shrek
ID: 37739563
no, just wait some time or force manual refresh with gpupdate /force in a cmd window.
0
 
LVL 22

Expert Comment

by:chakko
ID: 37739616
You can do a gpupdate /force and then it should install during the boot/Windows startup process (before the logon screen appears).
0
 
LVL 47

Expert Comment

by:Donald Stewart
ID: 37739617
GPO software installs *Only* take place during the startup process.

So yes you will need to reboot
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:techgenious
ID: 37739647
can I do a automatic install without rebooting using a batch file:

msiexec.exe \\xyz.com\gpo$\Inventory\TEST.msi /qn /norestart

Put it in the GPO, and this will push out automatically to all the servers I have in an OU, without user intervention and server reboots?
0
 
LVL 47

Expert Comment

by:Donald Stewart
ID: 37739795
Would you be using the .bat as a logon script ?

Do users have admin rights ?
0
 

Author Comment

by:techgenious
ID: 37740174
Do I need more than this?
Yes Administrative rights, etc.

msiexec.exe \\xyz.com\gpo$\Inventory\TEST.msi /qn /norestart
0
 
LVL 3

Accepted Solution

by:
BigRedRPB earned 200 total points
ID: 37742025
To do it via a batch file and without rebooting (as long as your users have admin rights), you can use Group Policy Preferences to create a scheduled task.

1. Create the task in GPP (of course, set the start time of the task a bit in the future)
2. Either do a GPUpdate on the machine or wait until policy refreshes, which is 60-90 minutes by default, I think.
3. The task should fire off the install.  You can also set the task to run only once and to delete if it does not need to run again.

See here for more details:  http://technet.microsoft.com/en-us/library/cc770904.aspx

Keep in mind, the cleanest way to do this is by assigning the software via standard Group Policy Software and restarting.  That makes it easier to remove in the future as you can simply remove the assignment and have Group Policy uninstall the software.  You 'could' actually do both the assignment and the scheduled task to have the best of both worlds.  That 'should' work, but you may want to test before rolling it out to 1000 users.  :)
0
 

Author Comment

by:techgenious
ID: 37742211
It has to be done via PowerShell Script, so I was able to do the MSIE command which I have to embed into PS.

msiexec /i "\\xyz.com\gpo$\TestInventory\Test Inventory.msi" /quiet /norestart
That worked when I tried it @ the command line.

Now I have to put that into a PowerShell script which I have as:

$script = {
   
$args = "/i "\\xyz.com\gpo$\TestInventory\Test Inventory.msi"  /quiet /norestart
[diagnostics.process]::start("msiexec.exe", $args).WaitForExit()
   
}

I am going to try this script and see if it works from Power Shell ISE
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We recently had an issue where out of nowhere, end users started indicating that their logins to our terminal server were just showing a "blank screen." After checking the usual suspects -- profiles, shell=explorer.exe in the registry, userinit.exe,…
I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question