Hello, I am trying to deploy OpenOffice 3.4 via GPO. I am able to do this in xp. My issue comes from windows 7 when i try to push to a machine it says please you setup.exe (I have altered the MSI to get around this) And can install it on a Windows 7 machine if im there and double click the MSI on the actual machine itself but if i try to install via GPO it does not install.

The original error i was getting was that it could not find the source file. Witch by making a registry change to allow more time for the network to respond seemed to clear that up now in event log i see this:

Beginning a Windows Installer transaction: {51071d66-d034-4239-94e0-723fca10b6fe}. Client Process Id: 924.

Ending a Windows Installer transaction: {51071d66-d034-4239-94e0-723fca10b6fe}. Client Process Id: 924.

But nothing was installed.
Im confused why i can install this very same package on a local windows 7 machine and not though GPO.

0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



Does the shared folder on your server has read permissions for everyone? If it does, can the target machine connect to the share without being logged on an actual user account? Are there any user-related restrictions when it comes to connecting to the share?

Answered 07/06/2012 by: SMal.tmcc
Red Belt

  • All the shares are set up same way for my GPO's the install of adobe flash, reader, and java worked on both xp and 7

    Just this open office msi being a pain... i just find it weird i can navigate right to the share on a windows 7 machine and install it but i cant install using a gpo.
  • could be a few things I have seen timing. uac, unsigned drivers, and rights all cause the same sort of symptions. Did you get any error numbers? You can try a couple things. create a GPO batch that creates a temp local folder, copy and install from there, delete it after to test.

    Also you can enbale logging of Application Deployment operations, add the following registry value on the client computer. Delete this value after troubleshooting to avoid performance degradation:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics

    Note that the you may need to create the Diagnostics key.

    Value: AppMgmtDebugLevel
    Type: REG_DWORD
    Data: 4b

    The logging file is named Appmgmt.log and is located in the %SystemRoot%\Debug\Usermode folder on the client computer
Please log in to comment
Answer this question or Comment on this question for clarity



Create verbose log and analyze it using WILogUtl.exe

Answered 07/06/2012 by: jagadeish
Red Belt

Please log in to comment