![]() The following table lists the differences between each approach in this scenario: Servicing method Typically, servicing happens in one of two ways. Instead, they service the custom image the VMs are based on. The admins don't service non-persistent VMs with things like installing Windows updates because all changes are lost whenever the VM restarts. Non-persistent VMs are provisioned based on a custom image, where multiple VMs are based on the same image. Resolutionįor users to connect to the non-persistent VMs without the error, the VM must have received an X509 certificate. As a result, the VM queries the Remote Desktop licensing server for an X509 certificate. With non-persistent VMs, depending on how you're servicing the VM, this issue may happen each time someone turns it on because its state always resets. This process can take several seconds, during which connections fail and display the error message "The remote session disconnected because there are no Remote Desktop License Servers available." Once the VM receives the X509 certificate, subsequent connections succeed. When the first user tries to connect, the VM queries the Remote Desktop licensing server for an X509 certificate. A Microsoft Remote Desktop Services deployment doesn't natively have the option to use non-persistent VMs. This scenario only applies to third-party VDI providers. While this scenario can happen with both persistent and non-persistent VDIs, it happens most often with the non-persistent VDI, as the VMs for the persistent VDI have connected to the Remote Desktop licensing server during the grace period. The VM has never connected to the Remote Desktop licensing server specified.No license server is required during this time. The 120-day licensing grace period has expired.The Remote Desktop licensing server the VM uses is configured in per-user mode.The Windows VM has the Remote Desktop Session Host (RDSH) role installed.VMs on non-persistent VDI typically use a shared custom image.Ī user sees the error message "The remote session disconnected because there are no Remote Desktop License Servers available." This issue happens if the user is the first one to connect to a VM after it's turned on, and the following conditions are true: Instead, every time you end your session, the VM reverts to its original state and loses any changes. ![]() Non-persistent VDI doesn't keep the changes you make to a VM after you shut down or restart it.Persistent VDI behaves like a physical machine. Persistent VDI keeps the changes you make to a virtual machine after you shut down or restart it.Let's first look at the difference between persistent VDI and non-persistent VDI: ![]() This article explains why this error happens and gives you directions for how to mitigate it. The remote session disconnected because there are no Remote Desktop License Servers available. If you're running a Virtual Desktop Infrastructure (VDI) environment with non-persistent virtual machines (VMs) that connect to a Remote Desktop license server with per-user licensing, you may see an error message the first time a user tries to connect.
0 Comments
Leave a Reply. |