Note: Enabling microphone and camera redirection via standard RDP is a feature only possible on our dedicated server offerings at this time. If you're on a shared VPS plan, or if RDP redirection isn't working reliably, see the Parsec Workaround section below.
Local Machine Setup
1. Connect and Test Devices
Plug in your webcam and microphone.
Open the Camera app to ensure the webcam is working.
Visit https://mictests.com to verify microphone functionality.
2. Adjust Privacy Settings
Camera Privacy: Enable access for Desktop App Web Viewer (also enable "More" if shown).
Microphone Privacy: Do the same — enable Desktop App Web Viewer.
Ensure the specific apps you plan to use (e.g., Zoom, Teams) are allowed access.
Remote Desktop Configuration
1. Launch Remote Desktop Connection
Open the Remote Desktop Connection (RDP) app on your PC.
Click Show Options in the bottom-left corner.
2. Enable Audio and Video Redirection
Go to the Local Resources tab.
Under Remote audio, click Settings and choose:
"Record from this computer" for microphone redirection.
Back under Local Resources, click More…
Under Local devices and resources, check Video capture devices.
Click OK, then Connect to launch the session.
Server-Side Configuration (Windows Server 2019/2022/2025)
1. Install Remote Desktop Services
Open PowerShell as Administrator on the VPS and run:
Install-WindowsFeature -Name RDS-RD-Server, RDS-Licensing -IncludeManagementTools -Restart
This installs both the Remote Desktop Session Host role (which enables microphone and webcam redirection) and the RD Licensing role (which is needed to activate CALs in the next steps). The VPS will reboot automatically when the install completes.
⚠️ Important — 120-Day Grace Period: Installing Remote Desktop Services starts a 120-day trial period. After this expires, Remote Desktop connections will stop working until a valid RDS CAL (Client Access License) is installed. To avoid disruption, complete the licensing steps below.
2. Activate the License Server
After the VPS reboots and you're reconnected:
Open Remote Desktop Licensing Manager (Start menu → search "licensing" or run
licmgr.exe).Right-click your server name → Activate Server.
Connection method: Automatic connection (recommended).
Fill in the company information (name, company, country are required — other fields optional).
Click through the wizard until you see "License server activated successfully".
3. Install Your RDS CALs
When prompted at the end of activation, choose Install Licenses Now (or right-click your server → Install Licenseslater).
License Program: Select License Pack (Retail Purchase) for reseller/standard keys, or choose the program matching your purchase (Open License, Enterprise Agreement, etc.).
Enter your 25-character CAL product key (format:
XXXXX-XXXXX-XXXXX-XXXXX-XXXXX).Confirm the product details:
Product version: Windows Server 2022 (or matching your OS)
License type: Per User (recommended) or Per Device (matching what you purchased)
Quantity: Matches what you purchased
Complete the wizard.
4. Configure RDSH to Use the License Server
Open PowerShell as Administrator and run:
# Point RDSH at the local license server $ts = Get-WmiObject -Namespace "Root/CIMV2/TerminalServices" -Class "Win32_TerminalServiceSetting" $ts.SetSpecifiedLicenseServerList("localhost") # Set licensing mode to match the CALs you purchased: # 4 = Per User CALs # 2 = Per Device CALs $ts.ChangeMode(4)About Per User vs. Per Device: RDS CALs come in two types. Per User CALs allow one named user to connect from any number of devices. Per Device CALs allow any user to connect from one specific device. If you bought Per User CALs, use ChangeMode(4). If you bought Per Device CALs, use ChangeMode(2) instead. The licensing mode set here must match the CAL type you installed in Step 3, or RDSH won't be able to issue licenses.
5. Verify Licensing Is Working
Open the RD Licensing Diagnoser (Start menu → search "RD Licensing Diagnoser" or run lsdiag.msc).
A healthy configuration will show:
✅ Green check: "RD Licensing Diagnoser did not identify any licensing problems"
✅ Number of licenses available for clients: matches your purchased quantity
✅ License server connectivity: Available
✅ Credentials: Available
If you see warnings or red X's, the diagnoser will explain what needs fixing — the most common issue is forgetting to install CALs after activating the license server.
Testing the Webcam on the VPS
After rebooting, open the Camera app on the VPS.
You should now see the live video feed from your redirected webcam.
Confirm microphone redirection by testing in your chosen communication app or visiting https://mictests.com from the VPS.
🎥 Parsec Workaround (Alternative to RDP Redirection)
If standard RDP redirection isn't an option on your plan, or you want a smoother low-latency experience, Parsec is a reliable workaround. Parsec streams your local webcam and microphone into the VPS session as native devices.
Step 1: Install Parsec on Both Machines
Download Parsec from https://parsec.app on both your local machine and your VPS.
Install and sign in with the same Parsec account on both.
On the VPS, install Parsec for Teams (or enable the Host role) so the VPS can accept incoming connections.
Step 2: Enable Microphone Permissions on the VPS
Once connected via Parsec, the VPS still needs Windows to allow apps to use the microphone. On the VPS, go to Settings → Privacy → Microphone and confirm the following are enabled:
"Allow apps to access your microphone" → toggled On
Under "Choose which Microsoft Store apps can access your microphone":
Desktop App Web Viewer → On
TradingView (or any other app you intend to use) → On
Also scroll down to the "Allow desktop apps to access your microphone" section and make sure it's enabled — this is what allows non-Store apps (Zoom, OBS, Discord, etc.) to capture audio.
Note: The microphone itself passes through Parsec natively — no extra software needed on your local machine for mic input.
Step 3: Install VB-CABLE for VPS Audio Playback
The microphone works out of the box with Parsec, but outbound audio from the VPS (music, video sound, app alerts, TradingView notifications, etc.) won't reach your local speakers by default on Windows Server. To fix this, install VB-CABLE on the VPS.
On the VPS, download VB-CABLE from https://vb-audio.com/Cable/.
Extract the ZIP and run VBCABLE_Setup_x64.exe as Administrator.
Click Install Driver and reboot the VPS when prompted.
After reboot, reconnect via Parsec and open Sound Settings on the VPS:
Under Output, set CABLE Input (VB-Audio Virtual Cable) as the default playback device.
Under Input, this creates a matching CABLE Output device.
In Parsec on the VPS (Host settings), make sure CABLE Output is selected as the audio source Parsec streams to your local machine — or set CABLE Input as the system default and Parsec will pick it up automatically.
Audio playing on the VPS (YouTube, music, alerts) will now route through VB-CABLE and stream down to your local speakers via Parsec.
Tip: If you need to hear VPS audio and have a specific app output somewhere else, VB-Audio also offers VoiceMeeter for more advanced routing.
Step 4: Enable Webcam in Parsec
In the Parsec client on your local machine, open Settings → Host (when hosting from the VPS).
Make sure Webcam Streaming is enabled if your Parsec plan supports it. Otherwise, use a third-party tool like OBS Virtual Camera locally and stream it through Parsec as your screen source.
On the VPS, open the Camera app or your communication app — your local webcam feed should now be available.
Step 5: Test Everything
Webcam: Open the Camera app on the VPS or join a test meeting in Zoom/Teams.
Microphone: Visit https://mictests.com from inside the VPS Parsec session, or run a test call.
VPS audio: Play a YouTube video or some music on the VPS — you should hear it through your local speakers.
🤝 Need Assistance?
If any part of the setup feels unclear, the QuantVPS team is happy to help. If you'd like us to verify your environment from our side, feel free to open a support ticket and get connected with the team: https://www.quantvps.com/