Scripting

In one of my software deployments, the installer refuses to run on Windows 7, saying it is an unsupported operating system. To install it manually, I have been changing the compatibility settings to run in compatibility mode for Vista SP2. When I do this, it installs without a problem. The application itself works just fine on Windows 7.

I created a vbscript to do this for me automatically: when the vbscript determines it is running on Windows 7, it sets the appropriate registry settings so the installer thinks it is running on Vista SP2.

This works great when I manually run the script as an administrator. I open a command prompt with administrative privileges, use "cscript.exe install.vbs", and the software installs as expected. The installer leaves a log file that specifies that it found itself running on Vista SP2, and completes successfully.

However, when I deploy the vbscript and installer through SCCM 2007, it doesn't work. I know the vbscript sets the compatibility setting in the registry (the vbscript writes this information to the Event Log), but the installer leaves a log that says it found itself running on Windows 7 and fails.

Right now the only thing that I can think may be causing this problem is if, for some reason, when applications run in the SYSTEM account (like SCCM deployments that are run with administrative privileges), Windows doesn't enforce compatibility settings. Unfortunately, I haven't found anything online to back up this suspicion.

Does anyone know if application compatibility settings are honored when running in the SYSTEM account?

Or, does anyone know of something else that may be causing this problem?