Defining the Device Reboot after the distribution as a user choice

It is also possible to define the reboot of the target device in such a way as to let the user choose if he wants to reboot the device at all, or when he wants to do it. This use case can be implemented in two different ways:

1. Two Operational Rules with a Dependency
   1. Create an operational rule for the Firefox distribution. Depending on where in the distribution process you interrupt, this rule might already be created.
   2. Create a second operational rule to control the reboot process.
   3. Create a dependency between these 2 rules.
   4. Assign and activate the 2 rules.
2. One Operational Rule with an Additional Reboot Step
   1. Create an operational rule for the Firefox distribution. Depending on where in the distribution process you interrupt, this rule might already be created.
   2. Add the steps to control reboot to this rule.
   3. Assign and activate this rule.
       The drawback of this second method is that if the user chooses not to reboot, the whole distribution result will be reported as Failed , while in the first case, the distribution rule will be Executed ( OK ) and the Reboot rule will be Executed (normal as the user decided not to reboot).

The following topics provide more information about defining the device reboot: