Forum Widgets
Latest Discussions
How to update to DesktopVirtualization API v. 2024-04-08-preview or API v. 2024-04-03?
Hello everyone, The information from my side is also not clear. I understand that if ARM templates, Terraform, Bicep, or something similar are not used, it is not necessary, and Microsoft performs that operation transparently. The message is universal, meaning that all customers who have deployed AVD receive it, but they do not know who uses and specifies the API version. For example, when creating an AVD through the Azure portal, you do not specify the API version at any time. If we go to the Resource Provider and look for Microsoft.DesktopVirtualization, we see that the default API cannot be changed and is in version "2privatepreview." Interestingly and crazily enough, even with this default API, if you deploy an AVD, the system chooses an older version. So, if anyone has a clear response from Microsoft or has resolved this, it would be great if they could share it. Regards. At least until Microsoft indicates otherwise, I have conducted several tests in different environments and the result is the same and as follows: I deploy the Hostpool and here we see the Json file of the hostpool, as you can see the API version is 2019-12-10-preview. Now I am going to look inside the parameters used in the deployment and WOW, there we can see that the API used to deploy AVD is the latest one, 24-04-08-preview, which is the one Microsoft indicates to use. The 2019-04-01 is the schema version (another different one). To finish confirming this, we go to Resource Provider and as we see, if we go inside the resource type and select hostpool, we see that the default version that CANNOT be changed is 2022-01-12-preview. But among the eligible versions is the one that has been used for our hostpool deployment, that is, 2024-04-08-preview.Gabriel_NaranjoFeb 17, 2025Copper Contributor17Views0likes1CommentConfigure FSLogix for AVD in Cloud Only Config
Most articles and video's mention AD at some point as a requirement but I saw one Youtube video saying that it's possible with only EntraID? I need instructions on how to get this done with a cloud-only environment. In this article: https://learn.microsoft.com/en-us/fslogix/how-to-configure-profile-container-azure-ad it eventually mentions under the Kerberos steps(3) that a hybrid environment is required...But I don't think it is. Please advise.DanielClaassenFeb 16, 2025Brass Contributor70Views0likes3Commentsan error occurred while accessing this resource
When trying to connect to a remote desktop connection in the Remote Desktop client app i get "an error occurred while accessing this resource." trying from browser (https://client.wvd.microsoft.com/arm/webclient/index.html) is less helpful: I have full owner RBAC on azure as well as the Desktop Virtualization User role i can login to the servers No specific ad join configuration: worth noting, if were to just use RDP to remote onto the server and not use AVD, i have to connect using an azure VPN and login with on-prem AD credentials. When i sign into the AVD platform i am using my entraID credentials.ben-pgFeb 15, 2025Copper Contributor31Views0likes3CommentsWindows App - Uniform Resource Identifier schemes - not supported?
Hi. I have been looking for a way to start a desktop session or remote app using the new Windows App from a users desktop as a shortcut. But I can only find documentation on the Remote Desktop Client for AVD: Uniform Resource Identifier schemes with the Remote Desktop client for Azure Virtual Desktop | Microsoft Learn Has anyone come across a way of accomplish this feature in Windows App? I can use ms-avd:connect?workspaceId=INSERTIDHERE&resourceid=INSERTIDHERE&username=email address removed for privacy reasons&version=0 fine, but it opens Remote Desktop Client for AVD, which I know Windows App uses for connecting to AVD, but it does not open the other assisting apps that Windows App opens then connection via the Windows App UI.Chris_toffer0707Feb 15, 2025Iron Contributor13Views0likes2CommentsTeams addin missing in Classic outlook in Azure virtual desktop
Hello Everyone! We have both classic and new teams installed in our AVD environment, Win11 Multisession. Since we have updated our AVD machines with the new image, we noticed that it does not have the Teams add-in in classic Outlook. We already checked in com-addins, but Teams was not listed there. Do any of you also face the same issue? Can you please help us understand how we can get the Teams Addin back in the classic Outlook? We are using the source image plan "win11-23h2-avd-m365," which has this issue. Please let me know if you need more information. Thank youSolvedDharani_RajFeb 15, 2025Copper Contributor215Views0likes8CommentsCommitted Memory issue
Hi, One of our customers wants to put as many users onto a session host as possible. fair play, i'd most likely want that too. So they have it enough Ram so they could do that. We are hitting a bit of a snag on the Committed memory and not sure how to tackle it. The session host has 64GB memory, but does not seem to be using it all. Instead its filling up the committed memory. When this reaches 100% things start going wrong, FSLogix service crashes and DWM crashes. Has anyone else come across this scenario. We just use the default Azure setting for System Managed onto the temp drive for the page file: Have we set something up wrong? Thanks.KevHalFeb 14, 2025Iron Contributor25Views0likes1CommentAzure Virtual Desktop Portal Bug
Since two days we discovered that in the AVD Portal under the Session hosts register the "VM Resource group" shows the resource group of the hostpool objects and not the actual virtual machines resourcegroup. In addition the "VM Location" is also the location of the hostpool objects and not the location of the virtual machines anymore.denis89Feb 13, 2025Brass Contributor15Views0likes0CommentsMicrosoft Entra ID Greyed Out?
I went to build a new host pool this morning and when I got to the part where I'm normally able to select "Domain to join", the only available option is "Active Directory"? Microsoft Entra ID is greyed out. It's been a month or so since I've built a host pool, and I do notice the interface has changed a bit. Can anyone tell me what I'm doing wrong?knicksonFeb 12, 2025Copper Contributor33Views0likes2CommentsMicrosoft Remote Desktop Client crashes when connecting
Using "newer" versions of the Microsoft Remote Desktop Client (client versions newer than 1.2.29) the msrdc.exe app crashed upon starting the connection to the resource. Version 1.2.29XXX connects just fine but anything newer and it starts having issues. I have only seen this on what seems to be random machines across several different clients/tenants/hostpools making it especially tough to narrow down what the underlying issue is. The subscribe process authenticates successfully and shows the resources in the feed properly but upon launching the Remote Desktop connection the msrdc.exe crashes right away. The only commonality is that i see this event id on all the machines (both win10 and win11 workstations): Faulting application name: msrdc.exe, version: 1.2.4159.0, time stamp: 0x645938cf Faulting module name: ntdll.dll, version: 10.0.22621.1485, time stamp: 0xb7f0154a Exception code: 0xc0000409 Fault offset: 0x00000000000a3346 Faulting process id: 0x0x3554 Faulting application start time: 0x0x1D9844F7F5FB6DF Faulting application path: C:\Program Files\Remote Desktop\msrdc.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 3dd4c0a1-bc99-4a24-a859-b7a5cda39e3b Faulting package full name: Faulting package-relative application ID:pbear25Feb 10, 2025Copper Contributor15KViews1like7Comments
Resources
Tags
- WVD104 Topics
- AVD81 Topics
- AVDUpdate54 Topics
- Azure Virtual Desktop37 Topics
- Windows Virtual Desktop35 Topics
- FSLogix27 Topics
- azure26 Topics
- wvdupdate16 Topics
- Windows Virtual Deskop13 Topics
- Azure Virtual Dekstop11 Topics