Събитие
Създаване на интелигентни приложения
17.03, 23 ч. - 21.03, 23 ч.
Присъединете се към поредицата срещи, за да изградите мащабируеми AI решения, базирани на реални случаи на употреба с колеги разработчици и експерти.
Регистрирайте се сегаТози браузър вече не се поддържа.
Надстройте до Microsoft Edge, за да се възползвате от най-новите функции, актуализации на защитата и техническа поддръжка.
If you're experiencing problems with your Remote Desktop connection to your dev box, this guide can help you find and fix the issues quickly. Whether it's frequent disconnections, latency, or sign-in problems, we've got solutions that can get you back on track.
Before you begin troubleshooting, ensure you have:
Organizations can set a policy that disconnects dev boxes after a specified length of time.
You might see this message if your organization sets a policy to disconnect idle dev boxes after a specified length of time, and has the single-sign on (SSO) feature enabled. Select Reconnect to access your dev box again.
You might have to close the remote desktop session and connect again.
If you're using a VPN on your client computer or dev box, you might experience network latency. A forced-tunnel VPN, which routes all IP addresses, can increase this latency. Check with your network administrator.
Enabling Windows insider channel in your dev box isn't supported. Upgrading your dev box to a Windows insider build might result in unable to connect to your dev box.
Windows update might take 30 minutes or more to install. If you can't connect to your dev box immediately after Windows update, retry after 15 – 30 minutes.
If you disabled the network connection in your dev box and are unable to connect, wait for up to 4 hours and retry. Our agent periodically checks and re-enable it every 4 hours.
If Teams calls don't work well in your dev box, open the About page in Teams and check that the AVD Media Optimized feature is installed. If this feature isn't installed, or if your dev box is running Windows Enterprise N or KN SKUs, contact your dev box administrator.
If Teams call from dev box can't access a camera or microphone, please go to your local computer, open Settings, navigate to Privacy & security > Camera or Privacy & security > Microphone, make sure it's toggled to On for all Microsoft Teams VDI apps.
If CPU profiling doesn't work on an AMD-based dev box, it's a known Windows issue. To fix it, go to Turn Windows features on or off, uninstall Hyper-V and Virtual Machine Platform, and reboot.
In an AMD-based dev box, enable nested virtualization on a Hyper-V VM by setting Set-VMProcessor -VMName <name> -ExposeVirtualizationExtensions $true
might prevent the Hyper-V VM from booting. To avoid this issue, use Intel based dev box.
When you sign in to dev box via Windows Hello for Business based authentication method and it fails with error code 0x8007013d, it could be due to Windows Hello certificate not properly installed. To fix it, first make sure you remember your password. Run certutil -DeleteHelloContainer
command on your client computer (not your dev box), sign out and log back in.
If you notice display issues like incorrect window scaling, blurry content, or broken screen paint, it might be due to a screen DPI rendering issue. These issues usually happen when using multiple monitors or switching between different physical machines. To fix it, disconnect and reconnect the dev box.
If UDP port 3478 is blocked in your network (for example, on your home router), your Remote Desktop connection might have problems using UDP. For the best experience, keep UDP port 3478 open.
Събитие
Създаване на интелигентни приложения
17.03, 23 ч. - 21.03, 23 ч.
Присъединете се към поредицата срещи, за да изградите мащабируеми AI решения, базирани на реални случаи на употреба с колеги разработчици и експерти.
Регистрирайте се сегаОбучение
Сертифициране
Microsoft Certified: Azure Virtual Desktop Specialty - Certifications
Plan, deliver, manage, and monitor virtual desktop experiences and remote apps on Microsoft Azure for any device.