Preparing to run the installer on a Windows computer


Before you start installing the products in the BMC Cloud Lifecycle Management solution, prepare your installer host by using the procedures explained in this topic:

For preparing your Linux installer host, see Preparing to run the installer on a Linux computer.

Uninstall  BMC BladeLogic RSCD Agent and NSH

For new installations, if you have an existing BMC BladeLogic RSCD Agent and BMC BladeLogic Network Shell (NSH) installed on your installer host, you must uninstall them. Because the RSCD agent will be installed with every BMC product and the NSH will be installed on the installer host, you must uninstall any existing versions. To uninstall the RSCD agent and the NSH:

Warning

Note

You need to uninstall the RSCD agent and NSH only for a new installation. This step is not required for upgrades.

  1. Go to Start > Programs > BMC BMC BladeLogic Server Automation  and click the RSCD uninstaller.
  2. After the RSCD agent is uninstalled, go to C:\Program Files\BMC Software\Bladelogic and delete the RSCD folder.
  3. Manually delete the c:\Windows\rsc folder.
  4. Reboot your computer.
     For more information, see the BMC BladeLogic Server Automation 8.1.00 Installation Guide.

Verify product host connectivity

To ensure that you can successfully launch the installation on a product host:

  1. Make sure that you are able to ping all target hosts (on which you want to install BMC products) from the installer machine, 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.

Map the target host hard drive

For the installer to access the target host successfully, you must map C:\ (\\<hostname\c$) drive of all target hosts or set up FTP to all target hosts.

Access target VMs from the installer computer

Before you launch the BMC Cloud Lifecycle Management installer, make sure that you can access target VMs from the installer computer.

Warning

Note

Use this procedure if FTP is not enabled.

  1. On the installer computer, click Run.
  2. Enter \\<target_machine_name>\c$ (or the d$ drive) for every target computer.
    • If you do not see an error, then the installer is ready to install the RSCD agent on the target host.
    • If you do see an error (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 Computer Properties.
    2. Click Advanced system settings.
    3. Click the Computer Name tab.
    4. Click Change to change its workgroup and domain settings.
    5. Select Workgroup.
    6. Enter WORKGROUP and then click OK.
    7. In the Windows Security dialog box, enter 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.
    14. Click Close to shut the Computer Properties dialog box.
    15. Restart the computer.
    16. When the computer restarts, click Run and then enter \\<target_machine_name>\c$.
       The installer is now ready to install the RSCD agent on the target host.

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 will not run until you configure Terminal Services correctly.

Warning

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.

  1. From the Windows Start menu, click Run.
  2. Type gpedit.msc; then click OK.
  3. Go to 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. (optional) Restart the computer.
  7. If the settings do not take affect, complete the following steps:
    1. From the Windows Start menu, click Run.
    2. Type regedit; then click OK.
    3. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
    4. Update PerSessionTempDir to 0 and DeleteTempDirsOnExit to 0.
    5. (optional) Restart the computer.

To configure the DEP feature

If you are using the data execution prevention (DEP) feature in Windows, configure DEP for executable programs.

Warning

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.

  1. From the Windows Start menu, click Control Panel; then double-click System.
  2. Click the Advanced tab.
  3. In the Performance area, click Settings.
  4. On the Data Execution Prevention tab, verify if the Turn on DEP for all programs and services except those I select option is selected.
     If the Turn on DEP for essential Windows programs and services only option is selected, no configuration is required. 

    Warning

    Note

    If you do not select the Turn on DEP for all programs and services except those I select option, and then perform the remaining steps in this procedure, the installer might not run correctly.

  5. If the Turn on DEP for all programs and services except for those I select option is selected, click Add.
  6. Browse to the executable, and then click Open.
     The installation program appears in the DEP program area.
  7. Click Apply; then click OK.
  8. (optional) Restart the computer.

Related topics

Preparing-to-run-the-installer-on-a-Linux-system
Installation-order-and-product-dependencies
Installing-BMC-Cloud-Lifecycle-Management-on-Windows

 

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

BMC Cloud Lifecycle Management 2.1.00