ServerConductor/Blade Server Manager Description and Reference
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
- If you restart the manager service while the machine is running, you must log on again to use the console. This is because the same status as at the time of disconnection occurs due to an idle-session timeout. This event occurs even when the idle-session timeout is set to 0. In such a case, log on again as instructed in the displayed message. If possible, try not to restart the machine on which the manager service is installed.
- When the console service's window is inactive, an attempt to display error and information messages sends control to the background of other application windows.
- Depending on the status of the communication line, operation from the management console might be executed normally even if a command-sending timeout error has occurred.
Example:
Power-off operation was executed on a managed server, but a command timeout error occurred. The server's power has actually been turned off.
- ServerConductor does not support the Dynamic Host Configuration Protocol (DHCP). You must not set up DHCP on a machine where ServerConductor is installed.
- Do not change the access permissions and service accounts in the files provided by ServerConductor. Changes to this information might have adverse effects on ServerConductor operations.
All Rights Reserved. Copyright (C) 2006, Hitachi, Ltd.