![]() ![]() No reboot is required after making these changes. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order - ProviderOrder -ĭefault entries: RDPNP, LanmanWorkstation, web client More information This problem occurs because Windows User Access Control (UAC) treats members of the Administrators group as standard users. Make sure the Network Providers entry has at least the default entries: Network Providers value for RDP might be missing in the registry. To do this, create two script files, and then use one of the workarounds, as appropriate. So your Visual Studio cannot see the P: drive at all, because that mapping is specific to your user. Administrator does not have the drive mappings that your user has. ![]() This is because the mapped drives were created under a login different from the administrator login. On the client Machine: Start - Run - MSTSC - Options - Local Resource - Make sure Disk Drives is selected.Ĭheck Resultant Set of Policy on the machine: Terminal Services Group Policies, under Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Client/Server data redirection - Don't allow drive redirection: shouldn't be enabled. Currently, you can work around this issue by running scripts to automatically reconnect mapped network drive when you log on the device. If you run a process (such as Visual Studio) elevated (as you claim in comments), its not running as your current Windows user, but as Administrator. Reason When User Account Control (UAC) is enabled, if you run a program as Administrator (elevated), you cant see network drives unless a registry setting is changed to allow it. On the Server: Terminal Services Configuration - Connections - RDP-Tcp - Properties - Client Settings: Under Connections - Connect Client Drives at logon is selected. On the Server: Terminal Services Configuration - Connections - RDP-Tcp - Properties - Client Settings: Make sure Drive Mapping option is unchecked under Disable the Following. There are no events in the Event Viewer pertaining to the failure to redirect drives.Moreover, the File Explorer also causes problems for showing up the mapped network drive even if you're using the standard rights. Other devices and resources may be properly redirected. The major reason why your mapped network drive isn't appearing in network locations is User Account Control mostly forbids the mapped network drive from showing on the screen.Local drives aren't redirected in the RDP Session. ![]() You may notice the following symptoms when connecting via Remote Desktop Protocol (RDP) to a Windows Server 2003 or Windows Server 2003 R2 Terminal Server: This article provides a solution to an issue where local drive redirection isn't working in RDP Session.Īpplies to: Windows Server 2003 Original KB number: 2436104 Symptoms ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |