VMware Horizon Community
pbastiaans
Enthusiast
Enthusiast
Jump to solution

Visio 2016 - Keeps running Office 2016 configuration

To create this app stack:

  1. Downloaded Visio 2016 VL from MS VLSC (verified it is not retail version)
  2. Followed instructions from here to build Office 2016 on the ref image: VMware Knowledge Base
  3. Created a new app stack on this ref image VM, using the Visio 2016 MSI installer previously downloaded.
  4. 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
32 Replies
rcscott44
Enthusiast
Enthusiast
Jump to solution

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

-Bob

Reply
0 Kudos
pbastiaans
Enthusiast
Enthusiast
Jump to solution

Bob,

Thanks for all the help. Still getting an error.

Paul

Reply
0 Kudos
Natestack
Enthusiast
Enthusiast
Jump to solution

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

Reply
0 Kudos
DanVM99
Enthusiast
Enthusiast
Jump to solution

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.

Reply
0 Kudos
Dempseyy93
Enthusiast
Enthusiast
Jump to solution

Hi pbastiaans,

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.

Finish provisioning.

Assign to user, and log into QA/Prod machine.

Open Visio...profit!.

Evironment details:

AppVols 2.16.

Windows 10 1709.

Office 2016 (x86 - Patched to Feb 2019) installed in Gold image.

Reply
0 Kudos
pbastiaans
Enthusiast
Enthusiast
Jump to solution

This did not work thank you. It appears that service is required or Office freaks out during install. Thanks any ways!

Reply
0 Kudos
Anobix67
Enthusiast
Enthusiast
Jump to solution

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

AppVol 2.18

Office 2016

Latest September patches installed on golden image for instant clones as well as the reference/provisioning machine.

Reply
0 Kudos
XSavior
Contributor
Contributor
Jump to solution

Has there been any progress on this issue?

I am facing this issue as well.

Windows 10 (1803) /w AppVolumes 2.17.0 on Horizon 7.9 and Office 2016 on Gold Image with Projects and Visio each placed on their own AppStack.

You can open any of the core Office Apps (Words/Excel and ect) over and over just fine... but if you open Projects or Visiso it will open the first time just fine but then after that any Office App will run the Setup again every single time you open an Office App. Really frustrating.

The only work-around I know is to have all of the apps on the gold image and then they all work fine together.

Originally if I installed Office on the Gold Image and Projects and Visio into Appstacks they would all work together AS LONG AS YOU DID NOT RUN WINDOWS UPDATE to update office. This problem has started when you try to update Office in any way (both on Gold Image and on AppStacks).

AppVolumes 4 is on the way soon but I have no idea if this issue is fixed???

I just noticed in 2.18.0 Release notes: https://docs.vmware.com/en/VMware-App-Volumes/2.18/rn/VMware-App-Volumes-218-Release-Notes.html

VMware App Volumes 2.18 Release Notes

Resolved Issues

  • When Office 2016 is installed in the base, an installer pop-up is displayed as follows:Please wait while Windows configures Microsoft Office 2016
    [2336096]

I will be updating and checking if the issue is resolved as well.

Reply
0 Kudos
dmmcsherry
Enthusiast
Enthusiast
Jump to solution

While we haven't seen this issue with Visio, we did run into the issue with the entire Office Suite when upgrading from 2013 to 2016. We resolved the issue by adding the NoReReg option in HKCU hive of the registry (had to be done with profile management tool, we are not using UEM/DEM).

reg add HKCU\Software\Microsoft\Office\16.0\Word\Options /v NoReReg /t REG_DWORD /d 1
reg add HKCU\Software\Microsoft\Office\16.0\Excel\Options /v NoReReg /t REG_DWORD /d 1
reg add HKCU\Software\Microsoft\Office\16.0\Access\Options /v NoReReg /t REG_DWORD /d 1
reg add HKCU\Software\Microsoft\Office\16.0\Powerpoint\Options /v NoReReg /t REG_DWORD /d 1
reg add HKCU\Software\Microsoft\Office\16.0\Outlook\Options /v NoReReg /t REG_DWORD /d 1

The path is the same for Visio, though I can't confirm if it will resolve what you are

reg add HKCU\Software\Microsoft\Office\16.0\Visio\Options /v NoReReg /t REG_DWORD /d

Reply
0 Kudos
sjesse
Leadership
Leadership
Jump to solution

I just did this with window 1809 7.10 2.18, I had office in the base image and visio in an appstack it gave me the reconfiguring issue, but if you had both office and vision in seperate appstacks it fixed the issue at least for me.

Natestack
Enthusiast
Enthusiast
Jump to solution

had a go at this as well on windows 10 1809

had the latest agent installed 2.18.2 and did the norm office 2016 in build same as desktops and installed visio 2016

didn't open visio finished the capture and bam all working normally.

So now im interested i know not supported but office 2019 with visio/project 2019

Reply
0 Kudos
eriewilson
Contributor
Contributor
Jump to solution

I had this same issue with every deployment technology I have tried to use.  Visio always repairs, but I found a workaround

Search the registry for "C:\Program Files (x86)\Microsoft Office\Office16\VISIO.EXE" and replace it with "C:\Program Files (x86)\Microsoft Office\Office16\VISIO.EXE /noreg"

Next replace the icon in the Start Menu folder with a manually created icon adding the /noreg switch at the end of the command-line

pbastiaans
Enthusiast
Enthusiast
Jump to solution

This was resolved by placing Office on the reference image.