So you're using Office 365, not just Office 2016?
Office 2016 MSI installs, KMS volume licensing.
VMware was unable to fix...other than saying update the App Vol to latest version. If this does in fact fix, I will post.
I was able to successfully create the Visio and Project App Stacks. Again, Office is on the Parent Image. The steps I followed were:
1) Clone the Parent image used for the specific Desktop Pool that the AppVolume will be attached to.
2) On the clone image (CI):
A) change the host name.
B) Remove (In this specific sequence!) AppVolumes Agent, UEM Agent, Horizon Client.
C) Ensure MS Feb' 2019 Update is removed (actual KB referenced in the chain above)
D) Reinstall AppVolumes Agent.
3) Power down and snapshot the CI
4) Power up the CI
5) Create new AppVolume and use the new CI as the provisioning machine
6) log in as the local admin account to CI, NOT a domain user account. (not sure if a factor, but I always do it to avoid capturing a new user profile)
7) Run .MSI but DO NOT run the actual application.
8) DO NOT run any re-arm or licensing commands.
9) Complete capture as normal.
This resulted in an AppStack that is usable ONLY on the desktop pool that was created with the same provisioning machine as the AppStack. I needed to create a CI for each pool that needed Visio and Project resulting in multiple AppStack versions specific to each pool. If ANY change is made to the Parent Image installation of Office, you may need to repeat the process to capture a matching AppStack. After a successful capture, we had to uninstall/reinstall Office on the Parent image (longer separate story regarding MS patching) and it broke the existing AppVolumes for Visio and Project. We also had a MS office patch break the Volumes, but rolling back the patch resolved the "setup" issue with the existing stack.
I've read through the chain, I do not see the KB number you are referring to as 'Feb MS Update' is this an OS, Office. IE, .net?
I would like to run through the steps you provided, once. ;-)
If you could pass on the exact KB number...
Sorry, I could have sworn there was a link to the discussion referencing it. See Custom Appstack.
I believe the exact KB is dependent on the version and build of Windows you are using. We are on Windows 10 LTSC 2019 and the KB I removed was KB4487044
Thanks for all the help. Still getting an error.
Any updates on this issue.
we in the process of doing an updated soe Build with office feb patches etc
and each time we do a new install of Visio/Project
we get the same issue.
thanks In advance
Have you tried disabling the Office Software Protection Platform service in your capture machine? This prevents Office from performing any inadvertent reevaluation of your Office license and configuration status during the capture process of other applications. You keep the service enabled in your Gold Image, just disable on your capture VM. This solved a similar issue for us.
We did the following to fix the issue:
Create an appstack using a 2.13 template.
Provision to an app packaging machine that has Office 2016 installed.
Install Visio 2016.
DO NOT OPEN Visio after install completed.
Assign to user, and log into QA/Prod machine.
Windows 10 1709.
Office 2016 (x86 - Patched to Feb 2019) installed in Gold image.
This did not work thank you. It appears that service is required or Office freaks out during install. Thanks any ways!
still having the same issues, including running the new 2.18 agent. Seems that any form of updates that happen that separate the template/image from the captured version messes everything up entirely.
Windows 10 1809 LTSC
Latest September patches installed on golden image for instant clones as well as the reference/provisioning machine.