After upgrading to Windows 10, many veteran RDP users discover that the familiar local resource sharing options have either moved or disappeared entirely in the Microsoft Store version of Remote Desktop. Unlike previous versions where you could simply check a box in the connection options, Windows 10 requires additional configuration.

First, ensure your remote server allows drive redirection:

# PowerShell command to check current settings
Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server" -Name "fDisableCdm"

# Enable drive redirection if disabled (requires admin rights)
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server" -Name "fDisableCdm" -Value 0

# Restart service for changes to take effect
Restart-Service -Name TermService -Force

For the modern Remote Desktop app from Microsoft Store:

1. Open Remote Desktop app
2. Click the three-dot menu next to your saved connection
3. Select "Edit"
4. Switch to the "Local Resources" tab
5. Under "More..." button, expand "Drives"
6. Select which local drives to share

If you prefer the classic RDP client (mstsc.exe):

1. Run mstsc.exe
2. Click "Show Options"
3. Navigate to "Local Resources" tab
4. Click "More..." under "Local devices and resources"
5. Expand "Drives" and select the ones to share

For power users who frequently transfer files, consider setting up a persistent configuration via RDP file:

redirectdrives:i:1
redirectprinters:i:1
devicestoredirect:s:*
drivestoredirect:s:*

If drives don't appear after connection:

• Verify Group Policy allows redirection (gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Device and Resource Redirection)
• Check Windows Firewall rules for Remote Desktop (TCP 3389)
• Try connecting with full administrator privileges

For automated deployments, this PowerShell snippet creates an RDP file with drive redirection enabled:

$RDPContent = @"
screen mode id:i:2
use multimon:i:0
desktopwidth:i:1920
desktopheight:i:1080
session bpp:i:32
winposstr:s:0,1,782,232,1812,1032
compression:i:1
keyboardhook:i:2
audiocapturemode:i:0
videoplaybackmode:i:1
connection type:i:7
networkautodetect:i:1
bandwidthautodetect:i:1
displayconnectionbar:i:1
enableworkspacereconnect:i:0
disable wallpaper:i:0
allow font smoothing:i:0
allow desktop composition:i:0
disable full window drag:i:1
disable menu anims:i:1
disable themes:i:0
disable cursor setting:i:0
bitmapcachepersistenable:i:1
full address:s:your.server.address
audiomode:i:0
redirectprinters:i:1
redirectcomports:i:0
redirectsmartcards:i:1
redirectclipboard:i:1
redirectposdevices:i:0
drivestoredirect:s:*
"@

$RDPContent | Out-File -FilePath "C:\path\to\your\custom.rdp" -Encoding ASCII

After migrating from Windows 8.1 to Windows 10, many sysadmins (myself included) were surprised to find the familiar local resource sharing options absent from the new Microsoft Remote Desktop app. Unlike the classic mstsc.exe which had clear checkboxes for drive redirection, the UWP version requires deeper configuration.

Method 1: Using the Classic Remote Desktop Connection (mstsc.exe)

The legacy executable still exists in Windows 10 and provides full functionality:

1. Press Win+R and type "mstsc"
2. Click "Show Options" 
3. Navigate to "Local Resources" tab
4. Under "Local devices and resources", click "More..."
5. Expand "Drives" and select the local drives to share
6. Connect as normal

Method 2: Configuring the New Remote Desktop App

For those preferring the modern interface:

1. Open the Remote Desktop app from Start Menu
2. Click the gear icon (Settings)
3. Select "Connection settings"
4. Scroll to "Local devices and resources"
5. Toggle "Drives" to enable sharing
6. Save and reconnect

After connection, verify the mapping in the remote session's File Explorer. Shared local drives appear under:

\\tsclient\C (for C: drive)
\\tsclient\D (for D: drive)

For frequent connections, automate with PowerShell:

$RDPFile = @"
screen mode id:i:2
use multimon:i:0
desktopwidth:i:1920
desktopheight:i:1080
session bpp:i:32
winposstr:s:0,1,0,0,800,600
compression:i:1
keyboardhook:i:2
audiocapturemode:i:0
videoplaybackmode:i:1
connection type:i:7
networkautodetect:i:1
bandwidthautodetect:i:1
displayconnectionbar:i:1
enableworkspacereconnect:i:0
disable wallpaper:i:0
allow font smoothing:i:0
allow desktop composition:i:0
disable full window drag:i:1
disable menu anims:i:1
disable themes:i:0
disable cursor setting:i:0
bitmapcachepersistenable:i:1
full address:s:your.server.address
audiomode:i:0
redirectprinters:i:1
redirectcomports:i:0
redirectsmartcards:i:0
redirectclipboard:i:1
redirectposdevices:i:0
drivestoredirect:s:C:\;D:\
"@

$RDPFile | Out-File "MyConnection.rdp"

Permission errors often occur when the remote computer's Group Policy restricts drive redirection. Check these policies:

Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Device and Resource Redirection

Connection drops may happen with large file transfers. Adjust these registry settings on the remote host:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations]
"MaxIdleTime"=dword:00000000
"KeepAliveTimeout"=dword:000927c0