Microsoft, please fix Remote Desktop Co ection for Mac

I live something of a double life. By night I am a highly influential, and very sexy, A le blogger/pundit but by day I am a highly skilled Windows System Administrator (though I'm still very sexy). Thanks to the confluence of a nice bo and Intel Macs I am able to do all my work on a shiny new MacBook Pro. However, there is one a lication that I find myself using, and cursing, on a daily basis: Microsoft's Remote Desktop Co ection.

Don't get me wrong, I think it is fantastic that MS makes this program available for the Mac, but it just wa 't created for someone who needs to co ect to multiple Windows machines in any way. I know that the MacBU is hard at work on a Universal version of Remote Desktop Co ection, so I thought I would list my major gripes with the program to help them focus on what I want (and i 't that what they truly care about?):

1. No concurrent co ectio : Often, I need to log into more than one Windows machine at the same time. This is very easy to do within Windows itself, thanks to the magic of MMCs (that's Microsoft Management Co oles to you), but nearly impo ible using RDC on the Mac. The client only su orts one co ection at a time, so you're out of luck if you are troubleshooting a cluster with 2 Windows nodes. The work around is to create a number of duplicates of the program itself, so you can have multiple copies of the a ru ing. This is lame.
2. Disco ecting from a remote machine quits the a : This is the most a oying a ect of RDC. So, I can't co ect to more than one machine at the same time, no big deal. I'll just co ect to one after the other. Sadly, RDC quits the moment you disco ect from a remote machine. This mea you need to relaunch the program to co ect to another machine. This is stupid.

Other than those two major complaints, I am very ha y with RDC and hope to see a number of improvements in the forthcoming update (No, I don't have any idea when it is coming out).