denrus0

I recently downloaded a trial version of Deployment Solution. I installed it on a win2003 server. I used ‘boot disk creator” . I installed the Vista winPE “pre-boot “ operating system and created an ‘automation boot disk’ iso file. I then burned it onto a cdrom.

If I boot my 1 year old ACER laptop with the cd, everything works fine and it boots as it should. If I boot three different minitower computers that are 1-2 years old (pent 4 or better), I get the following message in DOS:


-----------------------------------------------------------------------------------------------
Windows Boot Manager

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:

1) Insert your windows installation disc and restart your computer
2) Choose your language settings & then click next
3) Click “repair your computer”

If you do not have this disc, contact your system administrator for assistance.


File: \windows\system32\winload.exe

Status: 0xc000000f

Info: the selected entry could not be loaded because the application is missing or corrupt


--------------------------------------------------------------------------

Can someone help me with this?

Thanks

wmillen

I am having a similar issue. I just installed WinPE 2.1 on my deployment server and am trying to boot a pc to it via PXE but I get the following:

Windows Boot Manager (Server IP: xxx.xxx.xxx.xxx)

Windows Failed to start. A recent hardware or software change might be the cause. To fix the problem:

1. Insert your WIndows installation disc and restart your computer.
2. Choose your language settings, and then click "Next."
3. Click "Repair you computer."

If you do not have this disc, contact your system administrator or computer manufacturer for assistance.

File: \Boot\BCD

Status: 0xc0000001

Info: An error occured while attempting to read the boot configuration data.



I believe that I've followed all of the instructions correctly for setting this up as well. Seems like a similar, if not same problem that denrus0 is having.

mbstlcop

wmillen,

I am having the exact same issue as you. Since introducing DS6.9 and Winpe2.1, any attempt to create a PXE image with winpe2.1 fails to boot immediately with the exact message you are receiving.

Did you ever this this resolved? If so, what did you find to be the problem?

Anyone else have any ideas? They'd be greatly appreciated!

franz217

This is also happening for me, but so far only on HP DC5700s. At first I thought it was network driver related. All of the DC5700s here have the Broadcom NetXtreme Gigabit adapters so I loaded the latest driver from Broadcom. No luck, same failure.

We are running DS6.9 with SP1. I applied the hotfix to address the issue adding drivers to the PXE Boot Disk. Still have the same problem. It may not be a broadcom driver issue at all.

The task we are running is a scripted OS install. The step to push the fat32 image to the disk runs in automation then it reboots to begin the scripted OS install... that's where it fails.

Let's try to establish some common threads here:
What hardware are you exhibiting this problem on?
What jobs are you running in automation?

Predhead

I am getting the same problem after upgrading from DS 6.9 to DS 6.9 SP1. It happens so far on three different models. E6400, Optiplex 755 and 520. I have been on the phone with support for 1 1/2 days and still no fix. Has anyone else found a fix???

endo

I am reporting this to support right now. Hopefully someone knows what the problem is. If noone has posted an answer until I am finished with support. I'll make sure I do.

bfusco1

I am having the same issue after the SP1 upgrade. I made a separate thread (BCD error with WinPE in DS 6.9 SP1) before I found this one about the same issue. Please post back here if you find a solution.

endo

Hi. We are awaiting response from Altiris support. They have managed to recreate the problem, so I guess there is a good chance they will find a remedy for this problem.

It seem like it does not have anything to do with old or new computers........

In the meantime have a cup of coffee :-)

bfusco1

I sure hope they can fix it...

Yeah, I'm really not sure about the old/new computers thing. I just know that it works on a GX270 2.8GHz with IDE disk, but nothing newer than that. Even a GX270 3.2GHz with a SATA disk will fail.

plit

Just double check that if you are using Serial or any other Primary Lookup key (as single lookupkey) in Global DS options, then select Serial + MAC (to have 2 primary lookup keys).

Hope this helps.

endo

Hi. As plit says here this was the solution for us and what got from Altiris Support. Just tested it yesterday.

It seems like if you are upgrading from 6.8 or earlier this setting might not be set.

Another thing is that many of us that have been using DS for a while has set serialnumber as the only primary lookupkey because that is what been working in the past.

mbstlcop

Well, that did get me past this problem but it brought on another. That is outside the scope of this thread though.

How does using multiple lookup keys affect things in DS?

If a system's MAC address changes but Serial stays the same will DS still recognize it as the same system?

When staging accounts in DS, can I still just use Serial numbers and not worry about needing both Serials AND MAC addresses?

bfusco1

Works for me too. I hope that Altiris can come up with a better solution than that. Using a single lookup key has always worked in the past.

This is a concern for me too. I've found in the past that it only works if you have the primary key set to serial number ONLY. If you use the composite of S/N and MAC it does not work if you only provide the S/N.

bfusco1

Does anyone know if there has been any response on this issue from Altiris? I'd like to go back to using S/N as the sole primary lookup key.