Search

Powershell in Windows RT fails to Run Implicit Remoting to Powershell 2.0 by Sean Kearney

Active

6
0
Sign in
 to vote
Type: Bug
ID: 770035
Opened: 11/4/2012 1:13:33 PM
Access Restriction: Public
0
Workaround(s)
2
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
Details (expand)
How often does this happen?
Always Happens

Have you seen this problem before in this product?

No, this is new to the most recent version
Reproduction Steps
Add Client system as "Trusted" I WinRM on remote host
Add remote Host as "Trusted" on WinRM in Windows RT device

execute
$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)
Expected Results
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

$X=GET-XXCHILDITEM C:\THISFOLDER

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

BUT

ENTER-PSSESSION $S
GET-CHILDITEM C:\THISFOLDER

Works fine
File Attachments
0 attachments
Sign in to post a comment.
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement