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.

Meeting requirements for Windows product hosts

This topic lists the hardware and software requirements, and the tasks that you must perform before you install the BMC Cloud Lifecycle Management solution on Microsoft Windows. For more information about product-specific hardware requirements per deployment type, see deployment architecture and sizing guidelines.

This topic contains the following sections:

Requirements for installing all Windows product hosts

  1. Define a local Windows administrator to perform all installations. The user must be:

    • The local Administrator of the system (not a domain user)
    • Added to the Administrators group on the system
  2. Grant appropriate rights to the user:

    1. Open Administrative tools > Local Security Policy > 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.
  3. Standardize the user and system environment variables on the target product hosts so that they are set with the same value (for example, TMP=C:\AppData and TEMP=C:\AppData). 
  4. Set the system clock to the same time and time zone on all the product hosts.

  5. Delete any files from the C:\Windows\Temp folder. This will speed up the process of installing the RSCD agent. 
  6. Verify the product host connectivity 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.

    3. Record the IP addresses of all the target hosts. You might need these later during installation, for example, if you need to use an IP address in the installer because the host name does not work. 
  7. Ensure that a pre-8.3 version of the BMC Server Automation Remote Server Call Daemon (RSCD) Agent is not installed on any target host. 

    For new installations, the BMC Cloud Lifecycle Management installer installs version 8.3 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, perform one of the following actions:

    • Upgrade to version 8.3.
    • If you are unable to upgrade the RSCD agent and NSH, 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 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.

     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\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.
  8. Stop and disable the Windows Firewall service on all product hosts:
    1. Go to Start > Control Panel > Windows Firewall.
    2. Start the Windows Firewall service, if necessary.
    3. In the Windows Firewall dialog box, click Change Settings.
    4. In the Windows Firewall Settings dialog box, click Off and then click OK.
    5. Disable the Windows Firewall service. 
      For more information about stopping or disabling the firewall service, see the I Need to Disable Windows Firewall topic in the Microsoft TechNet Library. 
  9. To install the products successfully on all product hosts, you must have administrator privileges for actions, such as setting system environment variables and restarting services. Therefore, having only administrator privileges is not enough. You must set the User Account Control (UAC) to disable the Administrator Approval Mode, as follows:
    1. Open Administrative tools > Local Security Policy > Local Policies > Security Options.
    2. From the list of security options displayed, double-click the User Account Control: Run all administrators in Admin Approval Mode option and set it to Disabled.
  10. Install Microsoft Internet Explorer or Mozilla Firefox on any host on which you want to access the mid tier.
    For more information about the version of web browsers to install, see http://www.bmc.com/support.

  11. Configure the terminal services.

     Click here to review the steps.
    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.
  12. Restart the computer.
  13. (Optional) Install SAP BusinessObjects XI R 3.1 SP2 for reporting purposes.

BMC Remedy product requirements

This section lists the product-specific requirements for the BMC Remedy products.

BMC Remedy AR System and IT Service Management Suite – Primary

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 10526 MB 
    • Temp (tmp) directory: 9064 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)
  • Oracle JRE 1.6. update 31
  • Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities. Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.

Product-specific requirements: For remote database installations, configure credentials for the startup account of the Microsoft SQL Server service as follows:

  1. On your remote database computer, go to Administrative Tools > Services.
  2. Select SQL Server (MSSQLServer) service and right-click to open the pop-up menu.
  3. Select Properties and select the Log on tab.
  4. Provide administrator credentials in the This account field.

    Ensure that the Administrator user that you provide in this step is added to the Administrators group of the target Enterprise AR System server.

  5. Save the changes and restart the service.

BMC Remedy AR System – Cloud Database Primary

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 5223 MB 
    • Temp (tmp) directory: 2935 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)
  • Oracle JRE 1.6. update 31
  • Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities. Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.

Product-specific requirements: None

BMC Remedy AR System Server Cloud Database – Secondary

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 5223 MB 
    • Temp (tmp) directory: 2935 MB
  • Windows 2008 R2 Enterprise Edition (SP1 64-bit)
  • Oracle JRE 1.6. update 31
  • Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities (share the database with BMC Remedy AR System Server - Cloud Database Primary). Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.

Product-specific requirements: None

BMC Remedy Mid Tier

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 360 MB 
    • Temp (tmp) directory: 2609 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)
  • Oracle JRE 1.6. update 31

Product-specific requirements: None

BMC Remedy AR System and IT Service Management Suite – Secondary

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 10526 MB 
    • Temp (tmp) directory: 9064 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)
  • Oracle JRE 1.6. update 31
  • Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities (shares the database with BMC Remedy AR System & IT Service Management Suite - Primary). Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.

Product-specific requirements: None

BMC Atrium Core Web Registry requirements

Hardware and software requirements:

  • 2 CPUs
  • 6 GB RAM
  • Hard disk space: 
    • Installation directory: 1345 MB 
    • Temp (tmp) directory: 5223 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)
  • Oracle JRE 1.6. update 31

Product-specific requirements: None

BMC Server Automation product requirements

This section lists the product-specific requirements for the BMC Server Automation products.

BMC Server Automation – Application Server and Console

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 745 MB 
    • Temp (tmp) directory: 1626 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)
  • Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities (for remote or local database)
    Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations

Product-specific requirements: Before you begin installing BMC Server Automation – Application Server & Console, ensure that port 9700 is available on the host on which you want to install the product.

PXE Server (Optional)

Hardware and software requirements:

  • 2 CPUs
  • 1 GB RAM
  • Hard disk space: 
    • Installation directory: 46 MB 
    • Temp (tmp) directory: 1626 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)

Product-specific requirements: For more information, see the IIS 6 Compatibility components not installed topic in the Microsoft TechNet Library.

BMC Server Automation – Advanced Repeater (Optional)

Hardware and software requirements:

  • 2 CPUs
  • 1 GB RAM
  • Hard disk space: 
    • Installation directory: 265 MB 
    • Temp (tmp) directory: 391 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)

Product-specific requirements: None

BMC Server Automation – Multiple Application Server (MAS)

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 9 GB 
    • Temp (tmp) directory: 3 GB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)
  • Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities (shares the database with BMC Server Automation Application Server & Console). 
    Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations

Product-specific requirements: Before you begin installing BMC Server Automation – Application Server & Console, ensure that port 9700 is available on the host on which you want to install the product.

BMC Server Automation – File Server (Optional)

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory:  50 MB 
    • Temp (tmp) directory:  1 GB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit) 

Note

Storage on the File Server requires additional hard disk space.

Product-specific requirements: None 

BMC Server Automation – Remote System Call Daemon (RSCD) Agent

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: Installation directory: 100 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)

Product-specific requirements: None

BMC Atrium Orchestrator product requirements

This section lists the product-specific requirements for the BMC Atrium Orchestrator products.

BMC Atrium Orchestrator – Configuration Distribution Peer

Hardware and software requirements:

  • 2 CPUs
  • 2 GB RAM
  • Hard disk space: 
    • Installation directory: 590 MB 
    • Temp (tmp) directory: 3598 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)

Product-specific requirements: None

BMC Atrium Orchestrator – Configuration Distribution Peer (HA)

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 590 MB 
    • Temp (tmp) directory: 3598 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)
  • Msvcr71.dll

Product-specific requirements: None

For more information about a missing Msvcr71.dll file, see:

BMC Network Automation product requirements

This section lists the product-specific requirements for the BMC Network Automation products.

BMC Network Automation

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 1245 MB 
    • Temp (tmp) directory: 997 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)
  • Microsoft SQL Server 2008 R2 Enterprise 64-bit if you require Cluster capabilities (for remote or local databases). Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations
  • Microsoft .Net framework

Product-specific requirements: Ensure that you have Microsoft Windows 8.3 file-name setting enabled before the installation. For more information, see enabling Windows 8.3 file names.

 

Note

On new Windows installations of BMC Network Automation where BMC now supports MS SQL Server 2014, the installation fails if you do not specify the highest value of the data file path or log file path available. Enter the highest version of the path, for example:

  • C:\Program Files Microsoft SQL Server\MSSQL12. MSSQLSERVER\MSSQL\DATA\bcan_data.mdf (as the data file path)
  • C:\Program Files Microsoft SQL Server\MSSQL12. MSSQLSERVER\MSSQL\DATA\bcan_log.ldf (as the log file path)


BMC Network Automation – Device Agent

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 2093 MB 
    • Temp (tmp) directory: 770 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)

Product-specific requirements: Ensure that you have Microsoft Windows 8.3 file-name setting enabled before the installation. For more information, see enabling Windows 8.3 file names.

BMC ProactiveNet Performance Management

This section lists requirements for the following BMC ProactiveNet Performance Management components:

  • BMC ProactiveNet Central Server
  • BMC ProactiveNet Server
  • BMC ProactiveNet Data Collection Host

Hardware and software requirements:

  • 2 CPUs (for each product)
  • 4 GB RAM (for each product)
  • Hard disk space: 
    • Installation directory: 16642 MB for Central Server and 11731 for Server 
    • Temp (tmp) directory: 9261 MB for Central Server and 9406 for Server
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)

Product-specific requirements:

  • Ensure that you can log on to the BMC Server Automation application serverand that you can access the BMC Server Automation web services. 
    1. Open a command window.
    2. Change directories to the blasadmin utility (C:\Program Files\BMC Software\BladeLogic\NSH\bin\ on Windows and /NSH/bin/ on Linux).
    3. Enter the following command:
      blasadmin show AppServer enableWebServices
      If the value returned is true, the web services are running.

If the value returned is is false, start the web services and restart the application server:

    1. In the command window, enter the following command in the NSH\bin directory:
      blasadmin set AppServer enableWebServices true
    2. Restart the application server.
  • Ensure that ports 80, 1099, and 8080 are available and are not being used by other products. For example, you cannot install BMC ProactiveNet Central Server on the target computer if Microsoft IIS, the World Wide Web Publishing Service, or the SQL Server Reporting Service is using port 80.
  • Stop and disable the Windows Firewall service on the computers targeted for the BMC Proactive Central Server and BMC ProactiveNet Server:
    1. Go to Start > Control Panel > Windows Firewall.
    2. Start the Windows Firewall service, if necessary.
    3. In the Windows Firewall dialog box, click Change Settings.
    4. In the Windows Firewall Settings dialog box, click Off and then click OK.
    5. Disable the Windows Firewall service. 
    6. Restart the computer.
       For more information about stopping or disabling the firewall service, see the I Need to Disable Windows Firewall topic in the Microsoft TechNet Library. 
  • Ensure that BMC Server Automation Application Server host can ping the BMC ProactiveNet hosts (and vice versa) by the shortname and the fully-qualified domain name.
  • For all three products, ensure that you can view view both the 8.3 short name and the long name for the installation directory. Before starting the installation, you should be able to create a directory over 8 characters in a command line window, and then enter dir /x.
     
    If the 8.3 name is missing, a setting is not correct. You must then set Ntfsdisable8dot3namecreation in the Windows Registry to 2. 
    1. Select Start > Run > regedit.
    2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
    3. Select NtfsDisable8dot3NameCreation and edit it.
    4. Set Value data to 2.
    5. Click OK.
    6. Restart the computer after you make changes to the Registry.
      When you finish, ensure that you can see both the 8.3 short name and the long name by entering dir /x in a command window.

BMC Cloud Lifecycle Management requirements

This section lists the product-specific requirements for the BMC Cloud Lifecycle Management components.

Cloud Database Extensions

Hardware and software requirements: Install the Cloud Database Extensions on the same host as BMC Remedy AR System – Cloud Database. 

Hard disk space:

  •   Installation directory: 521 MB 
  •   Temp (tmp) directory: 1933 MB

Product-specific requirements: None

Cloud Platform Manager

Hardware and software requirements:

  • 2 CPUs
  • 2 GB RAM
  • Hard disk space: 
    • Installation directory: 521 MB 
    • Temp (tmp) directory: 1933 MB
  • Windows 2008 R2 Enterprise Edition SP1 (64-bit)
  • Oracle JRE 1.6. update 31 (Optionally, you can install the JRE that is bundled with the product or you can use an existing installation.

Product-specific requirements: None

Cloud Portal AR Extensions – Primary

Hardware and software requirements: Install the Cloud Portal AR Extensions on the same host as BMC Remedy AR System & IT Service Management Suite. 

 
Hard disk space:

  •  Installation directory: 521 MB
  •  Temp (tmp) directory: 1933 MB

Product-specific requirements: None

Cloud Portal AR Extensions – Secondary

Hardware and software requirements: Install the Cloud Portal AR Extensions – Secondary on the same host as BMC Remedy AR System & IT Service Management Suite – Secondary. 

Hard disk space:

  •  Installation directory: 521 MB
  •  Temp (tmp) directory: 1933 MB

Product-specific requirements: None

Related topics

To understand the complete requirements for each product in the solution, review the following topics:

Where to go from here

Copy of Installation order and product dependencies

Was this page helpful? Yes No Submitting... Thank you

Comments