Deployment Solution

 View Only

  • 1.  Initial Deployment Job reboots computer instead of deploying an image

    Posted Sep 23, 2010 05:54 AM
      |   view attached

    Dear all,

    I am evaluating DS 6.9 SP4.

    As soon as an unknown (new) computer connects to DS via DAgent (in WinPE), an initial deployment task to deploy an image is assigned. This is ok, but my problem is that DS instructs DAgent to "boot to automation", closes the connection and sends Wake-on-LAN-signal instead of deploying the image.

    While creating the deployment task I have left all settings as default, except for the option to use RDeploy instead of RDeployT. See screenshot (in german, but the options are the same) for details.

    Thank you,

    kind regards,
    Dimitri



  • 2.  RE: Initial Deployment Job reboots computer instead of deploying an image

    Posted Sep 23, 2010 07:50 AM

    What did you specify as your default automation environment in your PXE configuration? Is it different then the WinPE your booting to for unknown computers?



  • 3.  RE: Initial Deployment Job reboots computer instead of deploying an image

    Posted Sep 23, 2010 08:47 AM

    Hello,

    the default boot automation is "Next Device (BIOS/EFI)". Automation option for unknown computers is "WinPE (auto)".

    The idea is, computers should boot in WinPE only if they are unknown to DS. This should be fool-proof if a user boots his computer from network by mistake. I have seen it working this way.

    An initial deployment task has to be scheduled only if DAgent is started from WinPE, but this can be realized with cases.

    Thank you,
    Dimitri



  • 4.  RE: Initial Deployment Job reboots computer instead of deploying an image

    Posted Sep 23, 2010 09:52 AM

    Dimitri,

    Under Konfiguration,

    Uncheck the option "Zum AbschlieBen der Konfigurationsaufgabe...." and give it a try.
     
    I think that this option causes the computer to reboot if enabled with WinPE (at least with a boot CD, if I remember correctly)
     
    HTH
    Marco


  • 5.  RE: Initial Deployment Job reboots computer instead of deploying an image

    Posted Sep 23, 2010 10:31 AM

    Hello all,

    Under Configuration, I deactivated all options except for "Use DeployAnywhere (hardware-independent deployment)" and selected "WinPE (32-bit)" under "Preboot automation environment" and it is working now.

    Next thing is to try installing DAgent on an already configured computer - the computer is unknown to DS, but DS may not schedule an initial deployment event for this computer.

    Thanks, everyone.

    Kind regards,
    Dimitri



  • 6.  RE: Initial Deployment Job reboots computer instead of deploying an image

    Posted Sep 29, 2010 04:49 PM

    Pretty sure that your solution was the "auto" vs "32-bit" swap you made.  If Auto selects a minutely different WinPE than the 32-bit one (i.e. 64 bit) and the task calls for the 32 bit, you'll see that behavior.  The first comment on the thread was spot-on.



  • 7.  RE: Initial Deployment Job reboots computer instead of deploying an image

    Posted Oct 03, 2010 04:10 AM

    Marcos solution should work.

    By default all capture image task/jobs prepare the OS for imaging. Thus, the agents execute prepare for imaging tasks before the client reboots into production. aclient disables networking, i think dagent does the same.

    Just uncheck the boot to production and u should be good to go.

    nelo