ActivityId: f1bc4c92-2ae4-4cdd-adbc-84bb19029995 Error: The MSIX Application metadata expand request failed on all Session Hosts that it was sent to. Session Host: servername, Error: Error accessing virtual disk at ≤\\storagename\sharename\Zoom.vhd≥. (Code: 400)
Forum Discussion
MSIX app attach Azure portal integration public preview
MSIX app attach is an application layering solution that allows you to dynamically attach an application (that is an MSIX package) to a user session. Separating the application from the operating sys...
I actaully posted this question in another forum and got som answers you might find usefull, ill attach screenshot....
I have the same issue.
Stefan can you provide exact instructions for how we achieve this on AAD DS? I used SAS Key connection to the share as you alluded to:
$connectTestResult = Test-NetConnection -ComputerName synfslogix.file.core.windows.net -Port 445
if ($connectTestResult.TcpTestSucceeded) {
# Save the password so the drive will persist on reboot
cmd.exe /C "cmdkey /add:`"synfslogix.file.core.windows.net`" /user:`"Azure\synfslogix`" /pass:`"SASKEY`""
# Mount the drive
New-PSDrive -Name Z -PSProvider FileSystem -Root "\\synfslogix.file.core.windows.net\sharename" -Persist
} else {
Write-Error -Message "Unable to reach the Azure storage account via port 445. Check to make sure your organization or ISP is not blocking port 445, or use Azure P2S VPN, Azure S2S VPN, or Express Route to tunnel SMB traffic over a different port."
}
I still have issues where it cannot connect despite all permissions being added.
I'm open to doing it in other ways that you guys may suggest.
So basically, I ran ICACLS to mount the drive e.g.:
net use Z: \\storagename\sharename /user:Azure\synfslogix SASKEY
Then I used ICACLS to grant read access to the VHD:
icacls Z:\Zoom.vhd /grant computername:(r)
Those commands said they're successful, but I still get:
- Looking at teh code closer it seems you have the computer account access the the map shared via z? What are the permissions on the Z file share
Stefan Georgiev I'm guessing you're referring to doing this?
$connectTestResult = Test-NetConnection -ComputerName SHARENAME.file.core.windows.net -Port 445 if ($connectTestResult.TcpTestSucceeded) { # Save the password so the drive will persist on reboot cmd.exe /C "cmdkey /add:`"synfslogix.file.core.windows.net`" /user:`"SYNTEREX\COMPUTERNAME`" /pass:`"SASKEY`"" # Mount the drive New-PSDrive -Name Z -PSProvider FileSystem -Root "\\SHARENAME.file.core.windows.net\FOLDERNAME" -Persist } else { Write-Error -Message "Unable to reach the Azure storage account via port 445. Check to make sure your organization or ISP is not blocking port 445, or use Azure P2S VPN, Azure S2S VPN, or Express Route to tunnel SMB traffic over a different port." }mobilejon Once mapped did you grant ntfs permissions to the machine accounts?
