IT Pro Tips for SPSS Inc. SPSS 14

Deployment Tips (3)

Most Common Setup Type

Not Determined

Average Package Difficulty Rating

Rated 4 / 5 (Somewhat Difficult) based on 1 ratings

Most Commonly Reported Deployment Method

Windows Installer with Custom Transform (MST)

118

Note

From SPSS Tech support:

First, if you intend on pushing the installation to a directory where a previous version resides, you must first uninstall the old version using one of the following command lines. Please note you will lose all customizations from the previous version.

If the user has SPSS 13.0 installed:
msiexec /X{DB8CEC42-30B1-4F49-BD06-9393EB81CCF7} /qn ALLUSERS=1 REMOVE="ALL"

Installation Types:

The only installation allowed in SPSS 14.0 for Windows is a full (or local) installation. Minimal installations are no longer available as of this release. The details of the full installation are as follows:

Full Installation: Installs the SPSS program files, system files and registry entries locally on each client machine. This installation can be licensed locally (site license) or via a network license manager (network license).

Properties for Push Installations:

COMPANYNAME: Registers your company's name in the Help->About menu for each installation.

ISX_SERIALNUM: Registers the serial number provided by SPSS Inc. in the Help->About menu for each installation This number can help Technical Support identify a registered user should that user require assistance from SPSS Technical Support.

INSTALLDIR: The directory where SPSS for Windows should be installed on the end user's desktop computer. If this property isn't specified, the default path, C:\Program Files\SPSS will be used. A valid value is

C:\SPSS14

AUTHCODE: The authorization code that came with your software which requests a license for SPSS for Windows. Specify this property only if you have purchased a site license.

Note: If you do not specify this property, a temporary license will be installed with the product and expire after 14 days. At that time, you will need to license the software via the License Authorization Wizard on each machine.

SPSSLICENSE: The license type. Specify this property only if you have purchased a network license (using a network license manager to monitor concurrent usage). The only valid value, which is case sensitive, is

Network

LSHOST: The IP address or the host name of the network computer on which the network license manager is running. Specify this property only if you have purchased a network license (using a network license manager to monitor concurrent usage). A valid value is an IP address or network computer name.

COMMUTE_MAX_LIFE: The maximum number of days for which an end user can check out a commuter license. Specify this property only if you have purchased a network license (using a network license manager to monitor concurrent usage). If you do not specify this property, the default maximum life is 7 days. Valid values are between 1 and 180.

Examples:

Site License (please note authorization code must be in small letters):

msiexec /i "\\ServerName\SPSS\SPSS 14.0 for Windows.msi" /qb /L*V "<path>\logfile.log" COMPANYNAME="My Company" ISX_SERIALNUM="999999" INSTALLDIR="c:\spss14" AUTHCODE="abcdef123456"

Network License:

msiexec /i "\\ServerName\SPSS\SPSS 14.0 for Windows.msi" /qb /L*V "<path>\logfile.log"
COMPANYNAME="My Company" ISX_SERIALNUM="999999" INSTALLDIR="c:\spss14" SPSSLICENSE="Network" LSHOST="123.123.123.123" COMMUTE_MAX_LIFE="30"

Active Directory Group Policy Installation:

You can add the above properties to the SPSS 14.0 for Windows.msi file or create a transform file, using an MSI editor, such as ORCA. Add the relevant properties to the Property table, save the changes or create a transform file, and distribute the updated MSI or transform file via Active Directory Group Policy.

SMS (Systems Management Server) Installation:

The SPSS 14.0 for Windows CD-ROM contains a package definition file that can be used for installations distributed via SMS. This file, called SPSS 14.0 for Windows.sms, is located in the SPSS directory on the CD-ROM. You will need to modify this file, using any text editor, to reflect the appropriate command line for your installation. Below is the default command line taken from this file.

CommandLine = msiexec /qn /I "SPSS 14.0 for Windows.msi"

Uninstallation:

To carry out a silent uninstall of SPSS 14.0 for Windows, please use the following command line:

msiexec /X{0AE19D89-17A9-404D-932A-FAAF43F3C77E} /qn ALLUSERS=1 REMOVE="ALL"

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

jamcewen
04/11/2006
Show Comments ( 0 )

117

Note

SPSS 14.0 turned out to be more difficult than expected. For my particular case, where a site license was used, I used a transform instead of all the properties specified in one of the notes above. I added these properties to the Properties table in a transform:
SERIALNUM="999999"
AUTHCODE="abcdef123456"

Using these properties in the command line would work as well, but if you have the same particular problem that we had, then you need a transform (so that you don't have to modify the MSI itself). We use SMS 2003 to deploy applications. It runs the pushes using the SYSTEM account. SPSS 14.0 uses ISScript, and there is a particular custom action in the SPSS MSI that seems to install or configure the IntallShield Drivers on a computer. The custom action in the MSI is EngineStartup.D8FE90D... The numbers at the end might be different from product to product (for Flash Player it is EngineStartup.4F635...) but the name is the same.

This custom action has to be deleted from the transform. During installation, this action (which is located in the Istallation Sequence and the User Interface Sequence of the MSI) sets the InstallShield DCOM objects to run using the interactive user, which is the currently logged on user. If you run the SMS job, which will run the MSI using the SYSTEM account, the EngineStartup custom action changes the RunAs user of one of the InstallShield DCOM objects to run as the interactive user. Since the interactive user doesn't have admin rights, installation fails. Apparently, this happens because the InstallShield Driver tries to access some files that are in C:\Windows\Temp, but because it is running under a regular account (non-admin) it fails, and so does the whole installation. I found this information in here.

The solution is to first install isscriptXX.msi for computers that don't have it. Then delete the RunAs registry values: HKCR\AppID\{GUID}\Runas
The GUID is the Application ID of the InstallShield DCOM objects, which can be found using C:\Windows\system32\dcomcnfg.exe.

When the RunAs values are deleted, for every InstallShield InstallDriver and InstallShield String Table, the objects are set to run under the Launching User.

In the transform, you have to delete the EngineStartup custom action from both sequences (Installation and UI sequences). Also, don't forget to add those two properties in the transform if you are using a Site License. There is another thing that I did in the transform, just in case. In the InstallShield suppport website, they say that you should rearrenge the order of some custom actions. This is the website.

This is a copy of what it says.
--------------------------------
This issue can be worked around by re-ordering the InstallShield custom actions in the sequence. To accomplish this, follow these steps:

Select the Sequences view in the InstallShield IDE.

Expand the Installation | Execute sequence.

Highlight the ISStartup custom action in the sequence.

Right-click on the custom action and choose the "Move Down" option.

Repeat this process for the User Interface Sequence by expanding the Installation | User Interface Sequence.

Rebuild the project.
The old sequence has the following order:

ISMsiServerStartup

ISStartup

ISSetupFilesExtract
The new sequence should have the following order:

ISMsiServerStartup

ISSetupFilesExtract

ISStartup
This allows the setup files to extract before the OnBegin event, thereby making them accessible from InstallScript code within the OnBegin event.

Note: The default order is restored when custom actions are added or when the option is selected to "Reset InstallShield Custom Actions". Therefore, the steps above need to be performed again in these scenarios.

--------------------------------

According to a post by "Skuld-Chan" on this web site

Also, be careful when testing your script if you are using a Site License. Every time you license a copy of SPSS 14.0 with the authentication code, you have one license less in the SPSS servers.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

neirar
08/02/2006
Show Comments ( 0 )

117

Note

I used the info above, and it all worked great, with one exception. In order to get the package to properly activate with my AUTHCODE during install, I had to create a transform and change the custom action LaunchSPSSActivator to type 34, with source=INSTALLDIR and target=[INSTALLDIR]spssactivator.exe [AUTHCODE]. I also set it to Deferred Execution in System Context, so that it works for my locked-down users running the elevated install.

Setup Information:

Setup Type: unspecified

Deployment Method Used: unspecified

Deployment Difficulty: unspecified

Platform(s): Windows

CoreyFlies
01/11/2007
Show Comments ( 0 )

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

14

SPSS

Version

14

Questions & Answers (0)

Questions & Answers related to SPSS Inc. SPSS

Blogs (0)

Blog posts related to SPSS Inc. SPSS

Links (0)

Links related to SPSS Inc. SPSS

Reviews (0)

Reviews related to SPSS Inc. SPSS

SPSS Inc. SPSS

Don't be a Stranger!

Deployment Tips (3)

Inventory Records (1)

SPSS

Version

Questions & Answers (0)

Blogs (0)

Links (0)

Reviews (0)