Use Case: "We have a schedule to restart the machines in the delivery group every Sunday. The problem is that a few machines don't turn back on, others don't even receive the command to turn off."

Checking the Event Viewer logs in the Delivery Controller we see these errors:

Event ID 3105

Log name: Application

Source: Citrix Broker Service

Text: The Citrix Broker Service has terminated the processing of the GroupReboot for Desktop '[Delivery Group name]'  The reboot cycle UID = 999 ended with the final state 'Abandoned' Summary: '0' machines successfully rebooted, '2' machines failed to reboot. '1' machines were not processed

This software application is provided to you as is with no representations, warranties or conditions of any kind. You may use and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that: (a) the software application may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the software application fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the software application. In no event should the software application be used to support ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SOFTWARE APPLICATION, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the software application.

Run PowerShell command to remove reboot schedule entries in the Database and then Manually re-created the Reboot schedule via Studio-Delivery Group UI.

1. Issue PoSh command: Get-BrokerRebootSchedule At least 5 Reboot schedules for the Desktops were enumerated
2. Compare the Reboot schedule DB fields for all 5 DG's ; They should look identical
3. Issue command: Get-BrokerRebootSchedule -DesktopGRoupName "[Delivery Group name]" (got same results but only for the delivery group specified)

Recommended PoSh commands:
==========================
Remove-BrokerRebootSchedule -DesktopGroupName "[Delivery Group name 1]"
Remove-BrokerRebootSchedule -DesktopGroupName "[Delivery Group name 2]"
Recreate reboot schedule for the two Delivery Groups via Studio UI (user interface)

---

Problem Cause

The Reboot schedule entries in the SQL database were either corrupted or had some minor inconsistencies for the two Delivery Groups affected

Reboot schedule was created for 5 Delivery Groups. However for two of the Delivery groups the reboot did not occur

https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/downloads/broker_events.htm