GPO for software installation questions


I have created a GPO to install Microsoft SSO for Office365

In the GPO i have added a Software Installation under Computer COnfiguration and pointed it to a shared folder with the .msi file to install.

Couple of questions:

1)  Will this GPO install the .msi file from the shared drive or as part of the software installation option does it copy the file to all the Domain Controllers?

2)  Will it install as a quiet install or if not how do i perform this?

3)  I've added the GPO to a single test OU, with 1 laptop assigned.  When i perform a gpresult on the laptop it shows that the GPO is assigned but it doesn't actually do anything, it doens't install the software.  Am I missing something?

Thanks in advance
Who is Participating?
Jeremy TyreConnect With a Mentor Distributed Computer Systems AnalystCommented:
1) I am not sure if there is a better way of doing this but it could be placed on a shared folder on each DC.  I would not be worried about it causing the network to go down, unless there are other issues involved.  I have seen it pushed to 3000+ from a single server without an issue.  Of course, you push it at night when no one is at work.

2) Here is how to modding the 2013 installation:

Here is info on 365 Click-to-run installation customization:

msiexec is used to install .msi files.  You can get the switches by typing msiexec /? in cmd.  Here is the help output in Windows 7:

Windows ® Installer. V 5.0.7601.17514

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
      </package | /i> <Product.msi>
            Installs or configures a product
      /a <Product.msi>
            Administrative install - Installs a product on the network
      /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
            Advertises a product - m to all users, u to current user
      </uninstall | /x> <Product.msi | ProductCode>
            Uninstalls the product
Display Options
            Quiet mode, no user interaction
            Unattended mode - progress bar only
            Sets user interface level
            n - No UI
            b - Basic UI
            r - Reduced UI
            f - Full UI (default)
            Help information
Restart Options
            Do not restart after the installation is complete
            Prompts the user for restart if necessary
            Always restart the computer after installation
Logging Options
      /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
            i - Status messages
            w - Nonfatal warnings
            e - All error messages
            a - Start up of actions
            r - Action-specific records
            u - User requests
            c - Initial UI parameters
            m - Out-of-memory or fatal exit information
            o - Out-of-disk-space messages
            p - Terminal properties
            v - Verbose output
            x - Extra debugging information
            + - Append to existing log file
            ! - Flush each line to the log
            * - Log all information, except for v and x options
      /log <LogFile>
            Equivalent of /l* <LogFile>
Update Options
      /update <Update1.msp>[;Update2.msp]
            Applies update(s)
      /uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
            Remove update(s) for a product
Repair Options
      /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
            Repairs a product
            p - only if file is missing
            o - if file is missing or an older version is installed (default)
            e - if file is missing or an equal or older version is installed
            d - if file is missing or a different version is installed
            c - if file is missing or checksum does not match the calculated value
            a - forces all files to be reinstalled
            u - all required user-specific registry entries (default)
            m - all required computer-specific registry entries (default)
            s - all existing shortcuts (default)
            v - runs from source and recaches local package
Setting Public Properties

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
Jeremy TyreDistributed Computer Systems AnalystCommented:
I am looking for some KB articles to help you out, but here is the quick and dirty from my early morning brain functions.

1) The .msi file and all supporting files should stay located on the shared drive and run from there.  The GPO install only points to the location and the computer goes and grabs it.  It should not copy the files to all the DCs.

2) It will be quite if the .msi file is configured that way or if the proper switches are used. I am trying to locate more percise information on this and will get back to you.

3) More information is needed.  Did you do a gpupdate /force and restart a couple of times.  Also, try multiple computers with different configurations.  The laptop may have something on it that might prevent the installation.  Also, give the DC time to push the .msi.  I have seen this take a couple hours even if it is forced.
WolfAuthor Commented:
Thanks for the help

1)  How do we get the .msi pushed to all the DC's?  The file is approx 4mb and will be pushed out to all systems, approx 1200 computers.  I don't want all going to the shared folder and breaking the network.

2)  How do i configure the msi or what is the correct switch?  I've just added the file without anything extra
Do you use dfs or have you looked at storing these files on domain.local\sysvol\domain.local?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.