There are a couple of places this can go bad. One is, never run any Office component in the Install Machine. The first time Office runs, it writes some machine-specific information into the registry, and if that layer then wakes up on another machine, it has to go through the configuration again. Visio definitely counts as an Office component.

But the real problem with trying to put individual Office components into separate layers is that they are really all a part of Office, and share a lot of files and information. So if you have, for instance, Visio all by itself in a layer, that layer says that Visio is the only Office component present. If you put that layer on a desktop that also has the rest of Office, Office gets really confused. And this is generally true whenever you try to split up a single software suite into separate layers (AutoDesk software, for instance, breaks badly if you try to have it in discrete layers).

You have two choices: make sure you always include your main Office layer as a prerequisite when creating/editing Visio, or just make a combination Office+Visio layer for the people who need both. I don't like the first option, because it's not really stable. In Unidesk, layer priority is based on the creation time of the specific layer version you have. So when you create the new Visio layer with Office as a prereq, it's fine because Visio will have a higher priority. When you later Add Version to Office for updates, then suddenly that Office version is a higher priority than the Visio layer. When you apply that new Office layer to a desktop, then Visio isn't written into all the right shared files anymore.

Having a single layer for Office and a single, separate layer for Office+Visio (and similarly, if you need to add Project into the mix, separate layers for each of the various combinations you require) is going the be the simplest way to make sure this always works.

We also have an Office recipe which is worth consulting.

https://support.citrix.com/article/CTX224566