App Volumes Writable Volumes 2.14 - Windows 10 1803

[future2000]

Hi,

Forgive me for these simple questions, but I could not find much in the documentation.

Can we allow Standard Users to install applications on a Windows 10 1803 Instant Clone with the App Volumes Writable Volume (App Only, not profile) attached?

If so where are the applications installed to? Where is the writable location?

I cannot see the symlink which is allegedly created for an App Volume using junction64 sysinternal tool. Is there anyway to see this?

Does the user need to know to install the application to a particular folder when performing the installation or will the installer manage this?

To summarise, how are users meant to install applications on the Writable volumes. How is this achieved?

Many thanks

[Ray_handels · Accepted solution]

When you create a writables it does nothing more than create a VMDK with the name of the user.

When logging in this writable is being attached to the machine as an extra disk. You can check disk management, there should be a disk there that is called CVWRITABLE without a drive letter.

You can also go to c:\Snapvolumestemp (cannot browse to it, you need to type it) and there should be a lync called writable. the actual mountpoint is in that same folder under MountPoints.

When you install something the filter driver of Appvolumes writes the information to that writable disk and saves it there so the next time you log in it is still there.

If you do wanna look at the info on the disk(DO THIS AT YOUR OWN RISK!!) you can attach the disk to a machines that does NOT have the Appvolumes agent installed. Otherwise the filter driver will merge the information again.

Do keep in mind that UIA only does not capture the shortcut to the application or the application settings if they are created in the %USERPROFILE% folder. You would need another tool to capture that or use writable + profile.

[future2000]

Appreciate you taking the time to respond. Very good to know that UIA won't capture the shortcut and settings. Hopefully UEM will however. More testing needed.

Cheers

[Ray_handels]

UEM will only capture it if you tell UEM to capture it, that's how it works.

UEM you need to whitelist, Appvolumes writable you need to blacklist.

The reason why we still use profile for writables is that right now it is hard to see what applications users install themselves and also capture those settings of you are not aware of that application.

You could try and use some sort of script that records all executables being started so you know what applications are being installed by users.. Or maybe UEM can fix something?? **WINK WINK**