VMware Horizon Community
maxman722
Enthusiast
Enthusiast

What all does AppVolume writable volumes save?

Are all changes made in the desktop saved? Or is it only for certain apps or windows settings? If a user installs an application and configures it, should all of that data (the installation of the app and the configuration settings) be saved within the writable volume?

Tags (2)
5 Replies
Rajhere
Enthusiast
Enthusiast

Hello maxman722​ !!

Yes, the changes were written on the VMDK as soon as you make changes on the windows.

0 Kudos
maxman722
Enthusiast
Enthusiast

Can you manually sync the changes? I know that I made changes and rebooted the desktop, and not all of the changes were saved. Is it required to detach the writable volume before restarting the desktop?

0 Kudos
Ray_handels
Virtuoso
Virtuoso

It is a little bit more complicated than that.

At first you have 3 version of writables and they save different things. In pure basic it is the following

1. Profile only : Only saves the C:\Users folder and all HKCU settings (which is in that folder as ntuser.dat Smiley Happy)

2. UIA only: UIA stands for User Installed Application. It saves everything besides the c:\Users directory

3. UIA + Profile: As the name states, it saves everything.

That being said, the truth is a little bit more complicated. If you look at the writable in option 3, not everything you save locally is automatically saved in the writable. If you look at the writable, there's a snapvol.cfg file. In that file you can add exclusions of files that you do not want to safe. If you look at it you will mostly see folders for virusscanners, Appvolumes itself and other stuff you do not want to safe.

Looking at how it works. When you log in with a writable the svservice (Appvolumes filter driver) checks to see if it needs to register information that you are changing in the machine. If it is excluded (this can be a folder or a process) it will do nothing with that information. If it is included it will safe it to the writable volume which is simply a mount point of a VMDK file. When you log off the disk will be attached but info being saved is written there because it is realtime. The moment you reboot a desktop the Appvolumes agent will detach the writable from the machine for you. Do keep in mind that wriatbles can only be used with a non persistent machine and you need to refresh the machine after log off.

maxman722
Enthusiast
Enthusiast

They are used with a non persistent manner, but if you specify the desktop pool as dedicated, the user's settings should be applied in the same was as they were previously, correct? @Ray_handels

0 Kudos
Ray_handels
Virtuoso
Virtuoso

No not really, the entire idea behing the writable is that you can use a non persistent floating pool that has no dedication towards a specific user, that's the biggest win of using Appvolumes.

The moment you log in to either what machine in the pool during logon your writable volume and apptacks are being attached. Basically your machine is being build up during logon, all applications are being installed by attaching the appstacks, all settings are being deployed through your writable volume.

Do keep in mind that using this technique logintime will be longer than normally if not using Appvolumes.

0 Kudos