Forum Discussion
WVD with Azure Premium Files and FSLogix cannot connect
I just wanted to write this, to get it out there, possibly to channel frustration but most to see what other techs are doing out there for their WVD deployments that utilize FSLogix and Azure Premium...
The issue was during the Azure Outage: CA - Authentication errors across multiple Microsoft services (Tracking ID LN01-P8Z). Once services were restored, there were 4-5 .vhd profiles that had open file handles on them. The problem was, I could not see those open file handles within Azure Storage Explorer. I ended up having to create a new storage account and use the objectspecific registry settings for FSLogix for the affected users, and route their profiles to the new location. Fortunately I was able to copy their .vhd files from a recent backup over to the new storage location so they didn't' lose everything.
After the fact, I found a really useful powershell command that would have saved me from doing all of this. This is even helpful today, because sometimes we have an issue where users try to sign in but their .vhd profile "is being used by another smb process" even though it's not attached to the host. The commands that I found useful were:
Get-AzStorageFileHandle -Context $storageAcct.Context -ShareName $shareName -Path $filePath followed by Close-AzStorageFileHandle -Context $storageAcct.Context -ShareName $shareName -Path $storagePath -CloseAll
It was failing at first, even through the Azure CLi, but I found I had to whitelist my IP address that was trying to connect through the Azure CLi in the browser . I got that IP address by going to Azure AD sign in logs. Hope this helps someone with future issues.
After the fact, I found a really useful powershell command that would have saved me from doing all of this. This is even helpful today, because sometimes we have an issue where users try to sign in but their .vhd profile "is being used by another smb process" even though it's not attached to the host. The commands that I found useful were:
Get-AzStorageFileHandle -Context $storageAcct.Context -ShareName $shareName -Path $filePath followed by Close-AzStorageFileHandle -Context $storageAcct.Context -ShareName $shareName -Path $storagePath -CloseAll
It was failing at first, even through the Azure CLi, but I found I had to whitelist my IP address that was trying to connect through the Azure CLi in the browser . I got that IP address by going to Azure AD sign in logs. Hope this helps someone with future issues.