×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

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.
BMC Cloud Lifecycle Management 3.1 ... Installing Preparing for installation Setting up the installation environment

Preparing to run the installer on a Windows computer

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 by using the procedures explained in this topic:

To prepare for installation on a Linux computer, see Preparing to run the installer on a Linux computer.

Before you begin

  • For new installations, if you have an existing BMC BladeLogic Remote Server Call Daemon (RSCD) Agent and BMC 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. For a complete list of requirements, see Microsoft Windows installer host requirements.

    Note

    This task is not required for upgrades.

  • For the installer to access the target host successfully, you must be able to map C:\ (\\<hostname\c$) drive of all target hosts or set up FTP to all target hosts. This task can take several minutes to map all the drives. But if you then run the installer and you receive an error message that the trust relationship between the computer and the primary domain has failed, you run the risk of losing all your mappings after you synchronize the domain controller. Update the terminal server and configure DEP before you create the mappings. 

To uninstall 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 Console) 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 are performing an entire series of configuration actions, you can restart the computer when you are finished. 

    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.

To uninstall BMC Network Shell

  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\nsh folder.
  4. Restart your computer.
    If you are performing an entire series of configuration actions, you can restart the computer when you are finished. 
    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.

  1. From the Windows Start menu, click Run.
  2. Type gpedit.msc, and then click OK.
  3. Expand 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, and then click OK.
    3. Expand 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.

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, and then double-click System.
  2. Click the Advanced tab.
  3. In the Performance area, click Settings.

  4. If the Turn on DEP for all programs and services except for those I select option is selected, click Add.

    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. If the Turn on DEP for essential Windows programs and services only option is selected, no configuration is required.

  5. Browse to the executable, and then click Open.
    The installation program appears in the DEP program area.
  6. Click Apply, and then click OK.
  7. (Optional) Restart the computer.

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

Use this procedure if FTP is not enabled.

  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.

Related topics

Preparing to run the installer on a Linux computer
Prerequisites for installation, installation order, and product dependencies
Installing BMC Cloud Lifecycle Management

Was this page helpful? Yes No Submitting... Thank you
Last modified by John Stamps on Dec 03, 2013

Comments

Log in or register to comment.

Setting up the installation environment
Preparing to run the installer on a Linux computer
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.