HermiM88's Posts

Hi, We are using VMware horizon version 8. All our view pools are automated instant clone pool. Some of these pools are configured as "floating" and some as "dedicated". For dedicated view pools we have 2 configuration for the setting "refresh OS Disk after logoff" either "always" or "every 7 days" In Horizon 8 documentation it is saying that all instant clone VMs will be deleted and recreated once a user log off does not matter what type of desktop pool you are using. I am not able to understand this concept. I thought that for dedicated pool a complete delete and recreation of instant clone VM is not logical since at least user assignment will be lost and this is why I thought that dedicated VMs have always the "base-snapshot" which refer to the first time the VM was created and every time a user logoff or an administrator starts "recover" operation from horizon administrator console, VMs will just revert to the initial snapshot. It seems this is not the case and based on the setting "refresh OS Disk after logoff"  there are 2 different processing (I tried to capture operations on vCenter side). Please see attachment as described below : dedicated pool (refresh OS Disk after logoff = every 7 days) : attachment name = dedicated_every7_Days.jpg dedicated pool (refresh OS Disk after logoff = always) : attachment name  = dedicated_always.jpg   on a floating pool it looks logical for me. In fact, the existing VM will be deleted, new VM can be created or not depends on how provisioning settings on the pool is configured (on-demand VMs, max VMs, spare VMs). if new VM needs to be created a linked clone VM will be created and linked to the replica (parent VM) and from the parent VM new VM will be created (see attachment : floating.jpg)   My questions are : what's the logic behind the automatic refresh? why some floating VM has the "base-snapshot"?   Thanks in advance  

Hi, Some information about our VDI environment : VMware horizon 8.8.0 build - 21073894 (2212) APP VOLUMES 4, VERSION 2212 (4.9.0.41) We have couple non-persistent VM pools (instant clone). on one of them we are using UIA Writable volume to provide persistence to some users who needs to keep some application settings and some data (when a WV is attached and during first utilisation users are using a script to configure a development environment which will copy files and folders to C:\<folder name>.). All pools have hybrid Azure AD join working just fine except the one with writable volume. Disabling the WV, so it will not get attached during instant clone VM startup (since it is assigned per computer not per user), caused the same VM to be hybrid Azure AD joined. Please note that I am checking hybrid AAD join status by using dsregcmd.exe /status Please be aware that VMS within the affected pool have one application package, one UIA WV and FSLogix profile container attached to them. As described above the issue is not showing up when the application package and FSLogix profile container is attached (without UIA WV) I have been trying to troubleshoot the issue since couple days and I am really stuck right now and your support is more than needed. I don't understand what's going to be redirected to the writable volumes which can cause hybrid AAD join to fail.