I've been working with support on this a little but not having luck yet. Was hoping maybe to see if anyone else may have some suggestions.
The scenario is a new W2K16 based Session Host with Office 2016. The app layer was prepared according to the recipe and we've checked the flag files and kms files etc. It all appears to be in the right place.
What happens is that the image template is deployed with the MCS connector and the snapshot auto created by App Layer ELM. Then when deploying via MCS, MCS fails with a "Office Licensing Rearm Failed". I have had some success powering on the image confirming everything looks healthy (windows activated, office activated) then shutting down and creating a manual snapshot which then deploys via MCS successfully. However I updated my OS layer and no other changes (just removed the previous windows versions via disk cleanup) and then tried deploying again. This time, neither the app layer snapshot, nor my manually created snapshot worked.
We are trying a Win10 image and having a similar experience (MCS fails). I've seen about bypassing the MCS rearm step but I am hesitant to make a global site setting that affects everything because one new image is broken.
When logging into the image created by app layering, everything looks healthy and activated. I do not open any office applications.
If I do the same thing and publish an image without office it all works.
Question
Terry Rebstein
Hi,
I've been working with support on this a little but not having luck yet. Was hoping maybe to see if anyone else may have some suggestions.
The scenario is a new W2K16 based Session Host with Office 2016. The app layer was prepared according to the recipe and we've checked the flag files and kms files etc. It all appears to be in the right place.
What happens is that the image template is deployed with the MCS connector and the snapshot auto created by App Layer ELM. Then when deploying via MCS, MCS fails with a "Office Licensing Rearm Failed". I have had some success powering on the image confirming everything looks healthy (windows activated, office activated) then shutting down and creating a manual snapshot which then deploys via MCS successfully. However I updated my OS layer and no other changes (just removed the previous windows versions via disk cleanup) and then tried deploying again. This time, neither the app layer snapshot, nor my manually created snapshot worked.
We are trying a Win10 image and having a similar experience (MCS fails). I've seen about bypassing the MCS rearm step but I am hesitant to make a global site setting that affects everything because one new image is broken.
When logging into the image created by app layering, everything looks healthy and activated. I do not open any office applications.
If I do the same thing and publish an image without office it all works.
Any help is appreciated.
Some reference docs I've reviewed:
https://support.citrix.com/article/CTX224900
https://support.citrix.com/article/CTX223245
More info:
Broker version XenDesktop 7.9
VDA 7.11
Link to comment
12 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now