PC Power Down, Energy Saving

Reducing wasted elctricity and consequential carbon (CO2) emissions

User Guides

<< 4. MSI Deployment Index
5. Troubleshooting Troubleshooting MSI deployments

5.1. Introduction

Various points during the GPO push of the MSI package may fail. In the majority of cases, the failure is due to incorrect permissions for the computer account to access the GPO, defined package, physical package, or authentication problems. Also, an improperly configured MSI setup file may cause installation failures.

5.2. GPO

Problem: You do not see the message box at startup stating the MSI package is being installed.
Resolution: There are a few possibilities that can contribute to this. Check to ensure the target machine is located within the OU where the GPO containing the software deployment is applied. Also, check the permissions on the OU and GPO to ensure Domain Computers (or Authenticated Users) have both READ and APPLY GROUP POLICY rights. Also ensure the defined package object within the GPO has the appropriate rights for Domain Computers. Also, your GPO definition may not have fully replicated through the Active Directory domain. Either wait a while for replication to occur, or run gpupdate.exe /force at the command line of one client to test it's working.

Problem: Cannot create GPO object.
Resolution: Ensure that the account you are using to run the Active Directory Users and Computers application has sufficient rights to create Group Policies. Usually, you must be a member of the Group Policy Creator Owners group explicitly or implicitly by nested groups. See your local OU administrator to verify your group membership and to delegate the ability to create Group Policies.

Problem: You updated the MSI installer file, but machines do not get updated automatically.
Resolution: You must redeploy the Package Object within the GPO. Right-click on the Package Object and select All Tasks\Redeploy Application –OR- use the built-in versioning techniques of Package Objects (see Microsoft Knowledge Base for more info on using versioning of Software Package Objects).

Problem: Other administrators cannot redeploy the software or edit the GPO. Only the original creator or Domain Administrators can.
Resolution: Check the security permissions on both the Package Object and the GPO to ensure intended administrators can Read/Write/Modify the objects accordingly.

Problem: The Application Event Viewer indicates errors that the MSI package installation failed with an error ‘Package source not located’.
Resolution: This indicates that the local computer read and tried to apply the GPO and MSI Package object, but could not access the physical .MSI file. Check the permissions on the share containing the MSI file to ensure Domain Computers (or Authenticated Users) have at least READ access rights. It is also possible that the Package Object was created using the physical path (C:\Apps\Installer.MSI) instead of the UNC path (\\server\share\Installer.MSI). Also, the Package Object may reference the FQDN of the share path (\\server.domain.com\share\Installer.msi

You can manually verify the computer account has access to the share and MSI installer file by attempting to connect to the share as the local computer account (NT Authority\System) by performing the following:
1. On the target computer, log in as an administrator.
2. Schedule an AT job for 1 minute ahead of the current time to launch a command prompt as NT Authority\System:
C:\> at 1:00pm /interactive cmd.exe
3. After the command prompt window appears, you will have NT Authority\System access.
4. Attempt to list the contents of the share using the UNC path:
C:\> dir \\server\share - You should receive a directory listing of the files on the share


5.3. MSI & MST

MSI Installation on client PCs would have logs within the Event Viewer. Useful information is provided to check where the issue may be.

If MSI installation is corrupt then you may not be able to install or uninstall. To remove the corrupt installation please run the MSI removal utility provided by Microsoft. This utility removes all traces of the corrupt MSI installation.

All windows client machines would have to have the latest service packs provided from Microsoft as the Windows installer are different on different service packs.

When creating MSTs verify that the installation directory is correct for Windows Vista installations –
C:\ProgramData\PC Power Down
And for Windows XP -
C:\Program Files\PC Power Down
Also verify that the IP address of the server is correct and reachable on the network.



Last updated by Administrator (admin)  on Feb 23 2011  at 9:43 AM
<< 4. MSI Deployment Index