Citrix XenDesktop 7.15 MCS, SCVMM, Win10 non-persistent VDIs "update failed" Error.
Citrix XenDesktop 7.15 MCS Machines in the non-persistent pool go into update failed state intermittently. once we run a repair for the VM from SCVMM the machine is working as expected. I am seeing this only with non-persistent machines and not persistent ones.
Also, this does not happen for all the machines in the pool. This issue happens on around 100 machines out of 500 and each time it is a different set of machines
Citrix Xendesktop 7.15 LTSR CU3
SCVMM 2016
Hyper-V host: windows server 2016 DC
1->Issue is occurring in all windows 10 non-persistent Desktops for the users using MCS.
2->At the time of the issue, we are seeing that the machines are in “Update Failed “ state. Through SCVMM we can see failed jobs.
3-> we observed that when MCS triggered any power related activities, like Reboot or Shutdown through SCVMM, those non-persistent Win 10 Desktops are going to “Update Failed “ state. Also, we observed that the differential disk value has been changed. this might the root cause.
Citrix asked us to contact MS as they suspect it to be an issue at the hypervisor layer.
Also, this does not happen for all the machines in the pool. This issue happens on around 100 machines out of 500 and each time it is a different set of machines
Citrix Xendesktop 7.15 LTSR CU3
SCVMM 2016
Hyper-V host: windows server 2016 DC
1->Issue is occurring in all windows 10 non-persistent Desktops for the users using MCS.
2->At the time of the issue, we are seeing that the machines are in “Update Failed “ state. Through SCVMM we can see failed jobs.
3-> we observed that when MCS triggered any power related activities, like Reboot or Shutdown through SCVMM, those non-persistent Win 10 Desktops are going to “Update Failed “ state. Also, we observed that the differential disk value has been changed. this might the root cause.
Citrix asked us to contact MS as they suspect it to be an issue at the hypervisor layer.
ASKER
Hi Olivier MARCHETTA,
Please find the updated query. We are using MCS and SAN Storage.
The issue with non-persistent Win10 VDIs. But with persistent Win10 VDIs are working fine. No issues with Persistent VDI's.
Please find the updated query. We are using MCS and SAN Storage.
The issue with non-persistent Win10 VDIs. But with persistent Win10 VDIs are working fine. No issues with Persistent VDI's.
ASKER
Please provide any solution.
We suspecting issue in SCVMM 2016.
Any such known issues or solutions for this issue?
We suspecting issue in SCVMM 2016.
Any such known issues or solutions for this issue?
Checked WindowsUpdate log on the Win 10 for any problems?
To generate the log, open PowerShell with admin permissions, then run
Log will be generated on the desktop.
If you want us troubleshooting it attach the log here.
To generate the log, open PowerShell with admin permissions, then run
Get-WindowsUpdateLogLog will be generated on the desktop.
If you want us troubleshooting it attach the log here.
ASKER
Issue not with Windows Security patches. We have deployed the same patches in other environments.
Seems issues with MS SCVMM and Citrix.
Any similar issue anyone observed?
Seems issues with MS SCVMM and Citrix.
Any similar issue anyone observed?
ASKER
https://www.experts-exchange.com/questions/29150857/Issue-with-some-vms-not-resetting-but-powering-down-when-sent-reset-commmand-via-Citrix.html
Problem Statement:
We are running ESXi 6.5 and we have vms which are running 2012 R2.
The issue we are seeing is that we have around 80 Citrix servers on these vms and we send out reboot request each Sunday via Citrix for all for all of these vms, but the issue we are seeing is that some of the vms shut down instead of resetting but never power backup while others reboot just fine. So we have to manually power some of them back on.
Is there a setting somewhere that we need to change on the vms and or host so that when they get the command to reset that they do and don't shutdown?
Solution:
I have already seen similar.
Some devices need too much time for shutdown and down-state isn't reached while XenApp wish to power-up the system
i can't find a timing parameter for this.
i build a script powering up all devices with "down" state.
PS: there are possible solutions now...
https://support.citrix.com/article/CTX239537
https://support.citrix.com/article/CTX218117
https://support.citrix.com/article/CTX214838
Requester Answer:
We checked one machine in the registry and the entry was not there for the value of 10 to change to 60 do we just add it
Solution 2:
This must be configured at all DDC.
All VDA has to be restarted afterwards. (at least the broker service)
Problem Statement:
We are running ESXi 6.5 and we have vms which are running 2012 R2.
The issue we are seeing is that we have around 80 Citrix servers on these vms and we send out reboot request each Sunday via Citrix for all for all of these vms, but the issue we are seeing is that some of the vms shut down instead of resetting but never power backup while others reboot just fine. So we have to manually power some of them back on.
Is there a setting somewhere that we need to change on the vms and or host so that when they get the command to reset that they do and don't shutdown?
Solution:
I have already seen similar.
Some devices need too much time for shutdown and down-state isn't reached while XenApp wish to power-up the system
i can't find a timing parameter for this.
i build a script powering up all devices with "down" state.
PS: there are possible solutions now...
https://support.citrix.com/article/CTX239537
https://support.citrix.com/article/CTX218117
https://support.citrix.com/article/CTX214838
Requester Answer:
We checked one machine in the registry and the entry was not there for the value of 10 to change to 60 do we just add it
Solution 2:
This must be configured at all DDC.
All VDA has to be restarted afterwards. (at least the broker service)
ASKER
As per above issue and solution, it's known issue in Citrix XAXD 7.x
Irrespective of Hypervisor, VDI/SBC Power activities are disturbing.
I tried the above solution, but no luck.
Please suggest.
Irrespective of Hypervisor, VDI/SBC Power activities are disturbing.
I tried the above solution, but no luck.
Please suggest.
ASKER
We observed that when Citrix MCS triggered any power related activities, like Reboot or Shutdown through SCVMM, those non-persistent Win 10 Desktops are going to “Update Failed “ state. Also, we observed that the differential disk value has been changed. this might the root cause.
Please suggest.
Please suggest.
ASKER
Any Update? Please suggest
I have never used SCVMM. I think that it's something related to the SVCMM configuration.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are you using MCS or MCS/IO (enhanced write cache)?
What version of Hyper-V are you using? What type of backend storage?