We are using and RDP file to run an application via Terminal Server on a Windows Server 2008 that uses the command prompt to execute.

We have a short-cut defined in the server's desktop with the font settings (name and size) we would like to use for the command prompt window. If the RDP leads the user to access the server's desktop so they double click in the short-cut, the CMD window obeys the settings (this is standard behaviour).

If we instead have the users activate the remote connection making use of the "start the following program on connection" parameter in the RDP file, the command prompt that automatically runs does not have the settings.

The settings it uses are undesirable. We do not want users having to tinker with properties. Any clue on how to achieve this?


In the first case, console settings are stored in the shortcut itself (inside the .lnk file), so they only apply when that shortcut is clicked. In the second case, the shortcut is not being used – you run the executable directly. Having Windows check all .lnk's in existence is just impractical. But if you run your program this way, and then adjust the font settings, they will be stored in Registry1, tied to the console window's starting title2, and should apply to the program no matter how it is launched (unless they are overriden by a shortcut's settings).

1 The Registry location is HKCU\Console, an user-specific location (but could be deployed automatically using Group Policy).

2 Sometimes it's the window title, but sometimes it's the executable's full path. I'm actually not entirely sure which is used when.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.