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
Target Server Starts To Boot WinPE And Then Unexpectedly Reboots

Article: 177

Applies to: Releases 3.00 through 3.70

WinPE is failing to boot because one of the system filenames became truncated. This is the result of using an ISO utility to extract, burn or mount the RDP ISO image that is not ISO9660:1999 compliant.

To resolve this issue, either:

On the Deployment Server, in the folder .\bootwiz\platforms\Winpe\x86\BASE\I386\WinSxS\manifests, rename x86_microsoft.windows.isolationautomation.proxystub_6595b64144ccf1df_1.0.3790.1830_x-ww_148995c5.manife to x86_microsoft.windows.isolationautomation.proxystub_6595b64144ccf1df_1.0.3790.1830_x-ww_148995c5.manifest and then rebuild your WinPE images.
Use an ISO9660:1999 compliant utility to extract, burn or mount the RDP ISO image and then restart the installation.

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