For example, running setup. Customization files provide a way to customize the exact software components to install. With the customization file, users can selectively install software components for different systems using the same unattended installation package.
For example, you can choose to install Server Administrator, but not Remote Access Service on a specific group of servers, and choose to install Server Administrator, but not Storage Management Service, on another group of servers. The customization file is formatted as a simple text file with a.
For example:. A designation of yes indicates that the component is installed. A designation of no indicates that the component is not installed. Table shows the component IDs for each software component. The component ID is a 2- to 5-character designation. The return codes are described in Table Setup did not run because one or more of the options were not input correctly.
The unattended installation log files capture the installation status of each software component and the result of each unattended installation dependency check. For more information about log files generated by the dependency check, see " Dependency Check. Two log files are generated in a temp folder during an unattended installation, ominstal. Each log provides the installation status of each component, the host system name, and the start and end time of the installation.
On a large-scale, unattended installation deployment of hundreds or thousands of servers, users can save the unattended installation log file for each server and easily isolate an installation problem on one or more servers with the host information in the log file.
The omstatus. You can use this information to write automatic script files to query the installation status and take remedy actions as needed.
See Figure There is one line per software component. A value of "0" indicates that the installation of the component succeeded, a value of "-1" indicates that installation of the component failed, and a value of "1" indicates that the component did not install because a dependency was not met.
See " Dependency Check " for information about identifying installation dependencies. The software component ID is the same 2- to 5-character designation described in the " Customization Files " section. Figure Example of a Short omstatus. The ominstal. Example of a Full Text ominstal.
See Figure for an example of a log file. A value of "0" indicates that the installation is ready to proceed, a value of "1" indicates that one or more components has a warning, and a value of "2" indicates that one or more components has a dependency failure.
The software component ID is the same 2- to 5- character designation described in the " Customization Files " section.
See the " Log Files " for more information. The format is very similar to the. Table shows the dependency check command line settings available for unattended installation. Dependency Check Command Line Settings. Specifies the custom install directory. Specifies a nondefault filename for the short format dependency log file. The full path including the name of the file must be specified. If the showstatus option is set to yes then the dependency check status will be displayed in a small console on the desktop.
If the showstatus option is set to no or the showstatus option is not used, the status will not be displayed during the dependency check. Runs a dependency check on the components specified in the. For more information about the format of the. Dependency Check Return Codes. You can uninstall Server Administrator managed system software components by using the Systems Management CD or your operating system.
Additionally, you can perform an unattended uninstallation on multiple systems simultaneously. The Uninstall Selection screen appears. A check in the check box indicates that the software component is selected for uninstallation.
As a default, all installed managed system software components are selected. The Uninstall Summary screen appears, listing all of the managed system software services you selected for uninstallation. The Uninstall screen appears. Messages display, stating which components are being uninstalled. When the selected components are uninstalled, the setup program asks if you want to reboot your system. You must reboot your system to complete the uninstallation process.
A check in the check box indicates that the component is selected to be uninstalled. As a default, all installed components are selected. The Uninstall Summary screen appears, listing all the managed system software components you selected to uninstall.
A screen appears on which messages are displayed, stating which components are being uninstalled. When the selected components are uninstalled, a dialog box asks if you want to reboot your system.
The Systems Management CD features an unattended uninstallation procedure. Unattended uninstallation allows you to uninstall Server Administrator from multiple systems simultaneously. The unattended uninstallation package is distributed to the remote systems using a software distribution tool from an ISV.
When the package is distributed, the uninstallation script executes to uninstall the software. The Systems Management CD is preconfigured to act as the unattended uninstallation package. To distribute the package to one or more systems, perform the following steps:. Table shows the unattended uninstall command line settings available for unattended un installation. Unattended Uninstall Command Line Settings. If the showstatus option is set to yes then the unattended uninstallation status will be displayed in a small console on the desktop.
If the showstatus option is set to no or the showstatus option is not used, the status will not be displayed during the unattended uninstallation. This section explains how to install, upgrade, and uninstall Server Administrator on an ix86 system that is running a supported Red Hat Linux operating system. Additionally, Server Administrator includes Dynamic Kernel Support, a feature that automatically builds a device driver for a running kernel if Server Administrator detects that none of its prebuilt device drivers support that kernel.
Server Administrator provides prebuilt device drivers for the precompiled kernels listed in the Server Administrator readme file on the Systems Management CD. If the running kernel is not one of the precompiled kernels listed in the readme file, or if the running kernel is reconfigured and recompiled in such a way that none of the prebuilt Server Administrator device drivers support the recompiled kernel, Server Administrator must use its Dynamic Kernel Support feature to support the running kernel.
For example, if you see either of the following messages during Server Administrator installation or startup, Server Administrator attempted to use its Dynamic Kernel Support feature, but was unable to use the feature because certain prerequisites were not met:.
Server Administrator is unable to build a device driver for the running kernel because the needed kernel source files are not installed. Building device driver for running kernel For Server Administrator to use its Dynamic Kernel Support feature, the following Dynamic Kernel Support prerequisites must be met before installing or restarting Server Administrator:.
When these prerequisites have been met, Server Administrator's Dynamic Kernel Support automatically builds a device driver when needed during Server Administrator installation or startup. To install Server Administrator on a system running a kernel that is not supported by a prebuilt device driver, perform the following steps:. During installation, Server Administrator builds a device driver for the kernel running on the system. To enable Server Administrator to support a kernel that is not supported by a prebuilt device driver and is loaded after Server Administrator has been installed, perform the following steps:.
Server Administrator builds a device driver for the kernel running on the system the first time that Server Administrator starts after the kernel is loaded. By default, Server Administrator starts during system startup.
This action allows Server Administrator to use its Dynamic Kernel Support feature on multiple systems without having to install the kernel source on every system. For example: System A is running a kernel that is not supported by one of the Server Administrator prebuilt device drivers.
System B is running the same kernel. Perform the following steps to build a device driver on system A and copy the device driver to system B for use by Server Administrator:. This section explains how to install and upgrade Server Administrator. When you load the Systems Management CD in your system's CD drive, the setup program uses your system's peripheral controller interconnect PCI bus to search for installed hardware such as controller cards.
When a user selects the Express Setup or Express Upgrade option, the user lets the setup program install or upgrade all the managed system software components that are appropriate for the hardware configuration of your particular system. For more information on how to perform an express setup or express upgrade, see the Software Quick Installation Guide.
When a user selects the Custom Setup or Custom Upgrade option, the user can deselect one or more components that the setup program has identified as appropriate for your system. During an express setup or express upgrade, you cannot add to the list of components to install because all the components that are appropriate for the hardware configuration are preselected.
After the CD mounts, the File Manager should automatically start and display the contents of the root directory of the CD. As a default, all available components are selected. The Settings button indicates that you can install and configure the component. The Installation Summary screen appears, listing all of the managed system software services that you selected for installation.
Messages are displayed, stating which components are being installed. When the selected components are installed, the Installation Complete screen appears. A check in the check box indicates that the component is selected for upgrade. The Settings button indicates that you can upgrade and configure the component. The Installation Summary screen appears, listing all the managed system software services you selected for upgrade. This section describes how to perform an Express installation or upgrade of Server Administrator from the Red Hat Linux command line.
Use the following procedure to install Server Administrator for the first time or to upgrade to a more recent version of Server Administrator. The -license setting confirms that you accept the software license agreement. The installation script starts Server Administrator when the installation is complete. The unattended installation option also provides several " Unattended Installation Features " that allow users to configure, verify, and view information about unattended installations.
The unattended installation package is distributed to the remote systems using a software distribution tool from an ISV. The start. You can make the Systems Management CD image available to the remote system by distributing the entire contents of the CD.
To create an unattended installation package, perform the following steps:. The custom unattended installation package is located in the directory you created in the preceding step 1.
This directory contains all of the managed system software components to distribute, along with all the necessary unattended installation program files. Table shows the optional command line settings and subcommands available for unattended installation. Type the settings on the command line after start. Subcommands must follow a setting. Runs dependency check.
See " Dependency Check. If the - force option is not used, the system will not install software components that have warnings. Accepts the software license agreement for using the silent unattended installation program. If the path or the filename contains any spaces then the location must be enclosed in double quotes. For example, running start. For example, you can choose to install Server Administrator, but not the Remote Access Service, on a specific group of servers, and choose to install Server Administrator, but not the Diagnostic Service, on another group of servers.
The component ID is a 2- to 5- character designation. One line per software component is available. The software component ID is the same 2- to 5-character designation described in " Customization Files. A value of "0" indicates that the installation is ready to proceed, a value of "1" indicates that one or more components has a dependency warning, and a value of "2" indicates that one or more components has a dependency error.
See " Log Files " for more information. Type the optional settings on the command line after start. The Systems Management CD has been preconfigured to act as the unattended uninstallation package. The uninstall. The Systems Management User Security utility displays the following instructions:. Version x.
Do you want to change the default security settings for Server Administrator? This section explains how to install, upgrade, and uninstall Server Administrator on a system that is running a supported Novell NetWare operating system. There are two installation options:. A default message appears, stating that the product is to be installed from drive A. Indicate which file groups you want installed.
The installation of Server Administrator and the components you selected begins. Status messages appear. Type the new password, and then type the password again to confirm. The installation of Server Administrator and the components you selected continues. When the installation is complete, a dialog box appears stating that the installation is complete. Use the following procedure to silently install Server Administrator for the first time or to upgrade to a more recent version of Server Administrator.
The installation script installs all necessary files to the managed system. If you are upgrading to a more recent version of Server Administrator, the installation script will uninstall previously installed versions before installing the current version of Server Administrator. At the NetWare command line console, type omunins. The uninstallation script uninstalls all Server Administrator files from the managed system.
NOTE: Upgrading to the most recent version of Server Administrator does not require that you uninstall any previously installed software components. The setup program on the Systems Management CD automatically uninstalls, and then upgrades the managed system software components that are appropriate for your particular system's hardware configuration.
NOTE: For information about installing a supported system management protocol standard on your managed system, see your operating system documentation. Supported Microsoft Windows operating systems.
Available from the operating system installation media. Supported Red Hat Linux operating systems. You must install the SNMP package provided with the operating system. It is not OpenManage anymore for newer servers although you can install this. They will push you to install SupportAssist.
Thanks for posting this three years ago. Wouldn't have been a disaster if I'd lost the array as this host doesn't run any VM's it just holds Veeam Replicas , but I was glad to not have to build it again. OMSA fills that gap for me though, so I'm quite happy. Not surprisingly, they don't list Server or Hyper V under the OS choices , but it installed just fine.
I recently did this on a Hyper-V server myself. It is very helpful compared to iDRAC 6. I dunno. I kind of prefer the old, clunky interfaces that require a Java install from to work Airgapped, of course. I can get to it's console without Java, so I'm happy. I seldom need remote console access anymore since my office is 30 feet from the server, but it's nice to have the option if I'm out of the office I loaded the OS remotely on it from 30 feet away just because.
Of course, back then, it was Java all the way. Always fun when you run into an iDRAC in the wild whose password is still "calvin". That's why I always change it to "hobbes"!
Register Login. Reply Reply as topic. This topic has been deleted. Only users with topic management privileges can see it. So I decided to make these instructions. Click next Accept the license and click next again. Thanks a lot for the info. Yes, Google gives you that information. But did you just follow Google or try things? Why do all of that when there is no need? That is why it is not in my instructions above. I also ran runprereqchecks. Mike-Davis said: JaredBusch I just did it this morning on a box.
The whole reason for SysWOW64 is to enable 32 bit support for things. Just installed this on the Hyper-V Server instance I setup a couple days ago.
This was useful again today! Anyone test on yet?? I should be able to tomorrow or wednesday. So I dunno how those compare. They are much better and do have Storage Information. Idrac 9 is all HTML5 now. C 1 Reply Last reply Reply Quote 1. First post.
0コメント