Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home

Rapid Deployment Pack

Knowledge base
» 

Server management

» Rapid Deployment Pack
Resources
» Evaluation license
» Training
» Altiris
» Unified Infrastructure Management
» HP Systems Insight Manager
» HP BladeSystem Management
» Integrity Essentials
» ProLiant Essentials
» Storage Essentials
Related products
» ProLiant servers
» ProLiant clusters
» ProLiant Essentials services
» ProLiant services
» New products
» Retired products
» ProLiant IT consolidation
» Special promotions
» Site map
announcing new products
What's new in IT? HP Virtual IT Center
IDC Business Value of Virtualization
 
Content starts here
Job Fails With Error 116 "Unable to boot to automation."

Article: 52

Applies to: Release 1.50 or greater

This problem occurs when a scheduled job contains a task that must run in automation. To execute this task, the Altiris Deployment Agent on the target forces a reboot of the production operating system to PXE. If the PXE boot fails, the target server boots back to the production operating system. The Altiris Deployment Agent then determines that an automation-based task is scheduled and attempts to boot PXE again. This will repeat two or three times before the job fails with the message, "Unable to boot to OS automation" where OS is the automation operating system.

The possible causes are:

HP Management software is not installed.
If the target server does not display the PXE post message and it supports the one-time boot to PXE, the HP System Management component for ProLiant servers or HP Management Base component for Integrity servers is probably not installed. This component installs a driver or utility that is used by the Altiris Deployment Agent to force a reboot to PXE when running a production operating system. Install the ProLiant Support Pack or Integrity Support Pack.
For certain targets, PXE is not first in the boot order.
If the target server does not display the PXE post message, and does not support the one-time boot to PXE or is a virtual machine, PXE, the Network Boot, or Core LAN is probably not first in the boot order. Place PXE, the Network Boot, or Core LAN first in the BIOS or EFI boot order, and rerun the job. Refer to Knowledge Base article Do I Need To Set PXE First In The Boot Order? (Article 31) for information regarding which platforms require a change in the BIOS boot order.
There is a PXE error.
If the target server displays the PXE post message, watch for error messages from the PXE client that indicate the source of the problem. Refer to Knowledge Base article What Are The PXE Error Codes? (Article 138) for the message that is displayed.

NOTE: A ProLiant target server may attempt to PXE boot several times, failing with an error each time, before booting back to the production operating system.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.