Remoting with PowerShell QuickStart

re: Remoting with PowerShell QuickStart

Soliko — Sat, 10 May 2008 09:28:36 GMT

Is there WinRM CTP for windows 2003 or XP?

re: Remoting with PowerShell QuickStart

PowerShellTeam — Sat, 10 May 2008 16:46:27 GMT

> Is there WinRM CTP for windows 2003 or XP?

Sadly no, not at this time.

Yes - we know exactly how painful this is. We just couldn't make the schedules line up.

Jeffrey Snover [MSFT]

Windows Management Partner Architect

Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell

Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

re: Remoting with PowerShell QuickStart

PowerShellTeam — Sat, 10 May 2008 16:57:35 GMT

BTW - you can easily clean up the output by simply casting the expression to an [INT] (notice that I put the expression inside () so that we cast the RESULTS of the expression and not the FIRST ELEMENT.

Change:

icm kriscv-lh {gwmi win32_logicaldisk | select deviceid,freespace} | select deviceid,@{Name="freespace(GB)";Expression={$_.freespace/1gb}},computername

icm kriscv-lh {gwmi win32_logicaldisk | select deviceid,freespace} | select deviceid,@{Name="freespace(GB)";Expression={[INT]$($_.freespace/1gb)}},computername

And things clean up very nicely.

10,000 thanks to Krishna for going out of his way to do this write up. Take a look at the published time!

Jeffrey Snover [MSFT]

Windows Management Partner Architect

Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell

Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

re: Remoting with PowerShell QuickStart

Mike Schinkel — Sun, 11 May 2008 02:19:14 GMT

Oooooh! Your security team is going to have run keeping the hackers at bay on this one! ;-)

But seriously (as I'm really not a security wonk), why can't you make it so that I could run a script on the remote machine that exists only on my local machine? Forcing the remote machine to have the script is a rather large burden, no? Need I detail why?

re: Remoting with PowerShell QuickStart

PowerShellTeam — Sun, 11 May 2008 18:31:48 GMT

> But seriously (as I'm really not a security wonk), why can't you make it so that I could run a script on the remote machine that exists only on my local machine?

Ask and ye shall receive. :-)

It does! First let's start with the basics. We'll ship "secure by default". That means that you will have to make a decision to allow remote computers to manage a machine. Next, when you configure remoting, you'll have a number of configuration options which give you fine control over what the remote machines can do. In particular, there are 3 language MODES: FULL, DATA, NONE.

FULL is obvious - there are no language restrictions.

DATA limits the language to those elements that do not allow side-effects on the system.

NONE means you can enter commands but no language elements.

For each of these, you'll be able to configure what CMDLETS, SCRIPTS, Native applications, providers, and variables that are available to the remote machine.

jps

re: Remoting with PowerShell QuickStart

Ilya Haykinson — Mon, 12 May 2008 13:43:00 GMT

Ok, so maybe I'm doing something wrong, but the winrm configuration isn't working:

PS C:\Windows\System32> . $pshome\configure-wsman.ps1

VERBOSE: Configuring WinRM

WSManFault

Message = Access is denied.

Error number: -2147024891 0x80070005

Access is denied.

CheckError : Error restoring default WSMan configuration. Exiting

At C:\Windows\system32\WindowsPowerShell\v1.0\\wsmanutils.ps1:97 char:19

+ CheckError <<<< $ErrorMessages["Restore"]

WSManFault

Message = Access is denied.

... and more of the same. this is with an elevated version of powershell...

re: Remoting with PowerShell QuickStart

PowerShellTeam — Mon, 12 May 2008 15:55:10 GMT

> Message = Access is denied.

1) Are you running with elevated Privs?

2) Do you have Admin Rights?

jps

re: Remoting with PowerShell QuickStart

PowerShellTeam — Wed, 14 May 2008 04:44:01 GMT

Can you check if WinRM is running?

PS F:\> get-service winrm

Status Name DisplayName

------ ---- -----------

Stopped WinRM Windows Remote Management (WS-Manag...

PS F:\> start-service winrm PS F:\> get-service winrm Status Name DisplayName ------ ---- ----------- Running WinRM Windows Remote Management (WS-Manag...

re: Remoting with PowerShell QuickStart

Simon Garratt — Sun, 18 May 2008 23:15:03 GMT

I noted the comment above about 2003 and XP. Are you committed to providing remoting on 2003 and XP in the final version? We're really keen to see this.

re: Remoting with PowerShell QuickStart

PowerShellTeam — Mon, 19 May 2008 02:52:50 GMT

> Are you committed to providing remoting on 2003 and XP in the final version?

Never trust anything that looks like a commitment made in a blog. Seriously. If you ever see anything that looks like a commitment in this blog - it has to be understood as a PERSONAL commitment not a corporate commitment.

For example, I could say that I'm personally committed to making this go downlevel but that is VERY differen than saying that the company is committed to doing so.

Here is what I said in the blog entry:

http://blogs.msdn.com/powershell/archive/2008/04/24/how-could-you-top-ctp1.aspx

One big caveat to share with you around remoting. The good news is that we've made a lot of progress on remoting and it is shaping up nicely. The bad news is that (FOR THIS CTP) remoting is only going to work FROM and TO Vista and WS08 boxes (CRINGE!). I know that is a big hit and it means that many of you will not be able to test out remoting for us. Apologizes. There are a zillion details behind this so without going into them, all I can say is 1) we know exactly how BIG of a deal this is 2) we worked like heck to try and make it happen 3) the facts we were faced did not allow it to happen.

Just to be clear, this applies to the upcoming CTP and we are working very hard to make it available on downlevel machines in subsequent public releases.

Jeffrey Snover [MSFT]

Windows Management Partner Architect

Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell

Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

re: Remoting with PowerShell QuickStart

Paiboon — Thu, 12 Jun 2008 10:44:31 GMT

Hello,

When I run Receive-PSJob -job $job I got error like below. How do I do for fix this problem please advice? I use WinXP + SP2.

PS C:\> $job = Start-PSJob -command "Get-Process"

PS C:\> Receive-PSJob -job $job

Receive-PSJob : [localhost] The WS-Management service does not support the requ

est.

At line:1 char:14

+ Receive-PSJob <<<< -job $job

PS C:\> Get-Service winrm

Status Name DisplayName

------ ---- -----------

Running WinRM Windows Remote Management (WS-Manag...

PS C:\> $job

SessionId Name State HasMoreData Command

--------- ---- ----- ----------- -------

1 Failed False Get-Process

re: Remoting with PowerShell QuickStart

PowerShellTeam — Thu, 12 Jun 2008 20:37:56 GMT

You need to install the CTP of WSMan 2.0, but they are currently supported on Vista-SP1 and WS08 only.

re: Remoting with PowerShell QuickStart

DaveP — Thu, 07 Aug 2008 01:57:25 GMT

What is the current status of remoting on WinXP and WinServer 2003? I'd love to use PS for a proof on concept. Thanks.

re: Remoting with PowerShell QuickStart

Sanjay — Fri, 17 Oct 2008 18:08:35 GMT

Can you share some information on Powershell Remoting and Exchange 2007 administration?

re: Remoting with PowerShell QuickStart

Adam — Sun, 26 Oct 2008 05:19:04 GMT

I've been trying to use the Remoting capabilities within a C# application but it seems my assembly System.Management.Automation.dll doesn't contain

"System.Management.Automation.Remoting"

Any ideas?

Thanks in advance!

Adam

re: Remoting with PowerShell QuickStart -- XP etc

Josh Smith — Thu, 04 Dec 2008 19:40:56 GMT

I noticed WinRM is out for WinXP, but I imagine that doesn't necessarily mean that PS2 CTP2 now magically supports remoting. I actually get pretty far w/the WS-management script, except I get this one error:

CheckError : Configuring PowerShell plugin failed

At C:\WINDOWS\system32\WindowsPowerShell\v1.0\\wsmanutils.ps1:155 char:16

+ CheckError <<<< "Configuring PowerShell plugin failed"

Note v2.0 is installed, it's just in the v1.0 directory

re: Remoting with PowerShell QuickStart -- XP etc

Josh Smith — Thu, 04 Dec 2008 23:32:36 GMT

CheckError : Configuring PowerShell plugin failed

At C:\WINDOWS\system32\WindowsPowerShell\v1.0\\wsmanutils.ps1:155 char:16

+ CheckError <<<< "Configuring PowerShell plugin failed"

Note v2.0 is installed, it's just in the v1.0 directory

re: Remoting with PowerShell QuickStart

PowerBloger — Fri, 05 Dec 2008 02:16:50 GMT

You need to install the CTP of WSMan 2.0, but they are currently supported on Vista-SP1 and WS08 only.

re: Remoting with PowerShell QuickStart

BobK — Sat, 13 Dec 2008 11:22:39 GMT

Hi - I'm really having a lot of trouble understanding/confirming the exact system requirements needed to use PS remoting. I've looked around quite a bit on various blog sites - most everyone else seems to be able to run remoting commands with no issue.

My problem is that I am running both WS2008 and Win7, with the versions of PS 2 installed via the base OS install, and I am unable to use any remoting commands. I have done "winrm quickconfig" and the "configure-wsman1" scripts but no PS command seems to want to admit to knowing anything about remoting, they all give me errors saying that they do not know anything about '-computername', etc. The below output is from my WS2008 machine.

Is there a document or site somewhere that specifies *EXACTLY* what versions of the OS and PS you need to do remoting, and *EXACTLY* what steps need to be taken to set it up?

Many thanks

PS C:\Windows\System32\WindowsPowerShell\v1.0> $host.version

Major Minor Build Revision

----- ----- ----- --------

2 0 -1 -1

PS C:\Windows\System32\WindowsPowerShell\v1.0> $psversiontable

Name Value

---- -----

CLRVersion 2.0.50727.3506

BuildVersion 6.1.6936.0

PSVersion 2.0

PSCompatibleVersions {1.0, 2.0}

PS C:\Windows\System32\WindowsPowerShell\v1.0> winrm id

IdentifyResponse

ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd

ProductVendor = Microsoft Corporation

ProductVersion = OS: 6.1.6936 SP: 0.0 Stack: 2.0

PS C:\Windows\System32\WindowsPowerShell\v1.0> invoke-expression -computername foo

Invoke-Expression : A parameter cannot be found that matches parameter name 'computername'.

At line:1 char:32

PS C:\Windows\System32\WindowsPowerShell\v1.0> new-runspace

The term 'new-runspace' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again.

re: Remoting with PowerShell QuickStart

BobK — Fri, 19 Dec 2008 12:12:02 GMT

Hmm. Looks like I stumped the panel. Can anyone at least recommend another site where I can try reposting?

PowerShell V2: CTP3 now available!

James Manning's blog — Tue, 23 Dec 2008 16:57:24 GMT

Sea Tea Pea Three Whee! Go get it ! The bits in the overview I want to call out (because I've seen others

re: Remoting with PowerShell QuickStart

Will Ludgate — Sat, 28 Feb 2009 21:05:39 GMT

Please help - similar problem to somebody above.

I'll give as much detail as possible. I have upgraded to vista home professional & am trying to get powershell 2 to run background jobs. But I just can not do it.

I am first trying to get CTP2 working as if you jump straight to CTP3 you do not have the configure-Wsman.ps1 script !

Anyway - I've installed WinRM CTP3 on vista (x86) & powershell. I've tried all the suggestions to change the registry(DWORD stuff), stop UAD etc. I have even restored the "hidden" administrator id. But still, when trying to configure winRM I get ....

PS C:\Users\Administrator> get-service winrm

Status Name DisplayName

------ ---- -----------

Stopped WinRM Windows Remote Management (WS-Manag...

PS C:\Users\Administrator> start-service winrm

PS C:\Users\Administrator> & $pshome\Configure-Wsman.ps1

Configuring WSMan

WSManFault

Message = Access is denied.

Error number: -2147024891 0x80070005

Access is denied.

Error restoring default WSMan configuration. Exiting

PS C:\Users\Administrator>

Please can somebody help

Cheers

Will

re: Remoting with PowerShell QuickStart

PowerShellTeam — Mon, 02 Mar 2009 20:15:07 GMT

@Will

Basically you need to check three things:

1. PowerShell console runs elevated.

2. Password of your administrator account is not empty.

3. Local account token filter policy is enabled:

new-itemproperty -path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -name LocalAccountTokenFilterPolicy -propertyType DWord -value 1

Also, in CTP3 you need to use Enable-PSRemoting command for remoting configuration. Configure-WSMan script is deprecated.

Hope this helps,

Vladimir Averkin

Windows PowerShell team

re: Remoting with PowerShell QuickStart

Joel "Jaykul" Bennett — Tue, 01 Dec 2009 20:30:44 GMT

Any chance we could get these old posts updated AT THE TOP with something like [[THIS WAS A CTP POST -- IT'S PROBABLY WRONG NOW]] so that people don't have to come all the way to the bottom (or into IRC or USENET) to figure out why configure-wsman.ps1 doesn't work anymore?

re: Remoting with PowerShell QuickStart

Tadlock Enterprises — Tue, 22 Dec 2009 04:02:33 GMT

Question about how to import modules on a remote server. I'm trying to remotely stop an IIS website with the following command but it doesnt seem to work (although it doesnt report an error either).

powershell -command "icm hydrogen {import-module webadministration | stop-webitem iis:\sites\mysite}"

Any thought on why this doesnt work?