I distribute some MSI-Packages with GPO's (I created the mst files with the office tool) and I have different "install behaviours".
Office, i.e., installs itself after the first use. The Acrobat Reader is installed directly.

Where can I change this behaviour???

H. Thielen
0 Comments   [ + ] Show 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.


The difference here should be if you assign it to a machine, or advertise it to a user. If you assign it to a machine it will be installed at next reboot (startup). If you advertise it to a user, they will get it when they log on. In the case of Office (and other MSI setups, depending on how they are developed) you may see Windows Installer activity on first use if there are user keys or files (HKCU/Profile) elements within the package. If there is a component in the MSI with a keyfile that is user-specific, it will always repair itself on first launch to install the missing file(s). I would not recommend changing the Office package, but any that you create yourself can typically be stripped of such elements to avoid this problem.

Hope this helps!
Answered 01/19/2004 by: bkelly
Red Belt

Please log in to comment
while deploying via GPO the Add in Manager for the application fail to come up,but without GPO works perfectly. what can be wrong?
Answered 04/19/2004 by: segxy
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity