Administrators and IT specialists that are tasked with quietly deploying SAS 9.3 via provisioning software are often faced with a variety of scenarios within their enterprise. For example, deployment might include user groups that have different product requirements on multiple Windows operating systems, or an automated quiet installation process might need to be created.
When using provisioning tools to install SAS across an enterprise that has heterogeneous machines, you need to maintain greater control of the installation process and ensure that there are no surprises during the installation.
The following two-pass process not only helps reduce potential reboots that could occur during a quiet installation, but it also gives the administrator complete control over what is installed in their packages so that software pieces are not installed ad hoc. Troubleshooting advice is also included.
Note: No matter which provisioning tool you use to quietly deploy SAS in your enterprise (for example, LANDesk, Wise, Microsoft SCCM, Symantec Altiris, IBM Tivoli, BMC, and so on), the underlying methodology is the same.
Before you proceed with this method, SAS recommends that you perform a thorough inventory of all of the SAS products that your organization needs to be installed and investigate the system requirements of those products. This information is available on the SAS System Requirements web page. In the Current Releases box, select SAS 9.3 (TS1M0) and later, including maintenance and then filter your search according to your needs.
In this stage, you determine the system requirements, construct the applicable commands for each identified system requirement, and implement the system requirements commands into your provisioning software package.
Note the system requirements that are listed under Stage 1 System Requirements. You will implement these system requirements later. In most cases, where you are installing a minimum number of SAS products (for example, SAS Foundation or a client mix), you might see that only one to four system requirements are needed. In larger, more complex installations, you could have several more requirements.
The locations in the typical SAS 9.3 software depot of the system requirements and their associated quiet installation commands are listed in this SAS 9.3 applicable table. You will use these commands to implement the system requirements that you identified in Step 1. You should verify the paths in your depot, as the examples in Table 1 might be slightly different from the actual paths in your depot.
Note that some of the requirements have both 32-bit and x64-bit installers. You should install both 32 bit and x64 bit versions if your machine is Windows x64 bit and install only the 32-bit version if your machine is Windows 32 bit.
Reboots of the operating system might be pending either from previous installations of products other than SAS or because one of the system requirements that you just installed requires a reboot. Reboots are not always required. However, if necessary, now is a good time to reboot your system.
Because you are installing across a number of machines in the enterprise, you might need to ensure that rebooting does not take place. You should remove registry entries that are known to cause a reboot, such as FileRenameOperations or PendingFileRenameOperations. These entries are located here:
Running the fixpendingreboot.bat file that is included on the Downloads tab will remove the keys explained above if they are present. You can use this BAT file or its commands as an initial step in the final packaging job to remove the possibility of those keys affecting a potential reboot.
In this stage, you record a response file and construct a quiet installation command to be implemented into your provisioning software package.
From a command prompt navigate to the root directory of the SAS Software Depot and run setup.exe with the record and response file parameters. The following command is an example:
See "More Information about Response Files" below.
Note: Because the two-pass method is being used, the NOMSUPDATE parameter is used to suppress the SAS® Deployment Wizard from reinstalling the system requirements. Recall that Pass One determined the system requirements, and commands for them were created and deployed already.
From a command prompt, navigate to the root directory of the SAS Software Depot and run setup.exe with the QUIET, NOMSUPDATE, and RESPONSEFILE parameters. The following command is an example:
Note: SILENTSTATUS support is available in SAS 9.3 (TS1M1), Revision 12w23 and later. This option enables you to monitor the silent installation. The following command is an example:
Note: If the provisioning software is used to monitor the setup.exe process or if the package is configured to run one program before another, it will be necessary to use the WAIT parameter on the installation command. Adding the WAIT parameter on the installation command line as follows keeps the setup.exe process resident:
Before you incorporate the quiet installation command into your provisioning package, you should test the installation command that you created in Pass Two.
On a machine where you have completed Pass One and on which the system requirements have been deployed, run the command from Pass Two to verify that the installation command successfully installs the software.
To troubleshoot, run the installation command without the QUIET parameter as shown in the example below:
This command runs the installation against the same response file but will be interactive and might point out potential issues.
You should be aware of the following SAS notes:
See information about the missing Documents folder under Windows 7 on the SYSTEM account.
You need to know the following information about response files:
For example, you have three groups: Group A needs SAS® Enterprise Guide® only. Group B requires SAS Enterprise Guide and SAS® Add-In for Microsoft Office. Group C requires only SAS Foundation. In this example, you record multiple response files and name the response files accordingly—one file for each group to specifically install only the required products. You could record three files with the names EGresponse.properties, EGAMOresponse.properties, and SASresponse.properties if you want the names to reflect which products were being installed. You could also name the files to reflect the group name, such as GroupAresponse.properties, GroupBresponse.properties, and GroupCresponse.properties.
Note the following best practices:
Chapter 3, "SAS Deployment Wizard: Command Line Options, Record and Playback section" in the SAS Deployment Wizard and SAS Deployment Manager 9.3: User’s Guide
For SAS 9.4:
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | Base SAS | Windows 7 Professional x64 | 9.3 | 9.3 TS1M0 | ||
Windows 7 Ultimate 32 bit | 9.3 | 9.3 TS1M0 | ||||
Windows 7 Ultimate x64 | 9.3 | 9.3 TS1M0 | ||||
Windows Vista | 9.3 | 9.3 TS1M0 | ||||
Windows Vista for x64 | 9.3 | 9.3 TS1M0 | ||||
Windows 7 Professional 32 bit | 9.3 | 9.3 TS1M0 | ||||
Windows 7 Home Premium x64 | 9.3 | 9.3 TS1M0 | ||||
Windows 7 Home Premium 32 bit | 9.3 | 9.3 TS1M0 | ||||
Windows 7 Enterprise x64 | 9.3 | 9.3 TS1M0 | ||||
Windows 7 Enterprise 32 bit | 9.3 | 9.3 TS1M0 | ||||
Microsoft Windows XP Professional | 9.3 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2008 for x64 | 9.3 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2008 R2 | 9.3 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2008 | 9.3 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2003 for x64 | 9.3 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2003 Standard Edition | 9.3 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2003 Enterprise Edition | 9.3 | 9.3 TS1M0 | ||||
Microsoft Windows Server 2003 Datacenter Edition | 9.3 | 9.3 TS1M0 | ||||
Microsoft® Windows® for x64 | 9.3 | 9.3 TS1M0 | ||||
Microsoft Windows 8 Enterprise 32-bit | 9.3 | 9.3 TS1M2 | ||||
Microsoft Windows 8 Enterprise x64 | 9.3 | 9.3 TS1M2 | ||||
Microsoft Windows 8 Pro 32-bit | 9.3 | 9.3 TS1M2 | ||||
Microsoft Windows 8 Pro x64 | 9.3 | 9.3 TS1M2 | ||||
Microsoft Windows 8.1 Enterprise 32-bit | 9.3 | 9.3 TS1M2 | ||||
Microsoft Windows 8.1 Enterprise x64 | 9.3 | 9.3 TS1M2 | ||||
Microsoft Windows 8.1 Pro | 9.3 | 9.3 TS1M2 | ||||
Microsoft Windows 8.1 Pro 32-bit | 9.3 | 9.3 TS1M2 |
Type: | Installation Note |
Priority: | medium |
Date Modified: | 2013-11-26 10:13:54 |
Date Created: | 2013-08-21 09:38:38 |