Multiple keyword search
This is so incredibly awesome. Loving it! Thanks Stefane. I guess I need to visit your offices more often. ;)
System availability status
David,
Thanks for adding the keep open tab and reconnect option. One minor suggestion to change on this feature. Currently you're monitor host availability status. If I reboot a server and then click on the reconnect when available feature it will immediately fail. What I suggest you do is pause the connect request for about 5-10 seconds (give the host a few seconds to shutdown/reboot. Also, if the connect is an RDP connect or ICA connection or whatever, only attempt to reconnect when that actual port is listening. In other words, when a host reboots it'll start responding to pings almost immediately when the IP stack comes up, but it may be 30-60 seconds before the RDP/ICA/VNC, etc listener starts responding. So if you check port status (telnet like connection attempt) instead of host status (ICMP ping) then you'll have more realiable reconnection attempts.
Thanks.
Shawn
Multiple keyword search
I use tagging extensively as a way to filter a list of servers to connect to. One feature it seems RDM is missing (or at least I can't figure out the right keyword terms) is a way to combine search terms in the search box. For instance I might want to display a filtered list of servers running app version 4.5 AND in the Prod environment. I can easily search 4.5 or Prod, but I don't see a way to combine both terms to get a filtered list of both. I tried putting both keywords in using spaces, commas, "AND", "&", "&&" but nothing works.
Shawn
System availability status
One of the features I really liked in iShadow is that when you disconnected from a server, the tab remained open (because often times after rebooting a system you'll connect back into again when it's back up). In this disconnected tab, there was a Red or Green LED in the tab of the window. The LED light would indicate whether or not the RDP/ICA/etc port was responding (basic port telnet test). When the server was down it would be red, but upon the server coming back up it would go green. Was a really nice way of knowing when a server was back up and you could reconnect back into it. iShadow actually listed this port status for all systems as well so you could visually see which systems were not responding before connecting to them. That could be overkill though.
Shawn
Possible to use subconnections & shortcuts togethe
I may have found an acceptable workaround for this. Rather than use subconnections, I just created a folder for each hypervisor host. Inside that folder I'm adding the host hypervisor entry and it's corresponding VMs, then I'm creating shortcuts for the VMs to appear at the root group folder. Seems to work fine.
Shawn
Possible to use subconnections & shortcuts togethe
I had an idea that I was going to create a Hosts group and inside that hosts group list each of my lab servers various hypervisor hosts (ESXi, Hyper-V, XenServer). My plan was then to use the subconnections feature to have the VMs running on each of those hosts listed below the hypervisor host. This works fine. This is a nice way of organizing things so I can visually tell which host/hypervisor a VM is running on. The downside of this approach is that you need to know which hypervisor host a given VM is running on in order to launch a connection when using the systray icon right-click method. My thought on a way to fix this was to create shortcuts for each subconnection and list them directly under the main group. I can't seem to find a way to do this. Is there a way to use subconnections and shortcuts together? Or maybe a better way of organizing items to fit what I'm trying to do?
Thanks.
Shawn