Deploy, configure, and update IBM software with Microsoft System Center Configuration Manager

Comments

Overview

This article describes how to use Microsoft System Center Configuration Manager (SCCM) to install IBM software. Instructions include how to set up your environment for the deployment, and how to create a basic package, program, and advertisement to install IBM Installation Manager and IBM software using Installation Manager.

Prerequisites

To understand the steps in this article, you need familiarity with Microsoft System Center Configuration Manager 2007 and IBM Installation Manager.

System requirements

To complete the steps in this article, you need:

  • A server with Microsoft System Center Configuration Manager 2007 SP2 installed
  • At least one workstation with Configuration Manager Advanced Client installed
    • Note:
      Make sure you assign the workstation(s) to the server SCCM site

Set up your environment

Before you create the packages for deployment, decide how you want the workstations to access the Installation Manager repositories. There are two ways to access the repositories:

  • Remotely host repositories
  • Include the repositories in the package

You also need to determine where you want to maintain Installation Manager. There are two options for this:

  • Maintain an Installation Manager instance on the target machine(s)
  • Use Installation Manager from a shared drive

Remotely host repositories

The first approach is to remotely host repositories, using HTTP, HTTPS, FTP, or a network share. The primary benefit of remotely hosting repositories is that you can leverage the behavior of IBM Installation Manager to minimize the number of files downloaded to the target system and bandwidth used.

Include repositories in the package

Corporate policy might stipulate that you include repositories in the package. If so, it is recommended that the administrator create platform-specific repositories using the IBM Packaging Utility's command line mode and the "-platform" switch. This reduces the size of the repository to copy to the target machine. See the Information Center documentation Command-line arguments for the pucl command for more information.

Locally installed Installation Manager

Locally installing Installation Manager is the recommended approach. In this instance you use two steps to install a package.

  1. Install or verify that Installation Manager is installed
  2. Use that installed Installation Manager to install the desired package

Using the Installation Manager from a shared drive

You can use the Installation Manager installer from a shared drive to install packages. This allows an administrator to maintain only one instance of Installation Manager. Another benefit is tightly controlled end user access to the Installation Manager.

The drawback is the requirement of a shared drive which might not work well in a globally distributed environment.

Create the SMS package

It is recommended that you create two types of packages to install your IBM Rational software. The first type of package installs the Installation Manager itself, and the second installs the chosen package.

Download and unzip the Installation Manager package from the IBM Installation Manager and Packaging Utility download links page. When you create the package, the source directory should be the root of the directory containing the Installation Manager installer files.

For the second type of package, use the Installation Manager silent install capability.

Create the batch files to perform the installations

Use a batch file as a wrapper to call the Installation Manager when you perform the installation if the Installation Manager is installed in to the same path for all target systems. A response file included in the same directory is required.

The batch file performs the following steps:

  1. Set a HOME variable to the directory of the batch file. This lets you look up the location of the response file.
Listing 1. Set HOME location for batch file
 @set HOME=%~dp0%
  1. Set an IMCL variable to point to the location of the Installation Manager command line executable, imcl.exe, on the target system. Use the code shown in Listing 2 to see if Installation manager is installed in the 32 or 64-bit location.
Listing 2. Determining imcl.exe location
 @if exist "C:\Program Files\IBM\Installation Manager" ( 
  echo Found IM on 32 bit system
  set IMCL="C:\Program Files\IBM\Installation Manager\eclipse\tools\imcl.exe"
) else (
  echo Found IM on 64 bit system
  set IMCL="C:\Program Files (x86)\IBM\Installation Manager\eclipse\tools\imcl.exe"
 )
  1. Use the command line in Listing 3 to call imcl.exein the IMCL directory.
Listing 3. Call IMCL to perform installations
 call %IMCL% input %HOME%<name of response file> -log <path to log file> -acc eptLicense

This simple batch file runs the install using the response file given, and writes any errors to the log file that you provided in the command line.

Create the package

  1. Launch the SCCM Configuration Manager console.
  2. Expand the Site Database > Computer Management > Software Distribution menu items.
  3. Right-click on Packages and select New > Package.
  4. In the wizard, type the name for the package, i.e. Installation Manager, the version that corresponds to the version of Installation Manager you are installing, and the manufacturer, in this case IBM, as shown in Figure 1. When you create a package to install a product, use the appropriate name and version for that product. Click Next.
Figure 1. New Package Wizard, General page
Provide name and version on General page package
Provide name and version on General page package
  1. Select the box This package contains source files, then click the Set button to indicate where to find the files for this package, as shown in Figure 2. The files can either be local on the SCCM server, or available over a UNC path on your network. The directory should include both the batch file used to perform the install and any response file necessary to drive the installation. Click the Next button.
    Note:
    When you install or update Installation Manager, the Source directory should be the unzipped install kit for Installation Manager.
Figure 2. New Package Wizard, Data Source page
Provide package files on the Data Source page
Provide package files on the Data Source page
  1. Leave the default options for Distribution Settings, and Reporting. Choose which option meets your needs for Data Access.
  2. On the Security page, verify that the SCCM Administrator account has the appropriate security rights, as shown in Figure 3, then click the Next button.
Figure 3. New Package Wizard, Security page
Verify SCCM Administrator permissions
Verify SCCM Administrator permissions
  1. Verify that the information is correct on the Summary page, as shown in Figure 4. Click Next. The package creation starts. Once it is complete, click the Finish button.
Figure 4. New Package Wizard, Summary page
Validated information on Summary page
Validated information on Summary page

Create the distribution point

  1. Start the SCCM Configuration Manager console.
  2. Expand the Site Database > Computer Management > Software Distribution > Packages menu items.
  3. Expand the package you created in the previous section, and right-click on the Distribution Points item.
  4. Select New Distribution Points.
  5. Click the Next button on the wizard, then choose the available distribution point.

Create the program

For a package to start there must be a program to run. The following steps show how to create a program for the package you have defined.

  1. Launch the SCCM Configuration Manager console.
  2. Expand the Site Database > Computer Management > Software Distribution > Packages menu items.
  3. Expand the package you created in the previous section
  4. Right-click on the Program item.
  5. Select New > Program.
Figure 5. New Program Wizard, General page
Provide name and command line to execute on General page
Provide name and command line to execute on General page
  1. Enter the Name for your program, and the command line you want to run in the appropriate text fields. If you want, you can provide a comment to describe what the program does. Use installc.exe -acceptLicense as the command line to install Installation Manager. If you install a product, the command line will reference the batch files you create.
  2. Leave the default settings on the Requirementspage.
Figure 6. New Program Wizard, Environment page
run with administrative rights selected
run with administrative rights selected
  1. For the environment, consider whether you are installing Installation Manager or a package that requires administrative rights. The program can run whether or not a user is logged on, or you can choose for run mode to Run with administrative rights, as shown in Figure 6. If you want to install Installation Manager or a package in user mode, choose Run with user's rights.
  2. Keep the defaults already selected on the Advanced page.
  3. Keep the defaults already selected on the Windows Installer page.
  4. The Microsoft Operations Manager (MOM) Maintenance page shown in Figure 7 provides choices for operations manager alerts. You can choose to Disable Operations Manager alerts while this program runs, or to Generate Operations Manager alert if this program fails.
Figure 7. New Program Wizard, MOM Maintenance Mode
Choose whether alerts are generated
Choose whether alerts are generated
  1. Verify that the information on the Summary page (shown in Figure 8) is correct. If the information is correct, click the Next button. The program is created.
Figure 8. New Program Wizard, Summary page
Information to be verified
Information to be verified
  1. You can now run the package.
    Note:
    It is recommended that you use a task sequence to ensure that the packages are installed in the correct order and to make sure any potential required restarts occur in the proper order.

If you are not familiar with creating custom task sequences, read the Microsoft TechNet article "How to Create a Custom Task Sequence." For information on advertising the task sequence, see the Microsoft TechNet article How to Advertise Task Sequences.


Downloadable resources


Comments

Sign in or register to add and subscribe to comments.

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Rational
ArticleID=982581
ArticleTitle=Deploy, configure, and update IBM software with Microsoft System Center Configuration Manager
publish-date=09052014