New Customers: 50% OFF Your First Month on All VPS Servers & Web Hosting Plans!

How to enable camera and microphone on Windows Server Remote Desktop

Learn how to enable microphone and camera redirection over Remote Desktop Connection to Windows Server 2022. Configure client-side RDP settings, allow redirection in Group Policy, enable microphone privacy permissions, and verify the Windows Audio service is running.

HostworldWindows & remote desktop 3 min read Updated 23 Sep 2026

Enable microphone and camera redirection in Remote Desktop Connection on your computer, then allow them on the Windows Server 2022 host in Group Policy and Windows privacy, and make sure the Windows Audio service is running. Reconnect and your mic will appear as Remote Audio and your camera will be available inside the session.

Before you start

  • Use a Windows 10 client that is version 1803 or later for webcam redirection. Windows Server 2022 on the host side is supported.
  • Connect with a standard RDP session, not an /admin session.
  • Sign in to the server with an account that can edit local Group Policy.

Step 1: Enable mic and camera in Remote Desktop Connection on your PC

  1. Open Remote Desktop Connection (mstsc.exe), select Show Options, then go to Local Resources.
  2. Select Remote audio, then Settings. Set Remote audio recording to Record from this computer. This tells RDP to send your local microphone into the server session.
  3. Select More…, expand Video capture devices, and tick your camera. This enables RDP’s webcam redirection for the chosen device.
  4. If you are opening an .rdp file after the April 2026 updates, approve the new security prompts for microphone and camera at connect time. Unsigned .rdp files will not remember these choices, so you may need to re-approve on each connection.

Step 2: Allow redirection on the Windows Server 2022 VM

  1. Open Local Group Policy Editor on the server. Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection.
  2. Microphone: open Allow audio recording redirection and set it to Enabled. The host’s policy overrides the client request, so this must allow recording.
  3. Camera: open Do not allow video capture redirection and set it to Disabled, or leave it Not Configured. Either state permits camera redirection.
  4. Sign out of the RDP session and reconnect so policy changes apply.

Step 3: Permit the mic in Windows privacy and start Windows Audio

  1. In the server session, go to Settings > Privacy & security > Microphone. Turn on Microphone access and Allow desktop apps to access your microphone.
  2. Ensure the Windows Audio service is running and set to Automatic. If there is no Remote Audio playback or microphone device inside the session, start this service.

Step 4: Test inside the remote session

  1. Open the Windows Camera app in the server session to confirm the webcam stream arrives over RDP.
  2. In your voice app, select the Remote Audio microphone. If it is missing, return to Step 3.

If it does not work

  • Client settings not applied: recheck Step 1. In mstsc.exe you must set Remote audio recording to Record from this computer and tick your camera under Video capture devices. If you launch from an .rdp file after the April 2026 update, accept the new security prompts for camera and microphone at each connect unless the file is signed.
  • Host is blocking redirection: on the server, ensure Allow audio recording redirection is Enabled and Do not allow video capture redirection is Disabled or Not Configured. Avoid connecting with /admin because it can suppress client-experience features like audio-in.
  • Privacy or services: in the server session, turn on the microphone privacy toggles under Settings > Privacy & security > Microphone and ensure the Windows Audio service is running. If you are using a virtual camera on your PC, it will not redirect. Test with a physical webcam and the Windows Camera app.

If you have worked through the above and mic or camera still do not appear, some environments only succeed once the Remote Desktop Session Host role is installed and correctly licensed. This change affects how users connect and introduces licensing requirements. Plan first and open a support ticket so we can review your server and advise.

What next

For a fuller explanation of audio and video redirection, policy control, and the April 2026 security changes, see our VPS articles in our VPS guides. We keep Windows Server how‑tos and troubleshooting checklists together under our VPS guides for easy reference.

Common questions

What Windows 10 version do I need for webcam redirection in Remote Desktop?

You need Windows 10 version 1803 or later for webcam redirection to work with Remote Desktop Connection.

Why is my microphone not appearing in the remote session?

Check that you set Remote audio recording to Record from this computer in RDP settings, that Allow audio recording redirection is Enabled in Group Policy, and that microphone access is turned on in the server's privacy settings. Also ensure the Windows Audio service is running.

Can I use a virtual camera for Remote Desktop redirection?

No. Virtual cameras do not redirect over RDP. You must test with a physical webcam and the Windows Camera app.

Do I need to reconnect after changing Group Policy settings?

Yes. You must sign out of the RDP session and reconnect for Group Policy changes to apply.

What should I do if I see new security prompts when opening an RDP file after April 2026?

If the RDP file is unsigned, approve the new security prompts for microphone and camera at each connection. Signed RDP files will remember these choices.

Was this article helpful?