How To
Summary
This article provides instructions on how to create the necessary package and program steps to install Installation Manager through Microsoft's System Center Configuration Manager and IBM software.
Mark Guertin (mguertin@us.ibm.com), Advisory Software Engineer, IBM
Republish of a document originally published 05 September 2014
Objective
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.
Environment
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 IBM documentation topic 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.
- Install or verify that Installation Manager is installed
- 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.
Steps
Create the SMS package
It is recommended that you create two types of packages to install your IBM 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:
- 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%
- 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"
)
- Use the command line in Listing 3 to call imcl.exe in the IMCL directory.
Listing 3. Call IMCL to perform installations
call %IMCL% input %HOME%<name of response file> -log <path to log file> -acceptLicense
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.
For more information on using batch files to drive Installation Manager actions, see the article Installing, updating, and scripting installations for IBM Installation Manager
Create the package
- Launch the SCCM Configuration Manager console.
- Expand the Site Database > Computer Management > Software Distribution menu items.
- Right-click on Packages and select New > Package.
- 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. When you create a package to install a product, use the appropriate name and version for that product. Click Next.
- Select the box This package contains source files, then click the Set button to indicate where to find the files for this package. 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. - Leave the default options for Distribution Settings, and Reporting. Choose which option meets your needs for Data Access.
- On the Security page, verify that the SCCM Administrator account has the appropriate security rights, then click the Next button.
- Verify that the information is correct on the Summary page. Click Next. The package creation starts. Once it is complete, click the Finish button.
Create the distribution point
- Start the SCCM Configuration Manager console.
- Expand the Site Database > Computer Management > Software Distribution > Packages menu items.
- Expand the package you created in the previous section, and right-click on the Distribution Points item.
- Select New Distribution Points.
- 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.
- Launch the SCCM Configuration Manager console.
- Expand the Site Database > Computer Management > Software Distribution > Packages menu items.
- Expand the package you created in the previous section
- Right-click on the Program item.
- Select New > Program.
- 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.
- Leave the default settings on the Requirements page.
- 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. If you want to install Installation Manager or a package in user mode, choose Run with user's rights.
- Keep the defaults already selected on the Advanced page.
- Keep the defaults already selected on the Windows Installer page.
- The Microsoft Operations Manager (MOM) Maintenance page 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.
- Verify that the information on the Summary page is correct. If the information is correct, click the Next button. The program is created.
- 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, search the Microsoft TechNet articles for How to Create a Custom Task Sequence. For information on advertising the task sequence, search the Microsoft TechNet articles for How to Advertise Task Sequences.
Additional Information
Learn
- Installation Manager
- To download Installation Manager, see IBM Installation Manager and Packaging Utility download links
- For general information on how to use the Installation Manager read the IBM Installation Manager Document.
- Read about silent installation roadmaps.
- Read the Microsoft System Center documentation.
Document Location
Worldwide
Was this topic helpful?
Document Information
More support for:
IBM Installation Manager
Component:
INSTALLATION-CONFIGURATION-MIGRATION
Software version:
All Versions
Document number:
7105312
Modified date:
04 January 2024
UID
ibm17105312