Hi All

Are there any Msiexec properties set only when an MSI is installed by group policy that I can use to control a condition based install, ie "if installed by GPO, then do this, if not, then do this"

The reason is because we have an important security application that is currently deployed only via Group Policy (running 2003 mixed mode domain). To ensure all newly built workstations have this app installed (without relying on GPO which can fail), I need to also install the application on the workstation build image so the app is already installed by default before it even joins the domain.

The problem I have is that when the newly built machine joins the domain and picks up policy, the existing policy for the security app runs, sees the app is already installed but unmanaged, uninstalls the build image install of the app then on next reboot reinstalls it again, which is not ideal and has been known to fail, leaving the machine without any install at all.

Ideally what I'd like to do is configure it so that the build image install becomes managed by GPO without the uninstall/reinstall process but having tried MS's recommendations on doing this (for an unmanaged Office install changing to managed), it doesn't work. The alternative is to modify the transform we use to deploy this app so that I can set a launch condition based on whether the original install was a group policy install or build image install, but I dont know of any specific properties set when an install is triggered by GPO to allow me to do this?

Its not critical that the app becomes managed as we have other ways of uninstalling it if required, but what I do want to do is prevent the GPO install from removing and reinstalling it.

thanks
Chris
0 Comments   [ + ] Show Comments

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.

Answers

0
Why not simply add the managed install to the build image?You could create a special OU for the build machine you're using as a base, deploy to it and re-SysPrep it, no?
Answered 06/25/2009 by: VBScab
Red Belt

Please log in to comment
0
Unfortunately the build image process is done on a standalone domain, it can't be done on the live system due to security restrictions we have placed on us.
Answered 06/25/2009 by: Locoblade
Senior Yellow Belt

Please log in to comment
0
I suppose you could AppSearch for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\AppMgmt\[ProductCode]....
Answered 06/25/2009 by: VBScab
Red Belt

Please log in to comment
0
Yep good idea, I'll give that a go.

cheers
Chris
Answered 06/25/2009 by: Locoblade
Senior Yellow Belt

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