Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Failed to "Boot to" preboot images for restart automatically

Created: 17 Sep 2012 • Updated: 27 Sep 2012 | 5 comments
This issue has been solved. See solution.

Hi all:

        I'm now using altiris 7.5,  the version is 7.5.1212.

        I create a task of "Boot to" which could make the client server reboot to the target image we setted in the task.

       After I run this task , the client server reboot to target image first, but it restart automaticlly and immedimately and reboot to the target image again.

       The result is that my client server restart again and again until the task timeout in altiris server.

      The task can showed as followed:

    I confirm that the client server can boot to the target images successfully when it boot from pxe by itself but not be rebooted by the task above.

   What's more, I've enabled all of the items in the "Setting -> Agent/Plug ins " as followed:

 

 

 

Does anyone know how to solve my problem, Thanks very much!

Comments 5 CommentsJump to latest comment

andykn101's picture

You need to post to the beta forum.

But you could try specifying x86 or x64 instead of "Auto" in "Boot to".

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

Sachin_Joshi5's picture

Hello,

First of all, Enableing all items(as shown in picture 2) is not required as that won't help on the other hand they will start  installing & uninstalling plugin-in/pocliy from managed clients as and when NS's inventory is updated.

What is architecture of your client machine? You can stop & delete the task's run instance & then try to re-run with x86 or x64 architecture as appropriate.

>>>After I run this task , the client server reboot to target image first, but it restart automaticlly and immedimately and reboot to the target image again.
[Sachin] Is there any other 'boot to' task running concurrently?

Please let me know.

Thanks,
Sachin

 

 

John_Zhou's picture

Hi Sachin:

     I problem also exist if I "stop & delete the task's run instance & then try to re-run with x86 or x64 architecture as appropriate."

     I confirm that there is no other task running concurrently.

    What's more, I found that the problem only occurred when the target image is a customized image.  But, my client server can boot to this image by itself successfully but not be booted by the "boot to" task. So, I think my customozed is have no issues.

     Can you give me some instructions ? Really thanks you very much!

John_Zhou's picture

Hi Sachin:

      In the customized image, we set our client should reboot if it receive a message from a keyboard or file after it boot to this image successfully.

     So, I want to know does "boot to " task  send message to client server although it has received the successful message send by client using this commonds followed?

     /usr/bin/aex-cta list

     /usr/bin/aex-cta flush

     

Sachin_Joshi5's picture

Hi John,

After discussion about this issue with DS dev I came to know that there is a separate mail thread going on for this. Once the dev team gets required details from you, they can have look at those details.

"Boot to" task sends message to console after the task is complete but in your case that is not happening if custom image is used.

Thanks,
Sachin

 

 

SOLUTION