VPN in Azure Windows Virtual Desktop two different geo environments
Dear All, I have created a lab on Azure to test WVD and have IPSEC VPN connected to my on-premises Lab as the following: on Azure There is 1- DC02 | VirtualNetwork: (VNET01) Location: (East US) 2- WVD Master VM | VirtualNetwork: (VNET01) Location: (East US) 3- FSLogix Server | VirtualNetwork: (VNET02) Location: (East US 2) Due to Azure limitation on cores and CPUs on the same site I had to create FSLogix on a different site and setup Peering between both VNETs which worked fine, however from VNET2 to my On-prem network it didn't work. I tried the gateway transit option but that didn't work either. I tried adding the subnet on my on-premises IPSEC Firewall but didn't work too. What kind of solution is possible to get both networks and get access on my On-premises network? I know I can open a case with MS to expand my usage of resources on the same site but I would like to know if connecting both VNETs to the same VPN is possible or not? Thank you
Environment variables in MSIX package wont be used by AVD session host
Hi, We've been struggling with environment variables in MSIX packages. The package is created with Microsoft's MSIX Packaging Tool and a script was used under capture. Script is adding environment variables as we can see in the virtual registry after the package has been created. Problem is that session host will not use these environment variable keys. The package works, but there's a SSO feature which doesn't work because of the environment variables. If we add them manually on the session host the SSO feature works fine. We have tried the PSF tool using the fix there for environment variables, but once we change the AppxManifest.xml to point to PsfLauncher32.exe it gives the following error on the session host: 16.03.23 15:54:29 Error 403 avd-mgmt-7 error 0x80080207: Failure to get staging session for: \\?\Volume{9dc101d8-0130-4a01-xxxx-a81e0088b390}\applications\xxxx__trsqtdqqj719r. 16.03.23 15:54:29 Error 481 avd-mgmt-7 error 0x80080207: Opening the loose file package from location xxxx__trsqtdqqj719r failed. Any suggestions on what we can try?
