I am new to Advanced Installer and was wondering what the best way to do something might be. Our MSI is for an internal application and is deployed to about 500 machines via SCCM. At any point in time a handful of these machines are being used for testing or development work. Which machines these are varies greatly even from day to day.
When an updated MSI is sent out via SCCM we do not want it to run on the test/development machines. Keeping track of which machines are which in SCCM would be a pain in our case. So the thinking is to set a value(i.e. a value in an XML config file) on the PC that would indicate to the MSI if it should run or not.
Looking at the Advanced Installer users guide it looks like the Custom Launch Condition would be the thing to use. I am assuming that I would need to run a script of some sort at the start of the MSI to do the actual check and then set a property or environment variable, as it does nt look like I can create a condition that could check for a file or the contents of a file.
Has anyone done this type of thing before? Is this a reasonable way of doing this? Is the a better way?
Thanks for any input.
FOLLOW US
Get the latest news in Application Packaging