Do you know if there are switches or something that can be turned on to debug the GP deployment of an msi? I ask because I have an msi that works perfectly when installed manually but sits there endlessly on the installing screen when deployed via GP. I've left if upwards of 30 mins before giving up and hard rebooting the computer. It should take less than a min.

The event viewer doesn't give any clues. This app has been created in house btw but our developer is not sure what might be causing it.

Hope someone can help

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


- Create an ASCII (as opposed to Unicode) .REGwith this content
- Paste in:REGEDIT4


As you can see, it's just a policy, so you could apply it from the GP editor, just like any other.

- Merge the .REG on the target workstation
Note that, after merging, you will get logs for ALL MSI activity, including advertisements
- Logs are written to %SystemRoot%\TEMP, prefixed 'MSI', named with random alphanumeric characters, and with a .LOG extension.
- I use FIND to locate the log file pertaining to a particular deployment, looking for unique text. The MSI's ProductCode is the obvious candidate.
- Remember to turn the policy off when you're done, or that folder will fill up VERY quickly.
Answered 01/22/2009 by: VBScab
Red Belt

Please log in to comment
I ought to have added, BTW, that during the "hang", it's almost certain that the package has popped up a dialog of some kind, waiting for a user to press 'OK' or something. You should probably author that out.
Answered 02/02/2009 by: VBScab
Red Belt

Please log in to comment