If you send a managed computer into automation with no other job assigned using a Reboot To task, when the managed computer gets into automation, the "Redeployment Menu" for managed computers (found under Initial Deployment) does not display. The same computer manually booted into PXE will get the Redeployment menu.
This is by design. The "Reboot To" task counts as an assigned job, and the job does not complete until the client reaches automation, gets the task again, and then reports back up that it's already in automation. The task therefore is still running, and still assigned, until after the agent initializes.
The "Re-Deployment Menu" functionality in DS is configured so that "when a managed client boots into Automation and there are no scheduled jobs for the client, then a predefined list of jobs will be displayed." This is configured in the console as part of the "Initial Deployment" options for DS with a manually selected list of pre-created jobs and/or tasks.
The key is that this schedule only appears if there is nothing scheduled, and the Reboot To task IS, in fact, already scheduled.
It should be noted as well that the initial deployment / redeployment menu is displayed as the first thing run, prior to even getting any tasks, so by the time the agent is fully initialized and getting tasks, this period is passed. You can actually see the check for the menu in the PECTAgent logs immediately after discovery of the hardware and before full hand-off to the SMP log.
This is working as designed. For the redeployment menu to display, a system must boot to automation manually, and with no jobs of any kind assigned. For the Initial Deployment menu, the rules are the same, though since the computer is unknown, you can't actually schedule a job to boot to automation anyway.
Imported Document ID: TECH215246
Subscribing will provide email updates when this Article is updated. Login is required.