I have a wonderful shell script which I will be posting in the library when it's ready, that will test a group of services and give an up/down status of the group. This is particularly handy when an application is dependant on the entire set of services for an 'UP' status (i.e. Crystal Reports, ArcServe, Backup Exec, Symantec EndPoint Protection, etc.).
But because I'm trying to run this on a remote machine I've spent the last week trying to debug script based remote authentication using the objLocator.ConnectServer method. I'm an admitted VBScript hack, so any code samples you can point me to would be appreciated.

I'm almost there, but wouldn't it be grand if EVERY test method allowed you to define it's host. At that point, it seems to me, that the features of Connection Manager could be extended to most, if not all, test methods, launching a session if the named host has a subsequent Connection Manager Profile and running the test after a connection has been established, or fail gracefully based on the 'CM' results.
I know I've barked about this once before, but it's a bit frustrating when some tests (UNC, process test, etc.) have a field specifically for the host (sometimes called Server, Address, URL, or something else), while others don't (Shell Script). Sometimes it's implied as local (File/Folder size), or it's buried in an expression (as with the Performance Monitor 'check counter' field).
In every one of these cases a field could be used to define the host, not only for the reasons listed above but also for the purpose of generating reports and performing advanced log analysis across test types based on the host. I know, at least from a reporting standpoint, I could use a Comment field, but isn't that just a workaround?
And while I'm still a big fan of the HM these suggestions aren't just based on my vision, but on the features I've seen/experienced with other similar products. I'm selfish and I want the HUGE strengths I see with HM AND the strengths I've seen elsewhere in one package.
