Solved: Re: Visio 2016 - Keeps running Office 2016 configu...

pbastiaans · ‎02-04-2019

To create this app stack:

Downloaded Visio 2016 VL from MS VLSC (verified it is not retail version)
Followed instructions from here to build Office 2016 on the ref image: VMware Knowledge Base
Created a new app stack on this ref image VM, using the Visio 2016 MSI installer previously downloaded.
Ran cscript.exe ospp.vbs /rearm

I get the Office setup, whenever this Visio 2016 app stack is assigned.

As part of troubleshooting I have:

Run the Office 2016 repair while provisioning
Run the Office 2016 and Visio 2016 repair during provisioning
Created the app stack on a 'vanilla' VM without Office 2016 suite

pbastiaans · ‎09-11-2020

This was resolved by placing Office on the reference image.

View solution in original post

pbastiaans · ‎03-04-2019

Bueller. Bueller.

rcscott44 · ‎03-04-2019

I have the same issue. Running AppVolumes 2.15, Office 2016 Pro+ on the golden image of Win10 LTSC 2019 instant clone pool (Horizon 7.7)

Capture machine is a clean build of Win10 LTSC 2019. and have used the VMware Knowledge Base for the capture. Trying to capture Visio 2016 Pro and Project 2016 Pro.

I have tried installing with Office 2016 Pro+ on the provisioning machine and without it. Both seem to capture with no issues. But, when attaching to the instant clone, it launched into set-up and then fails with "can't find necessary file" type errors. If I close Visio, wait for set-up to revert itself and stop, I can re-open Visio and be functional, but it will not activate and de-activates Office 2016 Pro.

I have tried capturing the AppStack off the golden image for the instant clone pool, but the Visio installation fails to run with the same missing files errors.

Lastly, we use Active Directory-Based Authentication, not KMS server. Does anyone know if an actual KMS server is required? ADBA authenticates Visio 2016 Pro as a non-AppStack install just fine.

From the instant clone Application event logs, I can see install errors involving language packs, but both Office and Visio are configured with the exact same settings (Install All from Desktop).

pbastiaans · ‎03-04-2019

We're not on Win 10 yet...that's coming in the next few months.

The only suggestion I have is:

- Clone the reference image you publish to the pool

- Remove the Horizon agent/UEM Agent

- use this as your provisioning device

I have not been able to create an app stack of Visio 2016 (MSI Install). Period. VMWare support has been horrible. To the point one tech told me to exclude \program files (x86\microsoft office in snapvol.cfg

rcscott44 · ‎03-05-2019

I tried that exact method. I cloned my golden image, renamed, removed App Volumes, Horizon, UEM, and VM Tools. I then re-installed AppVolumes only and took a snapshot. When I tries to create a new App Stack and use the clone for provisioning, App Volumes saw the clone as available and allowed me to use it to provision. However, when I logged onto the clone, the AppVolumes Agent never ran and I got no window saying that AppVolumes was capturing.

Ray_handels · ‎03-06-2019

Just out of curiosity. Do you have Office itself (I know, Visio is part of Office, old school admin here ) installed on the golden image?

If you do have it installed there there is no need to rearm Visio during packaging, it sill use the Office "license" on the GI for as far as I know.

pbastiaans · ‎03-07-2019

VMware is suggesting this issue is resolved with app vol 2.14...where's that grain of salt?

Ray_handels · ‎03-08-2019

VMware is suggesting this issue is resolved with app vol 2.14...where's that grain of salt?

What version are you using now?

And to be honest (and believe me I have seen my fair share of Appvolumes versions) the 2.14.2 version has been one of the most stable versions VMWare made. 2.15 seems to be pretty decent as well apart from the packaging process that has some issues (not taking the February Microsoft Patch into account) when you need to reboot.

We went from 2.14.2 to 2.15 without much of a hassle.. Versions seem to be more stable and stable as we go..

rcscott44 · ‎03-08-2019

We are AppVolumes 2.15. We upgraded about a month ago from 2.14.2 because we are deploying Win10 LTSC 2019 for our instant clones.

Additional info: when I use a provisioning machine that was cloned from our golden image (remove Horizon and Uem, reinstall AppVolumes last) The installer fails with the generic can't find file error, with no code or idea of failing file during the capture. However, I can run the install on that provisioning machine natively when not capturing.

Ray_handels · ‎03-08-2019

Additional info: when I use a provisioning machine that was cloned from our golden image (remove Horizon and Uem, reinstall AppVolumes last) The installer fails with the generic can't find file error, with no code or idea of failing file during the capture. However, I can run the install on that provisioning machine natively when not capturing.

That seems to be the February patch issue.

jmatz135 · ‎03-12-2019

Are you using MSI installers for the Office and Visio install or Click-to-Run? You can't mix and match as far as I know.

I have MS Office 365 installed in an appstack installed with the click-to-run package with this config:

</Product>

</Add>

</Configuration>

This was done on a clean provisioning machine. Then on the same clean provisioning machine i.e. without the Office suite installed I captured Visio using the same Click-To-Run package but used this config:

</Product>

</Add>

</Configuration>

This seems to work except for Visio attachments won't open directly from Outlook. Haven't seen any other issues though.

pbastiaans · ‎03-14-2019

MSI Install. Support says upgrade to 2.14, taking that advice with a shaker full of salt.

rcscott44 · ‎03-14-2019

We are also using MSI install for all applications, no O-365.

Part of our problem has been resolved. Our provisioning machine did have the Feb'19 MS update and was blocking the MSI install when provisioning. I removed the KB and was able to successfully provision a working AppStack for Visio and Project 2016. I used a clone of the Desktop Pool's golden image (minus Horizon and UEM agents) and it all worked fine.

The last issue I have is that the Visio and Project applications will not activate. They do activate when installed on a base image, or stand-alone PC. Office on our base image activates without issue, but the AppStack does not not.

-Bob

pbastiaans · ‎03-14-2019

Thank you Ray - Possible to get that KB number?

pbastiaans · ‎03-14-2019

Bob

Do you have Office on your golden?

License activation, I have found these commands helpful (apologies if preaching to the choir)...

Check activation status..

cscript.exe ospp.vbs /dstatus

Check activation status all (found hidden stuff this way)...

cscript.exe ospp.vbs /dstatusall

Activates (this can also be added to app vol bat file or UEM to force)...

cscript.exe ospp.vbs /act

List KMS Server (we found a server had come up as a KMS server, which slowed/broke activation)...

cscript slmgr.vbs /dlv

aflopez · ‎03-14-2019

So you're using Office 365, not just Office 2016?

pbastiaans · ‎03-15-2019

Office 2016 MSI installs, KMS volume licensing.

pbastiaans · ‎04-12-2019

VMware was unable to fix...other than saying update the App Vol to latest version. If this does in fact fix, I will post.

rcscott44 · ‎04-12-2019

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.

😎 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.

-Bob Scott

pbastiaans · ‎04-15-2019

Bob,

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...

Thank you!

All

Visio 2016 - Keeps running Office 2016 configuration