Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Microsoft Windows installer host requirements


Before you launch the BMC Cloud Lifecycle Management installer, ensure that the installer host meets the requirements described in the following sections. An installer host is the physical or VM host on which you run the installer. This topic discusses the Windows installer host requirements.

Operating system and hardware requirements

Software

Hardware

Permissions

  • Microsoft Windows Server 2012 R2 Standard Edition 64-bit
  • Oracle JRE 1.7 (64-bit)
  • Microsoft Internet Explorer 7.0 or later, or Mozilla Firefox 3.5 or later
  • Minimum 30 GB free hard-disk space for storing installation applications
  • Minimum 1 GB free hard-disk space for the installation directory
  • 2 CPUs (3-GHz dual processor)
  • Minimum 1 GB RAM during installation

These permissions apply to BMC Cloud Lifecycle Management installer host and all target hosts. You need local Windows administrator credentials to perform all the installations. The user must be:

  • The local Administrator of the system (not a domain user)
  • Added to the Administrators group on the system

You must also perform the following steps:

  1. Open Administrative tools > Local Policies > User Rights Assignments.
  2. Add the user to the Allow log on locally property.
  3. Remove the user from the Deny log on locally property, if present.

Environment variables

Ensure that the user and system environment variables on the installer host are set with the same value (for example, TMP=C:\Support and TEMP=C:\Support). Also ensure that the values of these user and system variables match on both installer and product hosts.

Port requirements

If a firewall is configured in your environment, ensure that the firewall allows communication from the BMC Cloud Lifecycle Management installer host to the target computers by using the ports listed in the following table. The installer uses these ports to run commands to check application connectivity, database connections, RSCD connectivity, remote installation status, and so on. The port numbers in the table are the default values and might change based on user input or user environment configuration. For example, the database might be installed on port 1522 instead of port 1521. In that case, you must ensure that the port is enabled in the firewall.

Note

The Cloud Portal and Database server is installed by default on portmapper; the port number assigned in that case is port 0. For the Cloud Portal and Database server, you cannot change the port number during the install.

Component

Port number

Description

BMC Cloud Lifecycle Management  Install Planner

12333, 9998

Installer ports

On the BMC Cloud Lifecycle Management installer host, ensure that port 12433 is free.

The BMC Cloud Lifecycle Management installer executes product installations remotely using a silent installation. The product installations that are launched on the target hosts use port 12333 or 9998, as applicable, during invocation on the target host. The BMC Cloud Lifecycle Management installer queries the ports over the network to check whether the installation launched successfully. If a firewall is between the BMC Cloud Lifecycle Management installer host and a target host, ensure that these ports are not blocked.

This requirement applies to all product hosts.

BMC Remedy AR System server (AR System server) and IT Management Suite

0 (default value if the portmapper is being used)

Cloud Portal and Database server, AR System server postinstallation , and Cloud Portal AR Extensions port

The default value on which Cloud Portal and Database server is installed by the BMC Cloud Lifecycle Management installer is port 0 if the AR System portmapper is being used. The BMC Cloud Lifecycle Management installer queries the port (chosen randomly by the portmapper) over the network during AR System server postinstallation  to check whether the AR System server is running. Make sure there is no firewall is between the BMC Cloud Lifecycle Management installer host and a target host.

 

 

1433 (default value)

Cloud Portal and Database server database port

When the BMC Cloud Lifecycle Management installer installs Cloud Portal and Database, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is up and running.

If the target Oracle database is installed using default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked.

 

BMC Server Automation

1433 (default value)

BMC Server Automation database port

When the BMC Cloud Lifecycle Management installer installs BMC Server Automation installation, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port. If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked.

 

 

4750

BMC Server Automation RSCD agent port

This requirement applies to all hosts (product hosts as well as the BMC Cloud Lifecycle Management installer host). If a firewall is between the BMC Cloud Lifecycle Management installer and a target host, ensure that port 4750 is not blocked, because the BMC Cloud Lifecycle Management installer runs remote commands for target host installations to the RSCD agent on the target host (which uses port 4750).

 

BMC Network Automation

1433 (default value)

BMC Network Automation database port

When the BMC Cloud Lifecycle Management installer installs the BMC Network Automation, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port. If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked.

 

Preboot Execution Environment (PXE)

1433 (default value)

When the BMC Cloud Lifecycle Management installer installs PXE, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is up and running. If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked. 

Preparing the installation planner host

Before you start installing the products in the BMC Cloud Lifecycle Management solution, prepare the Microsoft Windows computer on which you will run the installer.

To verify credentials and access

For all new installations with the installer host, verify the following credentials:

  • The Windows user credentials must have access to both the installer host, the target Enterprise-AR host, and Enterprise-AR database host.
  • The installer host, the target Enterprise-AR host, and Enterprise-AR database host must be in the same domain.

To update the BMC Server Automation RSCD agent and NSH to the required version

For new installations, the BMC Cloud Lifecycle Management installer installs version 8.5 of the BMC Server Automation Remote Server Call Daemon (RSCD) Agent and BMC Network Shell (NSH). The installer uses NSH to execute silent installation commands, which are accepted by the RSCD agent installed on the target hosts. The RSCD agent executes the commands so that the installer can remotely install the supporting BMC products.

If an existing RSCD Agent and NSH are installed, uninstall them, as described in the following procedures.

Click here to review the steps for uninstalling the BMC Server Automation RSCD agent.
  1. Select Start > Programs > Windows Control Panel and open the Add/Remove Programs utility.
  2. Select the component that you want to uninstall (for example, BMC Server Automation RSCD Agent) and click Change/Remove
  3. After the RSCD Agent is uninstalled, go to C:\Program Files\BMC Software\Bladelogic and delete the RSCD folder.
  4. Manually delete the C:\Windows\rsc folder.
  5. Restart your computer.

    If you don't restart your computer, installing the RSCD Agent can take an extended period of time to perform, sometimes over an hour.

    For more information, see Uninstalling in the BMC Server Automation 8.3.00 documentation.

Click here to review the steps for uninstalling NSH.
  1. Select Start > Programs > BMC Software > BladeLogic Server Automation Suite > Uninstall Network Shell.
  2. After the NSH is uninstalled, go to C:\Program Files\BMC Software and delete the NSH folder.
  3. Manually delete the C:\Windows\rsc folder.
  4. Restart your computer.
     For more information, see Uninstalling in the BMC Server Automation 8.3.00 documentation.

To verify product host connectivity

Perform the following steps to ensure that you can successfully launch the installation on a product host:

  1. Ensure that you can contact all target hosts (on which you want to install BMC products) from the installer computer (for example: ping <host name>.
  2. Run the ipconfig command on the target host, and verify that the IP address returned in the previous step matches the the target computer's IP address returned in this step.

To update Terminal Services configuration options

If you are using Terminal Services, update the Terminal Services configuration options as needed before running the installer. The installer runs only when Terminal Services is configured correctly.

Note

If you do not configure these items before you run the installer, an installer panel appears listing the steps required to handle these issues.

Click here to review the steps for updating the Terminal Services configuration options.
  1. From the Windows Start menu, click Run.
  2. Type gpedit.msc, and then click OK.
  3. Navigate to the Temporary folders policies:
    Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders
    or:
    Computer Configuration > Administrative Templates > Windows Components > Terminal Services > Terminal Server > Temporary folders
  4. Set the Properties of Do not delete temp folder upon exit to Enabled and then click OK.
  5. Set the Properties of Do not use temporary folders per session to Enabled and then click OK.
  6. If the settings do not take affect, complete the following steps:
    1. From the Windows Start menu, click Run.
    2. Type regedit, and then click OK.
    3. Expand HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server.
    4. Update PerSessionTempDir to 0 and DeleteTempDirsOnExit to 0.

To access target VMs from the installer computer

Before you launch the installer, ensure that you can access target VMs from the installer computer.

Note

If FTP is not enabled, use the following procedure.

Click here to review the steps.
  1. On the installer computer, click Run.
  2. Enter \\<targetmachinename>\C$ (or the D$drive) for every target computer.

If you do not see an error message, the installer is ready to install the RSCD Agent on the target host.

If you do see an error message (for example, The trust relationship between this workstation and the primary domain failed), your computer is not synced with the domain controller, and you must perform the following steps:

  1. On the target computer, open the Computer Properties dialog box.
  2. Click Advanced system settings.
  3. Click the Computer Name tab.
  4. Click Change to change the workgroup and domain settings.
  5. Select Workgroup.
  6. Enter WORKGROUP and then click OK.
  7. In the Windows Security dialog box, enter the administrator user name and password to remove the computer from the domain, and then click OK.
  8. At the change prompt, click OK.
     After you successfully change the settings, do not restart the computer.
  9. In the System Properties dialog box, click Change.
  10. Select Domain.
  11. Enter the domain.
  12. At the welcome prompt, click OK.
  13. At the change prompt, click OK.Click Close to close the Computer Properties dialog box.
  14. Restart the computer.
  15. When the computer restarts, click Run and then enter \\<targetmachine_ame>\C$.
     The installer is now ready to install the RSCD Agent on the target host.

To set the minimum JVM heap size

For optimal performance, set the minimum JVM heap size to 1024 MB. Otherwise, the install planner might hang.

To install FTP 7.5 on Windows Server 2008

Note

If you cannot mount a network shared drive, you must install FTP 7.5.

See Installing FTP 7.5 on Windows Server 2008 in the Microsoft TechNet Library.

To set screen resolution

Set your computer screen to the recommended resolution of 1280 x 800 or greater.

Related topics

Preparing-to-run-the-installer-on-a-Linux-computer

Installation-order-and-product-dependencies

Installing-BMC-Cloud-Lifecycle-Management

Base-product-versions-and-compatibility-for-upgrade

Port-mappings

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*