Scripting

I spent the better part of today trying to finalize an SPSS 12 installer that doesn't involve repackaging (because of how badly our SPSS 11 installation worked as a repackaged MSI). The installer runs great as long as someone is logged in. I tried thinking of all the differences between our department's boot script or active directory push installs running and a logged on user, and couldn't figure out why these in particular would fail (esp. since so many other, similar installations have been successful).

It looks like the answer has something to do with the conditions under which DCOM objects are launched (my terminology is bad here). DCOM is configurable such that certain applications can be launched as one of a few different types of user (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/com/htm/security_3gjd.asp). Our machines are set to launch InstallShield InstallDriver applications as 'interactive user,' who does not exist pre-logon. However, I tried setting DCOM to use 'Launching User' for the InstallDriver and InstallDriver String Table, to no avail. I'm too ignorant about DCOM to know my way around it very well and to know what else to try.

It looks like InstallShield might actually reset the "installdriver" and "installdriver string table" user from "launching user" to "interactive user" when it runs, effectively overwriting the changes I've made in order to make the installer work.

SPSS' support is disappointing (support.spss.com):

"
Resolution number: 40099

Resolution Subject: Ensure that a member of the local Administrator's group is logged into each machine

Resolution Description:
This problem has been filed with SPSS Development and will be addressed in a later release of SPSS for Windows. In addition to the SYSTEM account, the installer requires a member of the local Administrators' group to be logged into each client at the time of installation. If the installation still fails, it's possible that the local system (or current account) does not have access to launch DCOM. Particularly if you are using Group Policy to deploy the MSI, this appears because it is the local system account that initiates action before any user is logged on. In doing so, Windows Installer launches the InstallScript DCOM engine as user "interactive user" and generates this failure. To resolve this, you may use DCOMCNFG.EXE to change the launch identity of "InstallShield InstallDriver" and "InstallShield InstallDriver String Table" to "Launching user". We apologize for any inconvenience this may have caused.
"

I've got 200 workstations on which I need to install SPSS, and I'm distressed that I can't install without repackaging. Does anyone have any suggestions?

Many thanks.
cdo-appdeploy@sociology.osu.edu