How to Configure Windows Server 2016 Remote Desktop Disk Redirection
Remote Desktop Disk Redirection is a feature within Remote Desktop Services (RDS) that allows local drives on a client machine to appear as mapped drives inside a Remote Desktop session. This means users can access files on their local computer from within the remote session without needing to copy files back and forth. Windows Server 2016 supports granular control over this functionality through Group Policy and Remote Desktop Session Host configuration tools.
When disk redirection is enabled, any drives connected to the client — including hard drives, USB flash drives, optical drives, and card readers — can be made available in the remote session under the “This PC” section in File Explorer. This is particularly useful in enterprise environments where users work remotely but need to access documents stored on their local machines.
Prerequisites
Before configuring disk redirection, ensure the following conditions are met on your Windows Server 2016 environment:
The Remote Desktop Session Host (RDSH) role must be installed. The Remote Desktop Services role services must be properly configured. You need administrative access to both the server and the Group Policy Management Console. Client machines must be running a version of the Remote Desktop Protocol (RDP) client that supports drive redirection, which is RDP version 5.1 or later.
Step 1: Open Remote Desktop Session Host Configuration
The first step is to verify the RD Session Host is properly installed. Open Server Manager and confirm the Remote Desktop Services role is present.
Get-WindowsFeature -Name RDS-RD-ServerIf not installed, add it with the following command:
Install-WindowsFeature -Name RDS-RD-Server -IncludeManagementToolsStep 2: Configure Disk Redirection via Group Policy
Group Policy is the primary mechanism for controlling which devices are redirected in a Remote Desktop session. Open the Group Policy Management Console (GPMC) and navigate to or create a GPO linked to the OU containing your RD Session Host servers.
Navigate to the following path within the GPO:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource RedirectionLocate the policy setting named “Do not allow drive redirection”. To enable disk redirection, this setting should be set to “Disabled” (which allows redirection). If the policy is set to “Enabled”, all drive redirection will be blocked.
Step 3: Apply and Test the Policy
After configuring the GPO, force a policy update on the RD Session Host server to apply the changes immediately:
gpupdate /forceVerify the policy applied correctly by checking the resultant set of policy:
gpresult /H C:GPReport.htmlOpen the generated report in a browser and look for the drive redirection policy under Computer Settings.
Step 4: Configure RDP Client Settings
On the client side, disk redirection must also be enabled in the Remote Desktop Connection client. Open the Remote Desktop Connection application and click “Show Options”. Navigate to the “Local Resources” tab and click “More…” under the Local devices and resources section. Check the boxes next to “Drives” and any specific drive categories you want to redirect.
Alternatively, you can configure this through an RDP file. Add the following lines to an .rdp configuration file:
drivestoredirect:s:*The asterisk means all drives will be redirected. You can also specify individual drives by letter:
drivestoredirect:s:C:;D:;Step 5: Verify Disk Redirection in Session
Connect to the Remote Desktop Session Host using the configured RDP client. Once logged in, open File Explorer and look under “This PC”. You should see a section labeled “Redirected drives and folders” containing the local drives from the client machine. These drives will typically appear with the client computer name appended, for example “C on CLIENTPC”.
You can also verify redirection from the command line within the session:
net useThis will list all network connections including redirected drives, which appear as tsclient shares.
Step 6: Restrict Specific Drive Types
In some environments, you may want to allow access to fixed drives but prevent USB or removable drive redirection for security reasons. This can be controlled through additional Group Policy settings in the same Device and Resource Redirection section. Enable the policy “Do not allow supported Plug and Play device redirection” to block removable storage while still allowing fixed disk access.
Use PowerShell to audit which drives are currently being redirected for connected sessions:
Get-RDUserSession -ConnectionBroker rdcb.domain.local | Select-Object UserName, HostServer, SessionIdTroubleshooting
If drives are not appearing in the remote session, check the following: Verify the Group Policy is correctly applied using gpresult. Confirm the RDP client has drive redirection enabled in Local Resources. Check Windows Firewall rules are not blocking RDP device redirection traffic. Ensure the user account has not been restricted from device redirection through user-level policies. Review the Remote Desktop Services event logs in Event Viewer under Applications and Services Logs for any redirection-related errors.
Get-EventLog -LogName "Microsoft-Windows-TerminalServices-LocalSessionManager/Operational" -Newest 50Properly configured disk redirection significantly improves the remote working experience on Windows Server 2016 by giving users seamless access to their local files within the remote session environment.
