If you regularly connect to multiple servers, using RDP or a similar protocol (VNC etc.), then you probably have a good memory of all the various IPs/Hostnames of the servers. Either that, or you keep them in a document and regularly copy/paste to connect.
Personally, I have to connect to 9 of my own servers along with 40+ servers at work on a daily basis. For home, I kept 9 separate RDP connections saved to my Desktop, cluttering it up with their icons. This worked for a while, but was cumbersome and inefficient. At work, we keep a spreadsheet of IPs for each server and over a period of time you begin memorising each.
So I started looking for a better solution, one that would store each of my required server connections in an orderly fashion, allowing me to connect to multiple servers at once from within a single interface. I soon came across Terminals, a secure, multi tab terminal services/remote desktop client. It stores the configuration in ASP.NET's .config file, an XML style format which allows you to easily take your saved list of connections with you to another install.
It's also very configurable with more options than the standard RDP client and also supports VNC, VMRC and many other protocols, allowing you to combine your server connection tools into one. And you can tag connections, allowing you to group them into logical categories - for me, per Active Directory domain/location.
If you meet the criteria, then give Terminals a go.