Hey.
Also a small note here. Writables only work with VDI, not with RDSH so you can skipp that part. What it does is it attached a disk that is read/write and all changes ae being saved to this disk. The Appvolumes filter driver then merges it with the machine as if you are using a local machine. Writable is always attached to either a user or a machine. You can however exclude very specific information from what appvolumes should store on the writable.
Does app volume saves all users data (downloads,copied files,....) in any folders of RDSH pool and user profile?
If you do not redirect that information yes it will. I will always suggest to redirect Downloads, Pictures and Documents, do NOT let than land in a writable.
Does app volume migrate profile and files of a user that before assigning writable volume logged on locally ?
No it will not. The first time a user attaches a writable to his or her VDI when logging in that's the moment it starts to build up the writable. If you disable the writable the user can log into a complete fresh machine.
Does writable volumes works good for profile?
Depends on what you try to achieve. If you are only worried about specific parts of the profile I'd suggest going with DEM. If you need everything (and i really mean everything) than writables could be an option for you.
