XenDesktop 7.11 on AHV (Plug-in compatability) | Nutanix Community
Skip to main content
The Nutanix MCS Plug-in seems not to workwith latest VDA release of XenDesktop 7.11. Can you confirm this incompatability? Is there a newer Version of the Plug-in that works with XenDesktop 7.11?
Please file a support ticket with priority "Request for Enhancement" RFE on portal.nutanix.com and ask them to link your ticket to Nutanix Engineering ticket ENG-62023.



This is our internal ticket tracking 7.11 support, and your support ticket will help us formally track customer demand for this support. The more customers demand something, the more priority it tends to get within Engineering to complete.
Hello



Currently the plugin is undergoing certification on XD 7.11 and we should release it in a week or two. There was an installer issue which we have fixed . No changes to the plugin or functionality.



Thanks,

Parth
Addin further if the customers had already installed the plugin on 7.9 and if they upgrade to 7.11 , they need not reinstall the plugin . The MCS plugin should work on 7.11 as well
upgraded from 7.9, plugin works in studio but when try to provision windows 10 1607 with the latest 7.11 VDA the process errors during copying the master image. on ahv and no VMs are cloned
Okay this seems to be a different issue , can you mail us the exact error details . It could be VDA 7.11 compatability issue on Windows 10 . We had similiar issue for VDA 7.9
Also can you also collect CDF diagnostic logs . Make sure you select all the topics .



http://support.citrix.com/article/CTX111961
For the sake of having this formally tracked, can you submit a support ticket and reference this thread URL, so we can pick up with the support team? Then we can also hop on a webex to view this all live.
Yup , that will be the right approach . Will wait for the support team to reach out to us (engg team) if the issue is not sorted out .
support ticket is #00082319
We did some analysis . It is not related to the MCS plugin . There is an advisory published by Citrix pertaining to Win 10 anniversary version .





On Citrix support link - http://support.citrix.com/article/CTX216312 , It is mentioned that –

Citrix strongly advises not to apply the Anniversary Update (v1607) on existing Windows 10 machines with Citrix VDA for Windows Desktop OS or Citrix Receiver installed.
this advisory is only for upgrading an existing Win 10 VDA to Win 10 1607. We did a fresh install based on a new created base image. This is working without issiues on XenServer hosting ressources within the same XenDesktop Farm
Okay even then we were unable to replicate the issue at our end



Our QA team upgraded base VM having Win10 1511 by running Anniversary Update (v1607) on it. The machine was already having VDA 7.11 installed on it.

After upgrade is complete, we took the snapshot of the base Vm and used the same to create machine catalog on XD 7.11 prod setup. Machine preparation is successful and VMs are created and not facing any issues during machine preparation.



Forwarded the details to Jon as well . Prima Facie it is not a plugin issue .
thx! you are right, there was something wrong with the vda installation, after re-install the provisioning works!but now there is an issue on logoff from the provisioned non-persistent VMs. During logoff the VMs crash with a blue screen and this leads to corrupt upm userprofiles...
This should be a known issue . We just need to search theCitrix KBs . For example there is an issue When we power ON VMs having Win10 v1607, the machine is automatically restored to the previous version of the windows.This is a known issue (Issue#3) in the citrix support link -http://support.citrix.com/article/CTX216312 & they provided solution as well.I suggest you to go through the Citrix KBs
This is another issue mentioned in the KB: i'am not working with upgraded VMs, it is a fresh/clean install based on windows 10 1607
Yeah this is another issue . I just gave it to illustrate that there are some known issues related to Windows 10 anniversary issues . Your issue might be one of the known issues for which you need to do some searching on Citrix KBs