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.

Summary of system requirements for Microsoft Windows

This topic summarizes the system requirements for the installer host, the supporting products, and databases used by BMC Cloud Lifecycle Management on Microsoft Windows operating systems:

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, based on your operating system. An installer host is the physical or virtual machine host on which you run the installer.

Installer host operating system requirements

 Click here to see the OS requirements for the installer host.

The following items are required:

  • Microsoft Windows Server 2008 (R2 64-bit)
  • Microsoft Internet Explorer 7.0 or later, or Mozilla Firefox 3.5 or later

Note

You need local Windows administrator credentials to perform all the installations.

Installer host hardware requirements

 Click here to see the hardware requirements for the installer host.

The following items are required:

  • Minimum 30 GB free hard-disk space for storing installation applications and minimum 1 GB free hard-disk space for the installation directory
  • 2 CPUs (3-GHz dual processor)
  • Minimum 1 GB RAM during installation

Installer host permissions

 Click here to see the permissions for the installer host.

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 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.

Installer host 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.

Installer host port requirements

 Click here to see the port requirements for the installer host.

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, 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 number in the table is the default value 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

Enterprise AR System server and cloud AR System server are installed by default on portmapper; the port number assigned in that case is port 0. For the enterprise AR System server, the port number cannot be changed during the install, but it can be changed for the cloud AR System server.
ComponentPort numberDescription
BMC Cloud Lifecycle Management  Install Planner12333, 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 is applicable for all product hosts.

BMC Remedy AR System server (AR System server) and IT Management Suite0 (default value if the portmapper is being used)

Enterprise AR System server, AR System server post-installation, Distributed Server Option (DSO),and Cloud Portal AR Extensions port

The default value on which Enterprise AR System 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 post-installation and DSO installation 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)

Enterprise AR System server database port

During the Enterprise AR System server installation using the BMC Cloud Lifecycle Management installer, 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.

 
AR System server - Cloud Database0 (default value if the portmapper is being used)

Cloud AR System server, AR System server post-install, DSO, and Cloud Extensions port

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

 
 1433 (default value)

Cloud AR System server database port

During the AR System server - Cloud Database installation using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is 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.

 
BMC Server Automation1433 (default value)

BMC Server Automation database port

During the BMC Server Automation installation using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is 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.

 
 4750

BMC Server Automation RSCD agent port

This requirement is applicable for 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 Automation1433 (default value)

BMC Network Automation database port

During the BMC Network Automation install using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is 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.

 
BMC ProactiveNet Performance Management10843 (default value)

Requires port for BMC Server Automation web services

During the BMC ProactiveNet Performance Management installation using the BMC Cloud Lifecycle Management installer, the installer executes commands over the network to check whether the BMC Server Automation web service is running. The BMC ProactiveNet Performance Management connects to BMC Server Automation using the same port to load BMC Server Automation packages.

 
Preboot Execution Environment (PXE)1433 (default value)During the PXE install using the BMC Cloud Lifecycle Management installer, 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. 

For more information about the ports used by BMC Cloud Lifecycle Management, see Port mappings.

Preparing the installer host

 Click here to see a list of the preparatory tasks you must complete for the installer 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 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.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.

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. 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 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 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.

Windows supporting product host requirements

This section 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. The requirements outlined in this topic are for a POC deployment only. For more information about product-specific hardware requirements per deployment type, see deployment architecture and sizing guidelines.

Common supporting product host requirements for all operating systems

Although the hardware and software requirements and pre-installation tasks differ according to each product in the solution, certain requirements are common for the supporting product hosts on both Microsoft Windows and Linux.

 Click here for steps that guide you through these requirements.

    Page not found for multiexcerpt macro.
The page: Common product host requirements was not found. Please check/update the page name used in the 'multiexcerpt-include macro.

BMC Remedy product requirements

The following table lists the product-specific requirements for the BMC Remedy products.

Product or componentRequirements
BMC Remedy AR System & IT Service Management Suite – Primary
 Click here to see the hardware, software, and product-specific requirements.

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
 Click here to see the hardware, software, and product-specific requirements.

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 & IT Service Management Suite – Secondary
 Click here to see the hardware, software, and product-specific requirements.

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 Remedy AR System Server Cloud Database – Secondary

 Click here to see the hardware, software, and product-specific requirements.

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
 Click here to see the hardware, software, and product-specific requirements.

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 Atrium Core Web Registry requirements

 Click here to see the hardware, software, and product-specific requirements for the BMC Atrium Core Web Registry.

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

The following table lists the product-specific requirements for the BMC Server Automation components.

Product or componentRequirements
BMC Server Automation – Application Server & Console
 Click here to see the hardware, software, and product-specific requirements.

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.

BMC Server Automation – Multiple Application Server (MAS)

 Click here to see the hardware, software, and product-specific requirements.

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 – Remote System Call Daemon (RSCD) Agent

 Click here to see the hardware, software, and product-specific requirements.

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 Server Automation – Advanced Repeater (Optional)
 Click here to see the hardware, software, and product-specific requirements.

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

PXE Server (Optional
 Click here to see the hardware, software, and product-specific requirements.

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 – File Server (Optional)
 Click here to see the hardware, software, and product-specific requirements.

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 Atrium Orchestrator product requirements

The following table lists the product-specific requirements for the BMC Atrium Orchestrator components.

Product or componentRequirements
BMC Atrium Orchestrator – Configuration Distribution Peer
 Click here to see the hardware, software, and product-specific requirements.

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)
 Click here to see the hardware, software, and product-specific requirements.

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

The following table lists the product-specific requirements for the BMC Network Automation components.

Product or componentRequirements
BMC Network Automation
 Click here to see the hardware, software, and product-specific requirements.

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
 Click here to see the hardware, software, and product-specific requirements.

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 requirements

This section applies to the following BMC ProactiveNet Performance Management components:

  • BMC ProactiveNet Central Server
  • BMC ProactiveNet Server
  • BMC ProactiveNet Data Collection Host
 Click here to see the hardware, software, and product-specific requirements.

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

The following table  lists the product-specific requirements for the BMC Cloud Lifecycle Management components.

Product or componentRequirements
Cloud Database Extensions
 Click here to see the hardware, software, and product-specific requirements.

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 
 Click here to see the hardware, software, and product-specific requirements.

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 
 Click here to see the hardware, software, and product-specific requirements.

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 
 Click here to see the hardware, software, and product-specific requirements.

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

Database requirements for Windows

The following sections outline the database requirements for Windows platforms.

Requirements common to database platforms

This section outlines the requirements that are common to Microsoft SQL Server and Oracle.

Supported database versions

The BMC Cloud Lifecycle Management solution supports the following databases:

  • Microsoft SQL Server 2008 R2 Enterprise 64-bit (if you require Cluster capabilities) on Microsoft Windows 2008 R2 64-bit OS.
    Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.

    Microsoft Support provides useful information on determining the version and edition of SQL Server and its components.

  • Oracle Database 11g R2 64-bit on Red Hat Enterprise Linux 5.5 64-bit OS

Unicode and character set requirements for databases

The following Unicode and character set requirements apply to both MS SQL Server and Oracle databases:

  • You must synchronize all your databases so that their character sets and Unicode settings are correctly aligned with their <product>, for example, BMC Remedy AR System settings.
  • You must run Unicode to Unicode or non-Unicode to non-Unicode. Do not mix these settings.
  • For Oracle, you must set the character sets to AL32UTF8.
  • For MS SQL Server, you must set the Unicode data types to nchar, nvarchar, and ntext.

SQL Server requirements for Windows

For SQL Server databases, you can have the installer create a database during the installation process or you can pre-create a database for your products, as indicated in the table in product-specific database requirements. However, the installer requires you to authenticate a pre-created database. The BMC Cloud Lifecycle Management solution supports Microsoft SQL Server 2008 R2 Enterprise 64-bit (if you require Cluster capabilities) on Microsoft Windows 2008 R2 64-bit OS. Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.

Note

You must have DBA credentials to create the database and users for the pre-created database and installer-created database option.

Pre-create database support and requirements for Windows

In the table in product-specific database requirements, the values for the pre-created database support for SQL Server are as follows:

  • Yes, but optional — A pre-created database is supported. However, you can optionally choose to have the installer create the database during the installation process.
  • Yes, and mandatory — You must use a pre-created database.
  • No — A pre-created database is not supported. You must allow the installer to create a database and a user.

Note

The BMC Cloud Lifecycle Management Installer creates an SQL Server database with the default data and log file sizes listed in the table in the following section, and users for products that require them. If you want to use the pre-created database option, ensure that you use the file size details listed in the table.

For more information about pre-created databases, see the documentation for the respective product in the documentation for related products.

Windows database requirements for supporting products

The following table lists the requirements for SQL Server databases. For specific preparatory tasks that you must perform before you complete product installation, see the Additional information column.

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

Comments