Deployment Solution

After i roll out a Windows Xp image via Altiris, after the imaging finish it will not reboot. It says it will reboot, but al i can see is a black screen.

The pc is still powered on, but there is no activity whatsoever. Ctrl+Alt+Del will not help. Only unplugging the power cable for a few seconds and plugging it back in again brings the system back to life.

What is wrong here?

Sounds like an incorrect HAL problem.

any solution

The solution has already been provided. You aren't using the right HAL. Either inject the right one or build a new image. It all depends on what HAL types you intend on supporting.

When you say comes "back to life" do you mean it works like you expect then? If that is the case I guess make sure you are using the cables that come with the system. I have seen HP monitors have a similar problem because of the power cable.

Yes all you have to do after imaging process done unplug the power cable and plug it back and it perfectly working. So I don't know what the HAL have to do with this!

I apologize, I misunderstood the original problem. I took it as, the machine is stuck at a black screen until you unplug it, I assumed that when you plugged it back in it would repeat the scenario after the POST.

You might check your power management settings in the BIOS. In some manner, it almost seems as if the BIOS is not processing the power down or reboot from your automation client properly.

this are the step and test I make
- changing the power cord
- changing the power circuit
- using UPS to make sure that non electric problem
- changing the network Switch
- checking the bios power manager setting

And buy the way if you unplug and plug the PC before sending the image it will work find. So the first time you send a image after unplugging and plugging the PC it will work perfectly. Any other solution?

Is this happening on multiple machines, or just this one particular one? If it is just this one machine, it's possible there could be some faulty hardware (i.e. power supply). It sounds like you have a pretty odd problem though.

it all DC5850 that we have I just update the Bios and having the same problem.
we have more then 50 new one

That's really odd. Have you checked with HP to see if they have had any other complaints from other customers on that same issue?

it is my next step i will let you know.

but found this on HP web site

http://forums11.itrc.hp.com/se...er.do?threadId=1295060

the problem is one you chose a PXE boot disk the PC so it most be a PXE problem i will contact HP for that

Hi Khal,

I had this problem back in October last year. I was using DOS for PXE. This is the solution I came up with for a temp solution (Article ID: 44131 at Altiris Knowledge base). But I found it necessary to switch to WinPE and I have no problems at all.

1)      Make sure they have the latest BIOS in the dc5850
Yes IT is the last version

2)      Try the power control (power off , power on, reboot) from the DS console and see if those execute correctly on the dc5850
Yes It is working

3)      Can they execute a job , in dos, on the dc5850?
Yes it give the same problem

a.       For instance they could create a dos job, that does a DIR

b.      This job should reboot the client to dos, then execute the dir command, then reboot

c.       This is a test to see if the dc5850 executes the reboot command successfully

4)      They should call symantec support.  Again it is not because the software doesn’t execute on the hw that the hw is to blame.  The sw has to support the HW.  We are not aware of any other issue like this…
It is know on the altiris Forums

Hi there

I have the same problem.  When I am trying to create an image of the workstation and altiris sends the command to reboot, the workstation just hags there ,  there is no more power to the usb keyboard and monitor,  it is just on with nothing going on..    I have updated the bios and still nothing, I am figuring it hasto do with the command for reboot but how do I change it in Altiri and whatis the most universal reboot command..  and can we test it before ,  ie from the command prompt on another workstation

appears to be caused be external usb device.  Particulary barcode scanner on our library checkout machines.  Unplugging usb cable prior to power on appears to solve problem