2.1.1 Manager Installation [Windows Manager]

Software preparation and checks are explained in the following sections.

This section explains the preparations and checks required before commencing the installation of Resource Orchestrator.

Host Name Checks

It is necessary to set the host name (FQDN) for the admin server to operate normally. Describe the host name in the hosts file, using 256 characters or less. In the hosts file, for the IP address of the admin server, configure the host name (FQDN) and then the computer name.

hosts File

System_drive\Windows\System32\drivers\etc\hosts

Note

When configuring the hosts file, note the following.

Do not set the host name (FQDN) and the computer name to "127.0.0.1".

Example

When configuring the admin server with the IP address "10.10.10.10", the host name (FQDN) "remote1.example.com", and the computer name "remote1"

10.10.10.10 remote1.example.com remote1
127.0.0.1 localhost.localdomain localhost

For the admin client, either configure the hosts file so access to the admin server is possible using the host name (FQDN), or name resolution using a DNS server.

System Time Checks

Set the same system time for the admin server and managed servers.

Exclusive Software Checks

Before installing Resource Orchestrator, check that the software listed in "2.4.2.5 Exclusive Software" in the "Design Guide VE" and the manager of Resource Orchestrator have not been installed on the system.
Use the following procedure to check that exclusive software has not been installed.

Open [Add or Remove Programs] on the Windows Control Panel.
The [Add or Remove Programs] window will be displayed.
Check that none of the software listed in "2.4.2.5 Exclusive Software" in the "Design Guide VE" or the following software are displayed.
- "ServerView Resource Orchestrator Manager"
If the names of exclusive software have been displayed, uninstall them according to the procedure described in the relevant manual before proceeding.
If managers of an earlier version of Resource Orchestrator have been installed, they can be upgraded. Refer to "E.2 Manager".
When reinstalling a manager on a system on which the same version of Resource Orchestrator has been installed, perform uninstallation referring to "11.1 Manager Uninstallation", and then perform the reinstallation.
Information
For Windows Server 2008 or later, select [Programs and Features] from the Windows Control Panel.

Note

When uninstalling exclusive software, there are cases where other system operation administrators might have installed the software, so check that deleting the software causes no problems before actually doing so.

Required Software Preparation and Checks

Before installing Resource Orchestrator, perform the following operations.
In addition, check that the required software, such as ServerView Operations Manager, given in "2.4.2.4 Required Software" in the "Design Guide VE" has been installed. If it has not been installed, install it before continuing.

When operating managers in cluster environments, refer to "Appendix D Manager Cluster Operation Settings and Deletion" and "D.2.1 Preparations", and perform preparations and checks in advance.

Microsoft LAN Manager Module
Before installing Resource Orchestrator, obtain the Microsoft LAN Manager module from the following FTP site.
The Microsoft LAN Manager module can be used regardless of the CPU architecture type (x86, x64).
URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe
Prepare for the following depending on the architecture of the installation target.
- When installing a manager on Windows 32-bit (x86)
  The Microsoft LAN Manager module can be installed without extracting it in advance.
  Deploy the obtained module to the folder that has been set for environment_variable%SystemRoot%.
- When installing a manager on Windows 64-bit (x64)
  The obtained module must be extracted using the Expand command on a computer with x86 CPU architecture.
  The obtained module is for x86 CPU architecture, and cannot be extracted on computers with x64 CPU architecture.
  For details on how to extract the module, refer to the following examples:
  Example
  When dsk3-1.exe was deployed on c:\temp
  >cd /d c:\temp <RETURN>
  >dsk3-1.exe <RETURN>
  >Expand c:\temp\protman.do_ /r <RETURN>
  >Expand c:\temp\protman.ex_ /r <RETURN>
  Use the Windows 8.3 format (*) for the folder name or the file name.
  After manager installation is complete, the extracted Microsoft LAN Manager module is no longer necessary.
  * Note: File names are limited to 8 characters and extensions limited to 3 characters.
  After extracting the following modules, deploy them to the folder that has been set for environment_variable%SystemRoot%.
  - PROTMAN.DOS
  - PROTMAN.EXE
  - NETBIND.COM
When installing Resource Orchestrator to an environment that already has ServerView Deployment Manager installed, it is not necessary to obtain the Microsoft LAN Manager module.

Settings for ServerView Operations Manager
In order to open the console screen of managed server, register the account of Remote Management Controller in ServerView Operations Manager.
For the settings, refer to the ServerView Operations Manager manual.
- Settings for ServerView Operations Manager 4.X for Windows
  In order for Resource Orchestrator to operate correctly, ensure that when installing ServerView Operations Manager for Windows you do not select "IIS (MS Internet Information Server)" for Select Web Server.
  For the settings, refer to the ServerView Operations Manager 4.X for Windows manual.

SNMP Trap Service Settings
In order for Resource Orchestrator to operate correctly, the following settings for the standard Windows SNMP trap service are required.
- Open [Services] from [Administrative Tools] on the Windows Control Panel, and then configure the startup type of SNMP Trap service as [Manual] or [Automatic] on the [Services] window.
  Set the service status to "Started".
Settings for ServerView Virtual-IO Manager
When using VIOM, in order for Resource Orchestrator to operate correctly, ensure that the following settings are made when installing ServerView Virtual-IO Manager for Windows.
- When using the I/O Virtualization Option
  Clear the [Select address ranges for IO Virtualization] checkbox on the virtual I/O address range selection window.
- When not using the I/O Virtualization Option
  Check the [Select address ranges for IO Virtualization] checkbox on the virtual I/O address range selection window, and then select address ranges for the MAC address and the WWN address.
  When there is another manager, select address ranges which do not conflict those of the other manager.
For details, refer to the ServerView Virtual-IO Manager for Windows manual.
DHCP server installation
Installation of the Windows standard DHCP Server is necessary when managed servers belonging to different subnets from the admin server are to be managed.
Depending on the functions used, it may necessary to configure the router settings. For details, refer to "7.6 Configuring the Network Environment" in the "Design Guide VE".
When registering managed servers that belong to a different subnet from the admin server, they must be registered on the admin LAN subnet in advance.
For details, refer to "7.8 Registering Admin LAN Subnets" in the "User's Guide VE".
Install the DHCP Server following the procedure below:
1. Add DHCP Server to the server roles.
  Perform binding of the network connections for the NIC to use as the admin LAN.
  For the details on adding and binding, refer to the manual for Windows.
2. Open [Services] from [Administrative Tools] on the Windows Control Panel, and then configure the startup type of DHCP Server service as [Manual] on the [Services] window.
3. From the [Services] window, stop the DHCP Server service.
  When an admin server is a member of a domain, perform step 4.
4. Authorize DHCP servers.
  1. Open [DHCP] from [Administrative Tools] on the Windows Control Panel, and select [Action]-[Managed authorized servers] on the [DHCP] window.
    The [Manage Authorized Servers] window will be displayed.
  2. Click <Authorize>.
    The [Authorize DHCP Server] window will be displayed.
  3. Enter the admin IP address of the admin server in [Name or IP address].
  4. Click <OK>.
    The [Confirm Authorization] window will be displayed.
  5. Check the [Name] and [IP Address].
  6. Click <OK>.
    The server will be displayed in the [Authorized DHCP servers] of the [Manage Authorized Servers] window.
ETERNUS SF Storage Cruiser
When using ESC, configure the Fibre Channel switch settings in advance.

Required Patch Checks

Before installing Resource Orchestrator, check that the required patches for the manager listed in "2.4.2.2 Required Patches" in the "Design Guide VE" have been applied.

If they have not been applied, apply them before continuing.

User Account Checks

This product automatically creates the user accounts listed below - if an application is using these OS user accounts, ensure there is no impact on the application before deleting them:

rcxdb (for connecting to the database)

Single Sign-On Preparation and Checks (when used)

To use Single Sign-On (SSO) coordination, before installing Resource Orchestrator, certificate preparation and user registration of an administrator (privileged user) with the directory service are required.
For details, refer to "Chapter 10 Installing and Defining Single Sign-On" in the "Design Guide VE".

2.1.1.3 Collecting and Checking Required Information

Before installing Resource Orchestrator, collect required information and check the system status, then determine the information to be specified on the installation window. The information that needs to be prepared is given below.

Installation Folder
Decide the installation folder for Resource Orchestrator.
Note that folders on removable disks cannot be specified.
Check that there are no files or folders in the installation folder.
Check that the necessary disk space can be secured on the drive for installation.
For the amount of disk space necessary for Resource Orchestrator, refer to "2.4.2.6 Static Disk Space" and "2.4.2.7 Dynamic Disk Space" in the "Design Guide VE".
Image File Storage Folder
The image file storage folder is located in the installation folder.
Check that sufficient disk space can be secured on the drive where the storage folder will be created.
For the necessary disk space, refer to "2.4.2.7 Dynamic Disk Space" in the "Design Guide VE".
For details of how to change the image file storage folder, refer to "5.8 rcxadm imagemgr" in the "Reference Guide (Command) VE".
Port Number
For details on port numbers, refer to "2.1.1.4 Checking Used Port Numbers".
Directory Service Connection Information for Single Sign-On of ServerView Operations Manager
Confirm that the directory service used for Single Sign-On of ServerView Operations Manager is correctly configured.
This can be performed using either of the following procedures:
- Log in to ServerView Operations Manager.
  Refer to the following manuals:
  - Manual for ServerView Operations Manager:
    "ServerView user management via an LDAP directory service" in "FUJITSU Software ServerView Suite User Management in ServerView"
  - Manual for ServerView Operations Manager:
    "Starting ServerView Operations Manager" in "FUJITSU Software ServerView Suite ServerView Operations Manager"
- Perform modification install of ServerView Operations Manager.
  When performing modification installation, the settings of directory service can be checked.
  Refer to the following manuals:
  - Manual for ServerView Operations Manager:
    "ServerView user management via an LDAP directory service" in "FUJITSU Software ServerView Suite User Management in ServerView"
  - Manual for ServerView Operations Manager:
    "Modify installation of Operations Manager software" in "FUJITSU Software ServerView Suite ServerView Operations Manager Installing ServerView Operations Manager Software under Windows"
  If the settings of the directory service for ServerView Operations Manager are correct, exit the modification installation without making any changes.
  If there are errors in the settings of the directory service for ServerView Operations, perform modification installation of ServerView Operations Manager to correct the errors.
ServerView Operations Manager V6.1 and later include OpenDJ as a directory service.
In the following descriptions, when "OpenDS" is used, replace it with "OpenDJ".

Parameters Used for Installation

The following table contains the parameters used for installation.

No.	Window	Entry	Description
1	Installation Folder Selection	Installation Folder	This is the folder where Resource Orchestrator is installed. When using a 64-bit (x64) OS Default value: C:\Program Files (x86)\Resource Orchestrator When using a 32-bit (x86) OS Default value: C:\Program Files\Resource Orchestrator The installation folder can contain 45 characters or less including the drive letter and "\". A path starting with "\\" or a relative path cannot be specified. Alphanumeric characters and blank spaces (" ") can be used. However, the "C:\Program Files (x86)" part of the default value of 64-bit OSs is the exception. Specify an NTFS disk. Note When using 64-bit Windows Server OSs, the following folder names cannot be specified for the installation folders. "Program Files" Folder When using 64-bit Windows Server OSs, if the drive letter is changed from the default value, the following folder name cannot be specified for the installation folder. "Program Files (x86)" Folder
2	Administrative User Creation	User Account	This is the user account name to be used for logging into Resource Orchestrator as an administrative user. When using Single Sign-On Specify the user registered in the directory service in " Single Sign-On Preparation and Checks (when used)" in "2.1.1.2 Software Preparation and Checks". Specifying the administrator account, "Administrator", of ServerView Operations Manager enables Single Sign-On coordination with ServerView Operations Manager when the OpenDS that is included with ServerView Operations Manager is used. When not using Single Sign-On The name must start with an alphabetic character and can be up to 16 alphanumeric characters long, including underscores ("_"), hyphens ("-"), and periods, ("."). Input is case-sensitive.
		Password	The password of the administrative user. Specify when not using Single Sign-On The string must be composed of alphanumeric characters and symbols, and can be up to 16 characters long.
		Retype password
3	Admin LAN Selection	Network to use for the admin LAN	This is the network to be used as the admin LAN. Select it from the list.
4	Authentication Method Selection	Authentication Method	Select one of the following options. "Internal Authentication" "ServerView Single sign-on (SSO)"

2.1.1.4 Checking Used Port Numbers

Ports Automatically Set in the services File of the System

When Resource Orchestrator is installed, the following port numbers used by it will automatically be set in the services file of the system.

If the following port numbers used by Resource Orchestrator are being used for other applications, a message indicating that the numbers are in use is displayed when the installer is started, and installation will stop.
In that case, describe the entries for the following port numbers used by Resource Orchestrator in the services file using numbers not used by other software, and then start the installer.

Ports Automatically Set in the services File of the System

# service name port number/protocol name
nfdomain      23455/tcp
nfagent       23458/tcp
rcxmgr        23460/tcp
rcxweb        23461/tcp
rcxtask       23462/tcp
rcxmongrel1   23463/tcp
rcxmongrel2   23464/tcp
rcxdb         23465/tcp

Checking Port Usage Status

Execute the "Environment setup conditions check tool" in "2.1.1.5 Configuration Parameter Checks" to check the port usage status.
For ports with "is in use" displayed for the result of "Port status", confirm that those ports are used with the purpose of usage for Resource Orchestrator defined in C:\Windows\System32\drivers\etc\services.
When ports being are used for something other than Resource Orchestrator, change the ports to use.

For the port information used by Resource Orchestrator, refer to "Appendix A Port List" in the "Design Guide VE".

Changing Port Numbers

To change port numbers after installing the manager, refer to the following:

"8.2 Changing Port Numbers" in the "User's Guide VE"

ephemeral Port

When the range of ephemeral port numbers on Windows is changed, the ephemeral port and the port to use conflict. In that case, select a port number which is not included in the range of the ephemeral port numbers.

The range of ephemeral port numbers is as below.

For Windows 2003
1025 to 5000

For Windows 2008 or later
49152 to 65535

2.1.1.5 Configuration Parameter Checks

Check configuration parameters following the procedure below:

Confirm that a single folder path is set for the TEMP environment variable.

Information

If the TEMP environment variable is not configured or if multiple folder paths are set for the TEMP environment variable, the Environment setup conditions check tool outputs the following message and cancels the process.

The check tool cannot be processed because the temporary folder %temp% cannot be accessed. Please set the TEMP environment variable of current user correctly, then rerun the check tool.
press enter key to exit...

If the above message is output, set a single folder path for the TEMP environment variable, then execute the Environment setup conditions check tool again.

Start the installer.
The installer is automatically displayed when the first DVD-ROM is set in the DVD drive. If it is not displayed, execute "RcSetup.exe" to start the installer.
Select "Tool" on the window displayed, and then click "Environment setup conditions check tool". Configuration parameter checking will start.
For the check items with the edition name displayed in the check results, check only the items corresponding to the edition to be installed.
When configuration parameter checking is completed, the check results will be saved in the following location.
%temp%\ror_precheckresult-YYYY-MM-DD-hhmmss.txt
The check results are output to Notepad at the same time.
The following items are displayed as the items to be checked:
- Required Software (LAN Manager module)
- Required Software (Windows PowerShell)
- Required Software (ETERNUS SF Storage Cruiser)
- Disk Space (Express/Virtual Edition)
- Disk Space (Cloud Edition)
- Memory Size (Express/Virtual Edition)
- Memory Size (Cloud Edition)
- cpu
- SNMP Service
- Port Status (Express/Virtual Edition)
- Port Status (Cloud Edition)
Confirm that "Warning" or "NG" is not included in the check results. If there are check items that were determined as "Warning" or "NG", resolve the cause of the problem based on the output message. For details of the corrective actions, refer to "2.1.1.1 Preparations" and "2.4 Software Environment" and "2.5 Hardware Environment" in the "Design Guide VE".

2.1.1.6 Installation

The procedure for manager installation is given below.

Before installation, check if "2.1.1.1 Preparations" have been performed.

Nullifying Firewall Settings for Ports to be used by Resource Orchestrator

When installing Resource Orchestrator on systems with active firewalls, in order to enable correct communication between the manager, agents, and clients, disable the firewall settings for the port numbers to be used for communication.

For the port numbers used by Resource Orchestrator and required software, refer to "Appendix A Port List" in the "Design Guide VE".

However, when port numbers have been changed by editing the services file during installation of Resource Orchestrator, replace the default port numbers listed in "Appendix A Port List" in the "Design Guide VE" with the port numbers changed to during installation.

Installation

The procedure for manager installation is given below.

Log on as the administrator.
Log on to the system on which the manager is to be installed.
Log on using the Administrator account of the local computer.
Start the installer.
The installer is automatically displayed when the first DVD-ROM is set in the DVD drive. If it is not displayed, execute "RcSetup.exe" to start the installer.
Click [Manager(Virtual Edition) installation].
Following the installation wizard, enter the parameters prepared and confirmed in "Parameters Used for Installation" properly.

Note

In the event of installation failure, restart and then log in as the user that performed the installation, and perform uninstallation following the uninstallation procedure.
After that, remove the cause of the failure referring to the meaning of the output message and the suggested corrective actions, and then perform installation again.
If there are internal inconsistencies detected during installation, the messages "The problem occurred while installing it" or "Native Installer Failure" will be displayed and installation will fail. In this case, uninstall the manager and reinstall it. If the problem persists, please contact Fujitsu technical staff.