2.Install the patch non-interactively:

#swinstall -x autoreboot=true -x match_client=true \ -s /PHCO_34240.depot

This assumes you have already met the dependencies of PHCO_34240. These instructions can also be found in the PHCO_34240.text file.

For more information, see the Patch Management User Guide for HP-UX 11.x Systems and the HP-UX Software Assistant Administration Guide, available at http://www.hp.com/go/swa-docs.

Installing optional software

Load any optional HP and third-party software you want to make available to all clients. Keep in mind that anything you install is distributed to all clients installed using the golden image. Keep in mind any licensing restrictions.

To install HP software from media or a network depot, you normally use Software Distributor (SD) tools. Third-party software installation varies depending on the vendor.

IMPORTANT: Inclusion of multiple versions of Veritas Volume Manager from Symantec (VxVM) in the same installation depot, or in separate depots that are used together in a single cold-installation session, is not supported. Doing so renders it unusable and generates errors when attempting to use the installation depot, or in the case of non-SD depots during the reboot attempt. For more information, see “Considerations when using Veritas Volume Manager from Symantec” (page 193).

Customizing the system

Perform any customizations you want to distribute to all clients. These might include customized CDE login dialog boxes, base /etc/passwd files, manpages, and corporate-wide default DNS and NIS setup. Do not include system, workgroup, or site-specific customizations such as gateways, user accounts, and machine-specific networking; these are taken care of by Ignite-UX later.

Creating the golden archive

Use the next steps to create the golden archive from the golden system, and configure the Ignite-UX server to use it. The make_sys_image command creates the golden archive. For more information, see make_sys_image(1M).

IMPORTANT: Do not use the golden system while make_sys_image is running; the make_sys_image command modifies files with host and networking information.

1.Use ftp or a similar command to copy the /opt/ignite/data/scripts/ make_sys_image script from the Ignite server to /tmp on the golden system.

NOTE: You don't have to install the full version of Ignite on the golden system to create a golden image; only the make_sys_image script is necessary.

2.Set the permissions of /tmp/make_sys_image so you can execute it.

# chmod +x /tmp/make_sys_image

NOTE: By default, make_sys_image stores the archive in the /var/tmp directory. You can have make_sys_image save the archive to a remote server. Either method requires sufficient disk space to hold the archive. The amount of disk space is approximately one half the amount of data contained on your system, assuming a 50 percent compression ratio from gzip.

3.On the Ignite-UX server, create a directory to store the golden archive:

# mkdir -p /var/opt/ignite/archives/Rel_B.11.11

Creating a golden image 153