New to AppVolumes

[piratefan]

I'm fairly new to AppVolumes (2.12)

Most of the applications that I'm trying to AppStack appear to capture correctly, but when I got to assign them to a user, the user get some kind of action that is prompting for a (first time) user configuration.

For example, the last app I tried was SnagIt.  At first launch, it was looking for additional files that was previously stored in the install directory.

I am installing all the apps for "All Users".  In most cases, I'm using the same install configuration that we use for our SCCM deployments.

Any assistance would be appreciated.

[mellicott]

Anything that was installed to the roaming profile, or HKey Current User, areas of your provisioning machine will not be saved in your appstack.  You need to provide for these in another manner, for instance UEM.

You can therefore have a first run experience to put these files/setting back, and will get that every time unless you save these somewhere.

[piratefan]

thank you for your response.

In the particular example with SnagIt, I'm being prompted to browse to the snagit.msi for addition user-based configuration that requires elevated privileges.

I understand UEM, but how would that tool prevent these types of prompts from occurring..or was your thought have the customer step through them 1 time and let UEM capture  their results for future application launches ?

The big question here is if I'm using a SCCM build that also used an ALL USERS configuration, how does that conflict with AppVolumes ?

[mellicott · Accepted solution]

Ah, I've seen that issue before. 

If you look at the properties of the shortcut, is the target greyed out and not shown?

If so, this is an "advertised shortcut" and they work differently (they are a pain!).  I usually delete these and replace with a shortcut created from the .exe itself, replacing the advertised shortcut you've deleted.

[piratefan]

that seems to be the trick.  thank you