VMware Horizon Community
Anobix67
Enthusiast
Enthusiast
Jump to solution

How to update separate Office applications in an appstack (Visio and Project)?

Hey all, looking for some advice as to how any of you are updating appstacks that have Visio and/or Project in them. Seeing how the updates aren't cumulative like they are for Windows, do you go to update the appstack then run the individual installers and then close up the appstack? (like from here: Microsoft Update Catalog  ?)

Part of the reason why I ask is that while we have office 2016 in our golden image, if we have Visio or Project appstacks attached it causes a couple of the main office applications to re-configure themselves on startup. This just started happening after one of the more recent updates for Office that applied to our GI (as I hadn't noticed it before).

Any advice would be great.

Thanks.

0 Kudos
1 Solution

Accepted Solutions
Anobix67
Enthusiast
Enthusiast
Jump to solution

So the issue ended up being that we have two different Windows 10 builds in testing. One is LTSC and one is a main branch (1709). Most applications have no issues being captured on a 1709 provisioning box, but for whatever reason Visio/Project would have an issue if mounted to the opposite OS (and cause it to re-configure a few [but not all] of the office applications at initial load). I now have two different provisioning machines one for LTSC and one for CB (or whatever mainline build we would be running) to capture one or the other depending on use case.

View solution in original post

0 Kudos
2 Replies
Ray_handels
Virtuoso
Virtuoso
Jump to solution

My guess is that you'd better just recreate the appstack after office patches have been installed. Might be a lot of work but it should work then..

0 Kudos
Anobix67
Enthusiast
Enthusiast
Jump to solution

So the issue ended up being that we have two different Windows 10 builds in testing. One is LTSC and one is a main branch (1709). Most applications have no issues being captured on a 1709 provisioning box, but for whatever reason Visio/Project would have an issue if mounted to the opposite OS (and cause it to re-configure a few [but not all] of the office applications at initial load). I now have two different provisioning machines one for LTSC and one for CB (or whatever mainline build we would be running) to capture one or the other depending on use case.

0 Kudos