"One of the first things that an admin wants to do with PowerShell ['Monad'] is run remotely. To do this securely, you must encrypt your data. SSH has been the proven way to do this. So the question becomes, how do I connect SSH and PowerShell together? With a little bit of kludge, it is possible."
Post a Comment
Member since:
2005-11-23
Member since:2006-01-10
Member since:2006-02-15
I noticed a 3rd party project called "PowerShell Remoting".. Another site ( http://www.redmonk.com/cote/archives/2006/06/teched_2006_pow.html )mentions remote capabilities (similar to what we expect of SSH) to be available in the 1.1 release. I suppose for now the idea is to use RDC and open a terminal?!?
Member since:2005-07-06
Remoting is a feature scheduled for a later release of PowerShell (v2, IIRC).
PowerShell is initially being staged across 3 releases, with the first aimed at standardizing the language and providing a stable, secure base supporting common scenarios. Subsequent releases will add other features like remoting and UI integration. There was a document on MSDN that provided some details on this, but I can't find it currently.
Remote execution is currently handled by the cmdlets/scripts (as is done in Exchange 2007 or WMI).
For file access, you can login to the remote machine using "net use" or similar (if you don't already have access), then "cd" to the remote share (e.g., "cd \\computername\sharename"). Powershell isn't needed on the remote machine for these scenarios.
For scenarios such as executing a remote PowerShell instance, you'll need to use TS/RDP or similar for now.
Edited 2006-07-11 19:56
Member since:
2005-07-14
Something like this really shouldn't require Cygwin. I was going to call it a kludge, but it isn't really... you're just (eventually) running PowerShell like you would any normal shell.
NT/2000/XP have come with an unsecured telnetd for years, you'd think "the most secure Windows ever!" would come with sshd.
- chrish
Member since:2005-07-18
Member since:2006-01-04
Member since:
2005-07-06
Member since:
2006-02-17
Member since:2005-07-07
Member since:2005-07-09
Member since:2005-07-09
Member since:2006-02-17
Member since:2005-07-06
Member since:
2005-07-06
A lot of the power of the .net framework (and hence Monad/powershell) is that it has inbuilt support for WMI, Remote Management (processes / services / users & groups / disk volumes /tasks etc) ... hence you run a script locally that queries a remote machine - the same you do with vbscript? The WMI etc services on the target computer return the information.
Or have I missed the point?
Member since:2006-01-04
Member since:
2005-07-18
I can type upwards to 100 words a minute, anytime I have to move my hands off the home row to the mouse, I am losing productivity.
Yes! This is the right perspective and the right issue. I get so very tired of the assumption that a GUI will somehow make me more productive.
Anytime I have to stream video, I am wasting bandwidth.
Right again.
Member since:2005-07-09
Member since:
2005-07-08
PowerShell might eventually become a useful tool for Windows administration, but it's by no mean revolutionary. For example, I've really enjoyed playing around with IPython and its pysh profile. It's essentially an interactive shell that lets you mix Python code and your default shell commands together. It makes interactively creating, saving, editing and running python scripts so seamless that I find myself amassing quite a collection of little timesavers. It's very much a work in progress, but then again so is PowerShell, and it seems like IPython is way more useful at the moment.
Yes, it runs on Windows and Mac OSX, too.
Member since:
2005-10-14
Member since:2005-07-06
Member since:2005-11-10
Member since:2005-07-06
Those that do not undestand Monad (PowerShell) think it's like Unix shells.
The OP didn't say it was "like Unix shells." He implied it was like a poorly implemented UNIX shell.
Monad works with objects. BIG difference...
Again, the OP appears to have accounted for this with the use of the qualifying word "poorly".
Member since:2005-11-10
Obviously, both of you do not understand that Monad is not like Unix shell at all. Thus, it can not be "like poorly (or 'like well') implemented Unix shell."
Another thing is, what is so poor about Monad?
I've been using it for almost six months now and it simply rocks. Maybe you should give it a try..
Member since:2006-05-01
Member since:2005-11-10
Usually, people that say that ("..limited environments..") -- it is the same people that think Monad is "poorly implemented Unix shell".
:)
OK, I suppose you use Unices and I don't see that you'll miss PowerShell (Monad) there simply because Unix has its ways of doing things in shell (text goes through pipes) and everything is done that way already while Monad does it differently (objects go through pipes).
On Windows, it will make a huge difference especially because Microsoft is (slowly) going to support PowerShell with all its producs (for example, Exchange beta now fully supports Monad. You can do anything from Monad. Actually, Exchange GUI, IIRC, uses Monad to perform all tasks).
One last thing, if on my Windows I can run both bash (via Services for Unix, Cygwin, etc) and Monad, while one can not run both on, for example Linux, then I really have to ask --- which environment is more limited?
