Training: https://www.youtube.com/watch?v=zadvca6LlzA

Troubleshooting Series: http://deployhappiness.com/top-10-ways-to-troubleshoot-software-deployment/

Installation can only happen on a reboot or logon and only if the GPO was downloaded beforehand. In a default environment, it is easiest just to reboot twice.

If you deploy the software to the user side (assigned or published), the GPO must be linked to an OU containing users (or you have to enable loopback).

When creating a GPO to deploy software, always choose Advanced.

1. Create a network share called Software
2. Set the permissions on the share
   1. Network
      1. Administrators → Full Control
      2. Authenticated Users → Read
   2. Filesystem
      1. Administrators → Full Control
      2. Authenticated Users → Read & Execute, List, Read

To install software in a Computer OU, the computer must have access to the share.

The Authenticated Users group includes computers.

Open both Group Policy Management Console gpmc.msc and ADUC.

Computer Configuration → Policies → Administrative Templates → System → Group Policy

• Specify startup policy processing wait time → 90

Computer Configuration → Policies → Software Settings → Software Installation

• Right-Click → New → Package → <browse via network to .msi> → Advanced
  • Advanced will allow editing all options later
  • Assigned installs to Computers
  • Published allows Users to install

In an administrative command prompt:

gpresult /r /z

Use /s to specify a remote computer.