Sign up today to participate, stay informed, earn points and establish a reputation for yourself!Sign up! or login
I had to deploy version 220.127.116.11 to desktops which are locked-down and the customer required the users configuration to (1) have the output sent to the clipboard and the printer, and (2) have the default storage location as the users desktop. I ran a setup capture to generate an MSI to control the users configuration. The application stores its configuration in an INI file located in the users context. The app is set to run automatically upon login. If the config file doesn't exist, the EXE will create one with its own defaults.
Seems simple enough; the MSI will start self heal and it'll create the INI file. Problem is that an INI file (delivered via the INI table) does not have a key file so it doesn't get repaired with self-heal or Active Setup. Further, the default setup causes the executable to be launched before Active Setup is performed on systems, so the EXE creates the INI for each new user before A.S. is launched.
The trick I used was to move the startup of the app into the Startup folder (system or user, it matters not). This is one of the last actions taken during the login process, so the application is actually started after the Active Setup process is executed.
View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.