Ghost Solution Suite

Hello, 

I've been working on getting several machines to boot up through the automation partition. The Automation partition installer job in the deployment server says it installs successfully. But,  We're getting the "Windows failed to start. A recent hardware or software change might be the cause." error.

I've followed this article with some success:

https://support.symantec.com/en_US/article.TECH232932.html

While modifying the bcd with bcdedit to [c:] will solve the issue temporarily, ghost changes [c:] back to [boot] every time we schedule a job such as a re-image so we're back to square one. 

This has been happening on 3 different computers - All different models. The most recent one I have tried is a Windows 7 HP5700 machine. I am wondering if there is a problem with the bcd entry ghost solution suite is creating. 

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume3
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {da0c5b79-b1f8-11df-936d-ba99eaae7eaf}
displayorder            {current}
                        {e217309d-dead-beef-a315-001372be0d01}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {26803088-cfde-11df-b91b-000ffed6a70d}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \windows
resumeobject            {da0c5b79-b1f8-11df-936d-ba99eaae7eaf}
nx                      OptIn

Windows Boot Loader
-------------------
identifier              {e217309d-dead-beef-a315-001372be0d01}
device                  ramdisk=[boot]\boot\altiris\iso\sources\boot.wim,{e217309d-dead-beef-a315-001372be0d02}
path                    \windows\system32\boot\winload.exe
description             Symantec Deployment Solution Preboot Environment
osdevice                ramdisk=[boot]\boot\altiris\iso\sources\boot.wim,{e217309d-dead-beef-a315-001372be0d02}
systemroot              \windows
detecthal               Yes
winpe                   Yes
quietboot               Yes
bootlog                 Yes

Any help would be appreciated! 

Thanks,

Chris 

I would not use Automation Partitons. If you upgrade to the latest HotFix you can now use Automation Folders. I think this was first available with Ghost 3 - Hot Fix 3. We have found much better results using the automation folder.

Attached is a file with more details.

Attachment(s)

Ghost 3.0 HF3 Automation Folders_0.pdf   834 KB 1 version

Thank you for your help! Since your post, I've tried using both the automation folder and the automation partition with the same result. Upon booting up, Windows Boot Manager - "The boot selection failed because a required device is inaccessible." 

We're currently on HF5 of Ghost solution Suite 3.0. Any other ideas as to what could be causing this?

Thanks,

Chris 

Tea7ime, I am getting the same errors.  I have the following boxes checked in the deployment image task.  When I don't have those boxes checked to automatically run the configuration task, my image is fine and Windows loads.

Scratch that...I tried again today with and without configuration checked and it fails inconsistently.  I'm leaning towards a DAgent issue, because the machine loads into automation every time the machine is restarted.

Uninstall the Automation Partition...that solved it for me!