Use the installation information file you have created for Silent Installation. The following explains how to perform the Silent Installation using this file. Install Systemwalker appropriate to the user environment.
In additions, after finishing to install, to operate Systemwalker Operation Manager, first, you must input the license key [Linux version/Solaris 64-bit version]. For the detail of inputting license key, refer to the"1.3.5.1 Registering a license key".
Installation in the UNIX system
The following explains how to install Systemwalker Operation Manager in the UNIX system.
Log in as the superuser.
Copy the created installation information file to the PC where you want to install Systemwalker.
Mount the installation product media.
Insert the installation product media into its drive. If the volume management daemon is not active, mount the drive. Check the correct drive device name as it may vary depending on the environment you use.
Issue the Silent Installation command as follows.
Solaris
# <mount point>/Solaris/tool_unx/sscmd/swsilent.sh -i /work/swinst.ini -y |
Linux
# <mount point>/Linux/tool_unx/sscmd/swsilent.sh -i /work/swinst.ini -y |
swinst.ini: Instillation information file
For more information of the swsilent.sh command, refer to the Systemwalker Operation Manager Reference Guide.
When installing Systemwalker in Windows via network connection
The following explains the Silent Installation procedure via the network connection.
At the PC you use for Systemwalker installation
Mount the installation product media.
In Explorer, set the drive with the product media as a shared drive. (network drive A).
Copy the created installation information file to any location on the PC which you use for installation, and set the sharing at the destination. (network drive B)
At the PC where you install Systemwalker
Log on as a user belonging to the local Administrators group.
Using either of the following methods, connect network drive A and network drive B of the "PC you use for Systemwalker installation" to the network.
Run the "net use" command from a command prompt with Administrator privileges to map a network drive.
Use Explorer to map a network drive.
Issue the Silent Installation command as follows.
Windows x86
<network drive A> \MAIN\tool\sscmd\swsilent -i <network drive B> \<file name> -y (Note) |
Windows x64
For server:
<network drive A>:\MAIN\tool\sscmd\swsilent -i <network drive B>\<file name> -y (*1) |
For client:
<network drive A>\Client\tool\sscmd\swsilent -i <network drive B>\<file name> -y (*1) |
File name: Installation information file
*1: A UNC path cannot be specified for <network drive B>.
For more information on the swsilent command, refer to the Systemwalker Operation Manager Reference Guide.
When installing Systemwalker in Windows during logon
The following explains the installation procedure by using the logon script under the domain environment.
At the PC you use for Systemwalker installation
The computer that is used for the installation work means a domain controller.
Specify a share name and installation information file using the full path name and alphanumeric characters.
Mount the installation product media.
In Explorer, set the drive with the product media as a shared drive.
Set any name as the Share Name.
Copy the created installation information file to any location of the computer used for the installation work. Set the sharing of copied installation information file by using the Explorer. For the shared name, you can specify any name.
Modify the logon script template and copy it to the script under the logon account.
The logon script template is stored in the following directory:
Windows x86
<CD-ROM drive>\MAIN\tool\sscmd\logonscr_japan.bat |
Windows x64
For server:
<drive>\MAIN\tool\sscmd\logonscr_japan.bat |
For client:
<drive>\Client\tool\sscmd\logonscr_japan.bat |
For the method of setting the logon script, see the manual of your operating system.
At the PC where you install Systemwalker
The installation target computers should belong to the domain managed by the above mentioned computer used for the installation work (domain controller).
Log on the domain of PDC (the PC where you have created the installation information file) as the user belonging to the local Administrators group.
The preset logon script will be executed and the installation will start.
Note
When Systemwalker Operation Manager is installed on a Windows system, under certain conditions, it will start automatically upon the completion of the installation process.
If any of the following conditions are met, Systemwalker Operation Manager will not be started automatically when the installation completes:
If Systemwalker Centric Manager has been installed
If the installation is not a new installation
If the Microsoft Visual C++ 2005 Redistributable package has been installed, the existing version is earlier than the version that is bundled with the product, and the conditions that require a restart are met
Note
Performing silent installation on Windows Server 2012
When performing a silent installation on Windows Server 2012, the following error message may appear in the event log.
In this case, no action is required as the installation itself has completed successfully.
Log Name: Application |
