For that reason, we recommend using the open command, and rdp:// URLs to launch sessions. This overrides or decreases the effectiveness of many of CoRD strong points, including unified sessions, etc. One symptom of this is multiple Dock icons. Launching CoRD from the command line this way causes a fresh instance of CoRD to be opened. Applications/CoRD.app/Contents/MacOS/CoRD -host -port 3389 -u username Passwords with any special characters in them, :, &, etc need to be encoded according to the URL Encoding FormatĬoRD supports the following command line options: -host -port -u -d -p -a set screen depth -width set screen resolution width -height set screen resolution height

Colons (:) can be used in place of ampersands for the same effect, without needing to be escaped. Open using ampersands (&) from the command line, they have to be escaped with a backslash (). 0 - Forward Audio to the Local Machine (Currently not used since CoRD doesn't present audio).

Open following parameters can be set for the session via a query string (as of 0.5.2): If you want to use rdp:// urls with existing saved servers, you can (as of 0.5.3)! Just use the label in place of a hostname:Īdditional parameters can be used to start a fully-configured session via the URL: If Apple changes this (or if anybody is aware of a way to extend it) we would love to hear about it. Unfortunately, there is no way to extend Finder's 'Connect to Server' dialog, which supports launching VNC URLs, so we can't launch CoRD from there. The CoRD documentation on github lays out how you can use URL encoded parameters to open full-configured RDP sessions.ĬoRD handles rdp:// URLs, which you can use from many places inside OS X. But the free and most excellent CoRD remote desktop client does handle rdp:// links which would let you call it from a launcher of your choice or even via open on the command line.

There is no command line access for the Microsoft Remote Desktop Client.

Apple remote for mac