Windows PowerShell Home
Powershell in Windows RT fails to Run Implicit Remoting to Powershell 2.0
Sean Kearney (Honorary Scripting Guy)
11/4/2012 1:13:33 PM
User(s) can reproduce this bug
When Executing a PS-Remoting Session from a Microsoft Surface Device with Windows RT using Powershell 3.0 to Powershell 2.0 on a remote server (with defined trusts in WinRM) Implicit remoting fails
An interactive session on the x64 Remote server works fine, but using an IMPORT-PSSESSION with -prefix parameter fails to produce any available cmdlets.
EXPORT-PSSESSION will produce a module on the local Windows RT device but the module will not load and execute
How often does this happen?
Have you seen this problem before in this product?
No, this is new to the most recent version
Add Client system as "Trusted" I WinRM on remote host
Add remote Host as "Trusted" on WinRM in Windows RT device
$s=NEW-PSSESSION -computer Netbios1 -credential (GET-CREDENTIAL)
(enter credentials for WinRM remoting on Remote system Netbios1)
IMPORT-PSSESSION $S -prefix XX
(To produce new verbs with an "XX" prefix from the remote system)
If you would like to run something like GET-CHILDITEM C:\THISFOLDER (as an example on the remote system) and store the results in $X
It should execute "GET-CHILDITEM C:\THISFOLDER" on remote System NETBIOS1
It fails as the cmdlets do not appear as available cmdlets on the local system
to post a comment.
Please enter a comment.
on 5/26/2014 at 6:06 AM
Error also happens without using prefix.
$Session = New-PSSession -ConfigurationName microsoft.exchange -connectionuri https://ps.outlook.com/powershell/ -Credential $livecred -Authentication Basic -AllowRedirection
to post a workaround.
Please enter a workaround.
© 2014 Microsoft