This section explains the tasks that must be performed prior to installation.
Reading the software ReadMe files
The software ReadMe files provide basic notes about Systemwalker Operation Manager. Be sure to read these files before installation.
Backing up existing environments
Make a backup copy of the existing environments in case of installation failure although they are transitioned automatically during upgrading or reinstallation.
For the detailed backup procedure, see the following
Checking the system installation environment
Confirm the following items regarding the system environment at the installation destination.
Server service
When you install Systemwalker Operation Manager, the Server service must be running beforehand. Ensure that the Server service has already started.
Windows Modules Installer service
When installing Systemwalker Operation Manager, confirm that one of the following options is set for Startup type in Windows Modules Installer Properties beforehand.
Manual
Automatic
Automatic (Delayed Start)
Use of DHCP
If you have used the DHCP server to dynamically assign an IP address to the server machine, you cannot start Systemwalker Operation Manager's server functions. Ensure that the DHCP is not used. However, you can use the Systemwalker Operation Manager's client functions even in the environment where the DHCP server is used.
Primary domain controller
When installing on a backup domain controller, confirm that the primary domain controller is running.
Network drive connection
Ensure that the destination drive or directory is NOT connected to the network as a separate drive within the same system. You must disconnect the drive or directory before installation. If connected, you may fail to install the server functions.
Active programs
Before installing Systemwalker, shut down all of currently active applications. Also, shut down the following programs before installation.
Resident programs (permanently running programs) including virus detection programs
Screen savers
Deciding the installation method
You can select one of the following methods to install Systemwalker Operation Manager in the system. Decide in which method you will install your Systemwalker Operation Manager.
Local installation
You can directly install Systemwalker on a PC with a drive by using the product media.
Network installation
You can install Systemwalker on a network-connected PC if the drive has been set as the shared disk.
Preventing depletion of the desktop heap
To prevent depletion of the desktop heap when using Windows Server 2008 or later, modify the registry and expand the size of the desktop heap.
Change the third parameter of the registry indicated below (SharedSection) to "3072".
If you want to raise Job Multiplexity from the default, we recommend 15360. After setting the Job Multiplexity, verify that the Job Multiplexity setting works correctly, and then adjust it as necessary.
Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems
Name: Windows
Value: Third parameter of SharedSection
Before (example in Windows Server 2012)
SharedSection=1024,20480,768 |
After (example in Windows Server 2012)
SharedSection=1024,20480,3072 (*1) |
*1: If the value of the third parameter of SharedSection is greater than 3072, do not change it.
Configuring firewall settings
In the firewall settings, allow connection with the port number/protocol to be used by Systemwalker Operation Manager. Refer to the operating system manuals for information on how to allow the required connection (port) for the firewall function. Refer to "C.1 Listing of Port Numbers" for information on the ports that Systemwalker Operation Manager uses.
Note
Using the mjrmtjob command
It is necessary to set the port numbers for the firewall to execute a job on a remote machine using the mjrmtjob command and to use the remote machine environment where the firewall function is used. On the remote machine, allow the port numbers listed in "Remote machine (port numbers that should accept external server access)".
You need a remote machine license to use the mjrmtjob command to execute jobs on a remote machine.
Using the jobschmsgevent command
If you use the jobschmsgevent command to cause a message event on a remote machine, and if the remote machine is using the firewall function, you must also set a port number for the firewall. In this case, the remote machine must allow the port number described in "Remote machine (port numbers that should accept external server access)".
