Vista - Quick and easy one...

I just realized one of the major limitations of PowerShell in my originally
installed v1.0 on XP SP2- I can't do anything on a remote system. So, I
searched around and found that there's a newer version (v2.0) that does
support remote capabilities. After installing it and the required WinRM
(Windows Remote Management), I issued a simple command against a remote
system and blah... it spewed out a bunch more errors. Doing some further
research, it appears that I won't be able to do very much in PowerShell
unless it's installed on *each* system that I want to manage. Is this true?

It is, WinRM is also required on all remote machines.



-----
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

In order to use PowerShell V2 remotely you will need to have PowerShell V2
and win-rm enabled on both the local and the remote machine.

if you can't get V2 loaded on to the remote machine then you will have to
fall back on to .NET and WMI ot use something like SpecOps Command that lets
you run PowerShell through GPOs
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"gscanga" wrote:

Thanks Rich,

<soapbox warning>
I have to admit that this is a big disappointment. With as much hype that
surrounds PowerShell and its usefulness, it sure is a blow to administrators
who will have to install this (plus WinRM and perhaps even .NET 2.0) on every
system that they want to manage. For change mgmt, this is a big/hard sell and
I'm sure there are other business groups that frown on such a widespread
config change.

I was expecting that PowerShell would leverage the existing tools that
systems already have installed (cmd, .net [vb]), etc). I really want to learn
better ways to script and administer systems and share in the hype but this
is a formidable caveat until we upgrade to a pure Vista and Server 2008
environment :-P
</soapbox>

I appreciate the clarification...



"RichS" wrote:

gscanga wrote:Let's be fair here. While I personally *hate* the WinRM requirement for V2
remoting, PowerShell v1 is extremely capable at performing remote operations
using several methods and it does not require you to install any additional
software. I'm talking about WMI, COM, ADSI, plus any other remote tools you are
currently using can be used from PowerShell as well, such as psexec. On top of
that, Microsoft and external vendors can create snapins with cmdlets which
perform remote operations in a way that is very native to PowerShell. /n
Software's NetCmdlets [1] is one such example, or Exchange 2007 and Virtual
Machine Manager from MS or you have stuff from IBM [2], VMware [3], and more on
the way.

I think it is much more productive to just ask here how to do something--I
guarantee you'll get a lot of replies and ideas.
? You most certainly can take advantage of your existing tools. In fact,
PowerShell is the ONLY thing going that can work with cmd.exe, .NET, and COM
stuff--all in the same script if you wanted to. That's one of its big
strengths.

Is there something in particular you think can't be done that we could help you
out with?
That is a total misconception in my opinion. Ideal? No. But it is DEFINITELY
worth investing time in learning what you can do with PowerShell now.

Besides, PowerShell doesn't come with Vista, only Server 2008 (and as everything
is on that OS, it is intentionally not installed by default).

[1]: http://www.nsoftware.com/powershell/
[2]: http://www-1.ibm.com/support/docview...id=swg24017698
[3]: http://blogs.vmware.com/vipowershell/

--

Hal Rottenberg
Blog: http://halr9000.com
Webmaster, Psi (http://psi-im.org)
Co-host, PowerScripting Podcast (http://powerscripting.net)

OK, thanks for these excellent distinctions Hal. I vow to maintain an
interest in learning PowerShell. Especially since I'm an avid user of the
PsTools suite. Matter of fact, it was a PsTools question that originally got
this thread rolling.

http://forum.sysinternals.com/forum_...ID=62743#62743

I still can't succeed in executing the suggested PowerShell command but to
be fair, the command was offered from a Vista environment (and I'm on XP SP2).

I have since upgraded to PowerShell v2 but still no success. Thanks for the
time.

"Hal Rottenberg" wrote:

gscanga wrote:Glad I could help. I've decided to discuss this topic on Episode 19 of the
podcast, due out this Sunday.

--

Hal Rottenberg
Blog: http://halr9000.com
Webmaster, Psi (http://psi-im.org)
Co-host, PowerScripting Podcast (http://powerscripting.net)