Can you elaborate on what is breaking? How the separation been done (base image + base apps vs. appstack captured apps)
I receive the following error after deploying the recently packaged app (either Project or Visio):
"The application can't start because AppVIsvSubsystems62.dll is missing from your computer"
The answers typically state to reinstall the app, or use the online office repair tool, both of which aren't helpful in our non-persistent environment.
Our base image includes:
AppVols Agent 2.18
Office Pro Plus 2016
C++ Redist 2013, and 2017 (both x86, and x64)
VMware Tools 10.3.5
Visio and Project work in the packaging environment, but break once provisioned to test users.
Installing Visio and Project in the user session works as intended, but non persistent environment makes this redundant exception of testing.
We thought it may be AV causing the issues, but cant confirm yet.
Office and Appvolumes is a very tricky combination.
What licensing method are you using? My guess is KMS?
Also, what package machine are you using? Best practice is to clone the GI machine and remove the obsolete agents within the packaging machine, then package the application in that machine.
Agreed, Office has always been a thorn in our side. We've moved away from Office 2016 in a stack, to in the build itself.
Now playing with 2019 via both means is producing the above error, as well as this one below:
"We're sorry, but Visio has run into an error that is preventing it from working correctly. Visio will need to be closed as a result.
Would you like us to repair now?"
Repairing closes the app indefinitely. Fun times.
To answer your questions, yeah, we're using KMS for licensing and running best practices for packaging.
Just curious whether others have successfully packaged 2019 for their environments.
Not there yet to be honest but we will be installing Office into the GI and I think that we will try and install Visio and Project within a ThinApp to remove the database licensing issue.
Any luck with Visio/Project ?