PVS TDs Machines don't always start after scheduled Reboot

[Rakesh Kondabattini]

Citrix Studio-Version: 1912.0.3000

Provisioning Services Console-Version: 7.15.33.11

Hypervisor-vSphere Client version 6.5.0.37000

 

I scheduled a reboot directly through studio at to reboot daily for all my some of the delivery groups but some of the VM reboots fine and some of the VMs does gets powered off and i had to manually reboot those machines daily this is kind of manual job daily.

 

Can some one suggest me how to fix this issue at earliest.

[CarlStalhood]

Maybe this? https://support.citrix.com/article/CTX237058

[Jeremy Hanson]

Yes would definitely recommend those timeout settings in that article. With the default settings the broker can ‘give up’ on the reboot operation before the VDAs have drained and shut down, with the result that some might not power up again. 

[Darryl Sakach]

Does anyone know, since these Reg entries are at the On-Prem Delivery Controller level, would they be set on the Cloud Connectors in a Citrix Cloud Services environment?

[Spasia Zhivkova]

@Carl Stalhood 

Quote

Any idea if those reg keys interfere with the reboot cycle duration?

 

[Christian Bianchini]

Hello,

 

We have the same issue since updated in 7 2112.

We put the https://support.citrix.com/article/CTX237058 reg keys, but nothing change.

 

Does anyone have another idea please?

 

Thanks,

[Spasia Zhivkova]

Yes, i applied registries shown here and since then we do not have a single server down! 

http://knowcitrix.com/server-vdas-remain-shutdown-after-schedule-reboot/>

 

However, first you have to confirm that all else is fine (time for reboot/number of machines/message sent). You could run 

Get-BrokerRebootCycle  to get inforation are your machines '"Skiped" or they are "Failed". 

Registries above are only applicable in the particular situation explained in the post. They should be applied to all DDCs.