Rob Eberhardt

Tuesday, May 03, 2005

Microsoft currently has two official RDP clients: Remote Desktop Client (built-in to Windows XP Pro, and downloadable for nearly anything else), and the Remote Desktops MMC snapin (from the Windows 2003 Administration Tools Pack).

They have all the right features between them, but neither has all of them in one place. The Remote Desktop Client has the most options, but can't connect to console session (aka "session 0") and is meant for one remote connection at a time. The Remote Desktops Snap-in can do these two things, but is missing tons of other options, plus one especially dumb limitation: It can't connect to a port other than standard 3389. (It gives an error “The server name cannot contain the following characters: spaces, tabs , ; : " < > * + = \ | ? ,” -- Another over-zealous coder under-thinking his validation logic!)

Update:
Microsoft says the Remote Desktop Client can connect to the console session, via a command-line switch. Not sure why it's not a checkbox on the options dialog ~~, but it doesn't work for me anyway. It removes the %sessionname% environment variable, but Terminal Services Manager still shows the session is a "RDP-TCP#" name. Oh well.~~ (turns out the console session has to already be logged in).

Something else I found: you can't connect to the console remotely with a non-admin account -- it gives you an error that "To log on to this remote console session, you must have administrative permissions on this computer."

The standalone Client is best when you're working in-depth on one remote machine. The Snap-in is better for when you're working lightly on several machines, and don't need the extra options. In daily use, I usually find myself switching between the Snap-in and the Client. It's a small but constant pain.

This is all to say that I just found Royal TS from code4ward, which is a free, open-source (C#) app, which attempts to combine the best of both programs. (It's like the Snap-in interface, but on steroids.)

I've been using it for a few days, and it's very good. I only wish it could do a better full-screen, or use less screen real-estate with the embedded view. I may try my hand at C# just to hack it up.

Hm, the author's site is down now. Hopefully it's temporary. Meanwhile, here is is on Snapfiles: http://www.snapfiles.com/get/royalts.html

tools/tips/hacks

5/3/2005 3:46 PM Eastern Daylight Time

Disclaimer | Comments [31] |

8/23/2006 11:20:23 PM (Eastern Daylight Time, UTC-04:00)

If all you need is a console session I recommend rclient:
 
 <a target="_new" href="http://www.netadmintools.com/art14.html">http://www.netadmintools.com/art14.html</a>
 
 I know it sounds really ancient (the original version came with the NT 4.0 reskit) but it really works. And, really, how hard can this console stuff be? ;)
 
 If you can't locate a copy (look in the win2k resource kit), email me and I'll send it to you. It can be installed remotely as long as you have an admin account on the target machine.

Jeff Atwood |Jeff Atwood

8/23/2006 11:20:23 PM (Eastern Daylight Time, UTC-04:00)

Thanks Jeff, I hadn't seen this before. This Console looks like the command-prompt aka DOS-prompt, which is unrelated to Remote Desktop's "Console Session". It's confusing that Microsoft reused that name.
 
 Remote Desktop's Console Session is also known as "Session 0", and is normally only given to local users (using the physical keyboard and mouse). It normally shouldn't matter which session you get, but it's a handy option if you start working locally and need to later reconnect remotely to the same session to finish a task.
 
 According to <a target="_new" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;278845">http://support.microsoft.com/default.aspx?scid=kb;en-us;278845</a>, this actually is possible with the standard Remote Desktop Client, using a command-line-only switch "/console". So far I can't get it to work, and it's a bit inconvenient anyway.

Rob Eberhardt |Rob Eberhardt

8/23/2006 11:20:23 PM (Eastern Daylight Time, UTC-04:00)

"According to <a target="_new" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;278845">http://support.microsoft.com/default.aspx?scid=kb;en-us;278845</a>, this actually is possible with the standard Remote Desktop Client, using a command-line-only switch "/console". So far I can't get it to work, and it's a bit inconvenient anyway."
 
 This does work when you are connecting to a Windows Server 2003 system. I tested it with a couple of mine. It does not work when you are connecting to a Win2K server. Thanks for that tip, I never knew you could take control of the server session. Nice.
 
 -Mike

Mike Butler |Mike Butler

8/23/2006 11:20:23 PM (Eastern Daylight Time, UTC-04:00)

Thanks to Mike for help with this.
 
 We did figure it out: The console session has to already be logged in. Otherwise it just doles out another "RDP-TCP#xx" type session.
 
 It'd be nice if they gave some error/warning/prompt so you know you're not actually getting the console.
 
 One way it could be a problem: If I want to START working on something remotely, and FINISH it locally. I'd use the /console switch, start my stuff, sit down later to finish and wouldn't be able to get to it, because /console wouldn't have worked.

Rob Eberhardt |Rob Eberhardt

8/23/2006 11:20:23 PM (Eastern Daylight Time, UTC-04:00)

Rob Eberhardt |Rob Eberhardt

8/23/2006 11:20:23 PM (Eastern Daylight Time, UTC-04:00)

Rob Eberhardt |Rob Eberhardt

8/23/2006 11:20:24 PM (Eastern Daylight Time, UTC-04:00)

Hi, there is another client you can try - "iShadow Desktop":
 <a target="_new" href="http://www.ishadow.com/Downloads/Betas/tabid/88/Default.aspx">http://www.ishadow.com/Downloads/Betas/tabid/88/Default.aspx</a>
 
 This client supports both Microsoft <a title="" href="" ><acronym title="Remote Desktop Protocol">RDP</acronym></a> and Citrix ICA protocols along with multi-monitor feature and a few other things.
 
 I like to know how it compares to RoyalTS since I created this one myself ;)
 
 <a target="_new" href="http://www.ishadow.com/Forums/tabid/56/view/topics/forumid/13/Default.aspx">http://www.ishadow.com/Forums/tabid/56/view/topics/forumid/13/Default.aspx</a>
 
 Best regards,
 
 ALEX

ALEX |ALEX

8/23/2006 11:20:24 PM (Eastern Daylight Time, UTC-04:00)

Thanks Alex! I tried it out. It looks like it could be pretty cool app, except that crashes at the slightest breeze. Because of that I couldn't get very far with testing it.
 
 One thing I wished it did (which RoyalTS does) was size the remote desktop to match the current window size. I don't mean scaling (which happens after the connection has been established), but actually setting the dimensions on the remote system's virtual video driver.
 
 I'd suggest a couple improvements for the website too:
 Differentiate between iShadow Desktop -vs- iShadow suite enough -- the difference (if any) is currently unclear.
 Make registration (during download) optional -- requiring it is inconvenient and invasive.
 
 It looks extremely promising, especially the side-by-side protocols. I'll keep an eye on it.
 
 How about VNC while you're at it?

Rob |Rob

8/23/2006 11:20:24 PM (Eastern Daylight Time, UTC-04:00)

Thanks Rob for checking iShadow Desktop out. Not sure why you had the experience "crashes at the slightest breeze" - I would recommend downloading a new version and trying it again :)
 
 Regarding desktop size - application detects current screen size (including situation with multiple monitors, which RoyalTS does not) and sets it as default with manual adjustments available. The goal here is to provide optimum desktop real-estate and compensate larger screen sizes with scale-to-fit functionality. Also note that iShadow Desktop can launch sessions with screen sizes exceeding available physical screen size including the full-screen mode.
 
 Another thing to look into - ability to show sessions side-by-side, which is unique to iShadow at this point.
 
 What is the relationship between iShadow Desktop and iShadow Application Suite? iShadow Desktop Beta will be part of iShadow Application Suite on the date of release. I am expecting it to become a standalone application as well.
 
 PS. Just added ability to import settings from <a title="" href="" ><acronym title="Remote Desktop Protocol">RDP</acronym></a> files created with Microsoft mstsc.exe client. This feature is available through the menu “Organize Favorites”.

ALEX |ALEX

8/23/2006 11:20:24 PM (Eastern Daylight Time, UTC-04:00)

DONE:
 <a target="_new" href="http://www.ishadow.com/Default.aspx?TabId=88">http://www.ishadow.com/Default.aspx?TabId=88</a>

ALEX |ALEX

8/23/2006 11:20:24 PM (Eastern Daylight Time, UTC-04:00)

Thanks for the heads-up, Alex. I tried the newest version, but without luck.
 
 The first problem: It seems that the previous version of iShadow Desktop registered its own msrdp.ocx. So it was locked by other <a title="" href="" ><acronym title="Remote Desktop Protocol">RDP</acronym></a> apps on my system when I tried to upgrade. I did get past that by closing the other apps.
 
 It'd be nice if the install would check to see if msrdp.ocx was already registered (which it is with Windows XP), and if so, leave it alone. If you're concerned about having the newest version, check for it. (I'm pretty sure I already had the newest version of that control, anyway).
 
 Next problem: I finished the install with no further issues. When I try to run the app, I first get a dialog with this error message:
 ---------------------------
 iShadow Desktop
 ---------------------------
 Unable to create cryptographic key container!
 
 No session information will be saved or restored!
 ---------------------------
 OK
 ---------------------------
 
 .. and then another with this message:
 ---------------------------
 iShadow Desktop
 ---------------------------
 Application terminated by the user.
 ---------------------------
 OK
 ---------------------------
 
 Of course it just quits there. Maybe it needs a reboot? It never says so, but I'll try again after I do.
 
 It sounds like you've got some great ideas, and I'm very excited about the VNC integration. While you're at it, how about other remote control protocols like GotoMyPC, RAdmin, and PCAnywhere?

Rob |Rob

8/23/2006 11:20:24 PM (Eastern Daylight Time, UTC-04:00)

I've rebooted twice and reinstalled iShadow, and I still get those two errors, so no luck. I'll try on another machine sometime.

Rob |Rob

8/23/2006 11:20:24 PM (Eastern Daylight Time, UTC-04:00)

Hey, any tests with the new iShadow Desktop (<a target="_new" href="http://www.ishadow.com">http://www.ishadow.com</a>)? There is a new RoyalTS out too - 1.3.2 (<a target="_new" href="http://www.code4ward.net/CS2/">http://www.code4ward.net/CS2/</a>)?

John |John

8/23/2006 11:20:24 PM (Eastern Daylight Time, UTC-04:00)

I have finally gotten iShadow Desktop working, and have been using it for a few weeks. It's nice but I think it's a little quirky. Right now I'd say it's at least equivalent as RoyalTS -- both are certainly better than Microsoft's own <a title="" href="" ><acronym title="Remote Desktop Protocol">RDP</acronym></a> clients.
 
 I'll probably do a more comprehensive review of iShadow when I get a chance (am I a reviewer now? as Wilde Silas Tomkyn would say, "hum!?").

Rob |Rob

8/23/2006 11:20:24 PM (Eastern Daylight Time, UTC-04:00)

Rob, there is a new update out. I suspect with this new release iShadow Desktop got the most advanced screen capture for remote sessions.

ALEX |ALEX

8/23/2006 11:20:24 PM (Eastern Daylight Time, UTC-04:00)

Thanks Alex, I'm trying it out. There are definitely some cool features in there.
 
 Hm, the iShadow installation broke my RoyalTS, making connections fail with the message "Error occured while connecting to requested server: Class not registered".
 Fortunately, I'm a pretty good troubleshooter, and I fixed it by re-registering %windir\system32\msrdp.ocx. Why is iShadow is unregistering msrdp.ocx, anyway??

Rob |Rob