Monday, November 19, 2012

SOLVED! - Cannot Connect to Local Drive on Terminal Server Session

Copying a remote desktop profile file (.RDP) from one PC to another, may not have the local drives available. The reason is strange enough - Microsoft's .RDP file will even recognize your drive "label". By default, if you haven't set a drive label for your local drive, the display name is "Local Disk". However, problem arises if for example you've set your D: labeled as "Data".

Now, you create a .RDP file and copy this file to another PC, with its local D: having no drive label. A user using your given .RDF to connect terminal will lost his local D:, even though both are connecting to the same terminal server using the same .RDP file with the local resource D: checked.

Solution? Standardize your local drive labels, either leave it blank, or set to the same name. Then, when you want to deploy your .RDP file to all your users, the drive label will always match.

For your interest, a .RDP file is JUST A TEXT FILE!! Open it with your notepad and have a look what's actually happening when you save your remote desktop settings to a .RDP file.

Your start to understand what I want to say... Microsoft...

No comments:

Post a Comment