When the users log in the VDI interface, they were facing slowness of up to 30-40 minutes where ideally it should not take more than a few seconds.
These issues are observed if there has been a patch update done inside the guest OS after which there was a latency peak observed.
Microsoft logs will show latency observed when querying the volume as shown below:
[20:34:42.839][tid:00001298.0000129c][INFO] Volume attach event[20:34:42.839][tid:00001298.00002c9c][INFO] VHD(x) GetVirtualDiskPhysicalPath request returning after 0 milliseconds[20:34:42.839][tid:00001298.00002c9c][INFO] VHD(x) FindFirstVolume request returning after 0 milliseconds[20:51:20.301][tid:00001298.00002c9c][INFO] VHD(x) loop through volumes returning after 997469 milliseconds, volumes tested: 2[20:51:20.301][tid:00001298.00002c9c][INFO] VHD(x) getVolumeGUIDFromPhysicalPath request returning after 997469 milliseconds
VMware vSAN 7.x
VMware vSAN 8.x
This issue can occur if there has been a Data loss prevention (DLP) utility upgrade done at the client side.
There is an issue identified with the DLP application on the client machine which was patched after which there is a metadata scan occurring.
Due to this scan operation, the users were facing latency when logging in.
The same has to be identified by the customer or the application vendor in DLP logs.
Work with the Guest OS vendor (Microsoft) and revert the DLP version to the previous working version (24.04.5677).
The user login will work normally after that.
More information about the Microsoft level logging are shared in the below link: