Reply to Message

View discussion in a popup

Replying to:
Ray_handels
Virtuoso
Virtuoso

@Ray_handels  This is what we were trying to do but we ran into some issues an app may have slipped something by us. Then I think we possibly added that same thing or maybe a different version to the Gold image after thus causing us issues. How do you catch that stuff? I'm guessing looking at the AppStack after creation? So if our AppStack has this would you just move C++ or would you move more? Thank you for your help we really appreciate it.

We install all available version of the vcredist within our golden image, this way normally an installation that requires this has it in the golden image (and package machine which is a direct clone of the GI) available.

If we do see that another version is being installed then yes, we do install it in the gold image, not in the Appstack. We had an issue with an application recently because it installed an older vcredist, after that all kinds of quirky things started to happen. Luckily a newer version of the application was available. Thing is that this will always be a thing no matter if you use physical or virtual machines.

Appvolumes is easy learn but hard to master. You really need to think things through before starting to package. It saves quite the hassle afterwards.

While we have full control of AppVolumes in our environment, unfortunately modifying the Gold image is out of our hands and can often take a while for anything to progress.

This is reason enough for us to tack on dependencies in the stack rather than wholly in the image.

Really?? Thinking about this I think it would be close to impossible to manage application or any VDI environment for that matter if you don't have full control over the GI. Because Appvolumes integrates within the OS as it does you really need to have control over both those things.. But just my 2 cents though.

Reply
0 Kudos