Ask Aresh

If you have a VMware VSAN environment and you wanted to export a App Volumes - Writable Volumes from the vsanDatastore to another datastore, storage or for VMware GSS/R&D for further analysis go ahead and read further! Background – The traditional way of exporting the Writable Volumes from the source vsanDatastore was to attach the *. vmdk to a dummy VM as a “ Existing Hard Disk ” and export the dummy VM using the “ Export OVF Template ” option from the vCenter. Repeat all the steps on target datastore where-in it needs to be imported. However, if you want an alternate and easy method than the dummy VM then follow the below steps. Step by Step Instructions: -- SSH to any ESXi Host Resource Cluster where the WV is stored and browser to the cloudvolumes/writable directory location : # cd /vmfs/volumes/vsanDatastore/cloudvolumes/writable (This is the location where all end-user writable volumes are stored) -- Now search for the end-user (E.g twood) for which you want to exp...

In your Virtual Desktop Infrastructure with the following configurations: Horizon 7.x – Floating Desktop Pool App Volumes 2.x – Writable Volumes UIA+Profile McAfee Agent 5.x and McAfee VSE 8.x in your Master Image If you start noticing 100 % -   CPU Usage   for prolonged period of time and the Horizon Session getting disconnected from time to time after launch then you might need to include the following exclusion within your Writable Volumes (UIA+Profile) snapvol.cfg file: #McAfeeExclusion exclude_process_path=\Program Files\Common Files\McAfee\SystemCore My colleague Daniel Bakshi has written an extensive blogpost on how to modify the snapvol.cfg for individual or group of end-users please reference it to make the necessary changes - Using the VMware App Volumes snapvol.cfg File to Customize Writable Volumes I hope you will find these exclusion useful and will help you resolve a similar issue a lot quicker. A big thanks to Art Rothstein in helping to troubleshoot and...

If you have a VMware VSAN environment and you wanted to capture a memory dump of the Virtual Machine for debugging or want to provide memory.dmp to VMware GSS or R&D for further analysis go ahead and read further! Use Case – In our scenario had a few VDI Desktops running Windows 10 1607 + Horizon 7.3.1 + App Volumes Writable Volumes 2.13.1 + UEM 9.2.1 that were getting into unresponsive state. As a last resort we wanted to capture the memory dump to find out more what is causing the VM to get unresponsive. Step by Step Instructions: -- Using the vCenter console select the Virtual Machine VM – Power – Suspend -- This will create the *.vmss and *.vmem file for Debugging. (Note the *.vmem file is applicable for ESXi 6.0 onwards) -- Make a note of the ESXi host Name/IP for the VM is in Suspend state -- SSH to the ESXi Host and browser to the VM Directory location : # cd /vmfs/volumes/vsanDatastore/od-av-troub-1 (Where “od-av-troub-1” is the VM name) -- Now lets op...