The issue you're encountering is very common and stems from a fundamental limitation of Windows Server operating systems when accessed via standard Remote Desktop Protocol (RDP).
For your microphone to work, your VPS must be running a Windows client OS (like Windows 10 or 11). If it's running a Windows Server OS (like Server 2019, 2022, 2025), you will need an extra, more complex step that is often not practical for a single user.
Here is the step-by-step guide to diagnosing and fixing the problem.
Step 1: Identify Your VPS Operating System
First, you need to know what version of Windows your VPS is running.
-
Right-click on the "Start" button on your VPS and select "System" .
-
Look for "Windows Edition" . It will say either "Windows Server" or "Windows 10/11".
This single piece of information determines the entire solution.
Step 2: Configure Your Local RDP Client (This is always required)
For microphone redirection to work, you must enable it in the Remote Desktop Connection client on the computer you are using to connect.
-
Open Remote Desktop Connection (search for mstsc in the Windows Start Menu).
-
Click on "Show Options" to expand the menu.
-
Go to the "Local Resources" tab.
-
In the "Remote audio" section, click the "Settings..." button.
-
In the new window, under "Remote audio recording" , select "Record from this computer" .
-
Click "OK" and then "Connect" to your VPS.
Step 3: Apply the Fix Based on Your OS
If Your VPS is Windows 10 or 11 (Client OS)
This is the easier scenario. You just need to enable the correct settings on the VPS itself.
-
Check Privacy Settings: On your VPS, go to Start > Settings > Privacy & security > Microphone.
-
Ensure "Microphone access" and "Let apps access your microphone" are turned On.
-
-
Run the Audio Troubleshooter: Go to Start > Settings > System > Troubleshoot > Other troubleshooters. Run the "Recording Audio" troubleshooter.
Your microphone should now appear as "Remote Audio" in the VPS's sound settings.
If Your VPS is Windows Server (The "Advanced" Scenario)
This is the most likely cause of your problem.
By default, a standard Windows Server installation does not support microphone redirection. It requires an additional, complex role called Remote Desktop Session Host (RDSH) .
Enabling this role is technical and has important licensing consequences:
-
Licensing Requirement: Installing RDSH requires Remote Desktop Services Client Access Licenses (RDS CALs) , which must be purchased from Microsoft.
-
Temporary Grace Period: You can install the role and it will work for a 120-day "grace period" without a license. After that, it will stop functioning unless you purchase the proper CALs.
If you want to proceed with this route for testing, the process is as follows:
-
On the VPS, open Server Manager -> Manage -> Add Roles and Features.
-
Proceed through the wizard until you reach "Server Roles" .
-
Expand "Remote Desktop Services" and check the box for "Remote Desktop Session Host" .
-
Complete the installation and restart your VPS.
Alternative Solutions to Avoid Complexity
If adding the RDSH role to a Windows Server VPS seems like too much trouble, here are two effective alternatives:
-
Use a Different Remote Access Tool: Third-party tools like TeamViewer, AnyDesk, or Parsec handle audio differently than Microsoft RDP. They often support microphone passthrough without any special configuration on the remote server.
-
Reinstall Your VPS with a Client OS: If possible, the cleanest solution is to rebuild your VPS using a Windows 10 or Windows 11 image. These are designed for direct interaction and will support your microphone with the simple steps in the first solution.
I hope this helps you get it working. If you find out your VPS is running Windows Server and decide to try the RDSH role, let me know if you run into any issues during the setup.
