You must perform the following tasks before starting the installation on a Microsoft Windows server:
Perform the following steps to extract the installation files:
For either downloads or media, the file name is bna-server-v.r.mm-win64.zip
v.r.mm is a substitute for the current version, 8.5.00 in this release.
Extract the archive. The following table lists the files contained in the download:
Files contained in the download
The main installation executable
Compressed Java archive that contains installation files
Main installation files
Installation maintenance utility used for various tasks. See Running the Maintenance and Cleanup tools.
Installation cleanup utility used for various tasks. See Running the Maintenance and Cleanup tools.
The BMC Network Automation installation on a Microsoft Windows server requires a user account (for example, bcan). This account is referred to as the BCAN_USER account. You can create this account either before installation or during installation.
The user account cannot be an administrator account and must have privileges to log on locally.
This account would own all the installed files in BCAN_HOME and BCAN_DATA. It would also be used to initialize and run the embedded postgres service, if you use that option.
You can optionally use the BCAN_USER account for FTP and SCP file transfers. For more information about remote device agents and FTP/SCP file transfers, see Administering remote device agents.
Log on as an Administrator. The BCAN_USER account must be a local account. Create the BCAN_USER account under Control Panel > User Accounts as a Limited account. Assign a password to the account.
BMC strongly recommends not using the at sign (@) in the password. Some device file transfers might fail because they use the user:password@host/file format. If the password contains an at sign, the file transfer treats all characters after the at sign as the host name.
Installation of the BMC Network Automation Server requires approximately 1.2 GB of free disk storage on a Microsoft Windows server.
Do not install the software on a networked drive. You must install the software on a local drive.
To use TFTP as the file transfer protocol for devices, you must install Microsoft .NET Framework 3.5.x. To install the .NET Framework specific to your OS, see http://www.microsoft.com/en-in/download/.
If you plan to use File Transfer Protocol (FTP) or Secure Copy (SCP) for device configuration and software image management, install the FTP server (see Installing an FTP server on Windows) and the SSH/SCP server (see Installing an SSH and SCP server on Windows) per the installation instructions specified before making a configuration snapshot. The software installs a Trivial FTP (TFTP) server only on Windows platforms as part of its installation process.
If your server is running any security software (such as a firewall, anti-malware, anti-virus, or intrusion protection software) you need to ensure the software does not interfere with any of the applications installed by BMC Network Automation.
Ensure all of the following:
To successfully install the application server and remote device agent, you must enable Microsoft Windows 8.3 file names before the installation. Perform the following steps to verify or enable Windows 8.3 file names:
fsutil behavior query disable8dot3.
disable8dot=0, then Windows 8.3 file names are enabled.
disable8dot=1, then Windows 8.3 file names are disabled. Continue with the next step to enable Windows 8.3 file names.
fsutil behavior set disable8dot3 0.
Perform the following steps to disable DEP on Windows:
If Turn on DEP for all programs and services except for those I select is not selected, Click OK to close System Properties.
If you do not correctly configure the DEP feature and terminal services, when you run the installer a wizard panel appears indicating that you need to handle these issues.
Microsoft Windows Terminal Services configuration options need to be updated. Perform one of the following tasks depending on your OS version:
Windows 2008 R2
The topics on this page describe how to Microsoft SQL databases for Microsoft Windows., and
If you use a remote PostrgreSQL database, it must be initialized with UTF-8 encoding. Specify the
-encoding UTF-8 option when you initialize the database.
Read the topics in this section to understand the tasks that you need to perform on Oracle and SQL Server databases before installing the product on a Windows computer.
BMC recommends creating a user account for use only by BMC Network Automation. BMC Network Automation strictly prohibits using the sa user account.
BMC recommends creating a new schema for BMC Network Automation objects. Confirm that the user login properties has mapping to a user-defined schema.
On the SQL Server, change the isolation level of the BMC Network Automation database to
READ COMMITTED SNAPSHOT.
The BMC Network Automation Oracle or SQL Server user account must be granted the following privileges:
Oracle or SQL Server
When creating database users for the BMC Network Automation installation, ensure that the user names meet these requirements:
For more information about naming database users, see the guidelines and rules stated for the non-quoted identifiers in the Schema Object Names and Qualifiers section in the Oracle documentation.
If your database is an Oracle Real Application Cluster (RAC) using Automatic Storage Management (ASM) to manage the data file, the path to the data file must use the following format:
For example, if the data space name in your Oracle RAC environment is named
DATA, you would enter
Oracle RAC databases that are not using ASM should use the standard format, the absolute file path to the database data file.
When performing a fresh installation and selecting the Create New Database option, ensure that the SQL Server service log-on account is Local System Account.
If you are installing the BMC Network Automation server or remote device agent on a Microsoft Windows host computer that has both IPv4 and IPv6 protocols, confirm that the DNS is properly configured.
nslookup command and confirm that both IPv4 and IPv6 addresses are configured, as shown in the following example:
Windows nslookup to verify IP addresses
C:\Users\Administrator>nslookup -type=any vw-pun-bpm-qa05
vl-pun-bna-dv06.ipv6.bmc.com internet address = 10.128.251.112
vl-pun-bna-dv06.ipv6.bmc.com AAAA IPv6 address = 2001:500:100:1100:250:56ff:f