These NOtes are for S&T 2010. BUt they apply to 2009 + 2011 too. Just didn't want to create a new KB.
Tip 1: The INI and command line info above is correct and pretty much complete. THe one MSI PROPERTY value you would want to add for a corporate, locked down environemnt would be :
In addition to that -> there is a much simpler and cleaner way to handle any HKCU registry settings associated with this application. Such as the EULA above. Transpose the HKCU result that you find in the registry from any of your app responses to an HKLM equivalent like this e.g. :
N.B. Thsi example is from a WIN7 64bit OS machine. But it applies equally well to 32bit WIndows OS installations by eliminating the WOW6432Node portion of the path.
They work. I was able to use this technique to handle the following:
- the annoying "auto update off the web" prompt at first run under each new userid.
- the GPS settings and port selection for our corporate fleet units (which are always the same as they all use the same model laptop with same BIOS settings)
BTW: This technique of transposing an applciation's "preference" settings from its default HKCU location onto the HKLM hive, to effectively make that option's choice a preference mode GPO, works with A LOT of diffferent applcaitions and their settings under a lot of scenarios. It beats custom user GPO's or having toe create Active Setup based scripts.
The command line and INI optiosn above should be good for most people
IN additon, there is a much cleaner, more elegant and robust, + simpler way to handle S&T applcaition settings and preference such as the EULA item above that you want to fix in your environment. You can take the HKCU setting reuslt from a sample machine and trqanpose it into teh HKLM hive as per below:
The above example if for a WIN7 64 unit. But works jsut as well on 32 bit WIndows OS's with teh WOW6432Node portion of the path removed.
BTW: This method of transposing an app's HKCU based preference settings to the app's HKLM hive to make the setting iniitally applicable to ALL user profiles on a box can be used for many settings for many applications. It effectively acts as a locally deployed preference mode GPO you , the packager control. Try using to handle your apps preferences first. Before you look at custom user GPOs or Active Setup options.