Using Live Mesh as a Message Based PowerShell Remoting Tool
"Once problem that often arises when trying to manage machines is when the management layer itself is the thing you need to diagnose. For example, trying to diagnose Remote Desktop connectivity issues when port 3389 is blocked, or using PowerShell Remoting when WSMAN is misconfigured.
Alternatively, you might not have the client you need to manage the machine -- such as an SSH client, or a version of PowerShell V2 installed.
One way to get around both of these problems is another communication channel. It may be of lower fidelity, but can help you get your job done.
One perfect example of an alternative communication channel is any of the many synchronization tools out there: Live Mesh, Syncplicity, FolderShare, etc. In addition to managing connectivity, they let you broadcast messages (by way of files) between connected computers. Let's use that as our communication protocol:
…”
There’s something about this, well this “hack” in the classical sense of the word, that just appeals to me. Using Live Mesh to transfer messages (i.e. files) between workstations, kind of like a MSMQ channel seems kind of neat. And given MS is working hard to secure Live Mesh, will be providing a SDK, etc, well there might be something to this.
Okay, yeah, yeah, I know it’s a Frankenstein, Rube Goldberg, like contraption, but that doesn’t make it any less cool. :)
Posts
No comments:
Post a Comment