I came across this bit of info. Frankly I'm not sure how or where this applies, but given some recent discussions about server deployments, virtualization, and evaluation controls... might be useful.
Quote:
Windows Active Setup helps administrators fixing the application which is installed by a Software Distribution System during user login before even application is triggered by the user.
HKLM\Software\Microsoft\Active Setup\Installed Components\[ProductCode]
HKCU\Software\Microsoft\Active Setup\Installed Components\[ProductCode]
The registry keys listed above are compared, and if the HKCU registry entries don’t exist, or the version number of HKCU is less than HKLM, then the specified application is executed for the current user.
If your application requires installation of components such as files or registry keys specifically for the current user profile (per-user), but your application has no advertised entry points or other triggers to initiate the installation process (such as Windows Installer Self-Repair), then Active Setup is the solution.
rest of the info found at:
http://blog.exp.be/2007/08/06/windows-active-setup/
I'm thinking along the line of a 'master pub' installed on work and home systems, and user-specific files carried on a USB/Flash drive (portability but not requiring virtual environ).
Login
FAQ
Search
