Solved

Want to create a 32 bit remote powershell session

Posted on 2014-09-24
6
409 Views
Last Modified: 2014-09-25
This is what I do:

. E:\VMWare\scriptWithMyFunction.ps1	
$username = "username";
$password = ConvertTo-SecureString -String "password" -AsPlainText -Force
$cred = new-object -typename System.Management.Automation.PSCredential -argumentlist $username, $password
$session = New-PSSession -Credential $cred -ComputerName "serverdnsname"
$a = Invoke-Command -Session $session -ScriptBlock ${function:myFunction} -ArgumentList $var1, $var2, $var3

Open in new window


However, this starts a 64 bit powershell session and when loading the VMware.VimAutomation.Core snapin, an error message gets thrown that states: "This cmdlet requires 32bit process."

So how can I make a 32 bit process and still do the above?
0
Comment
Question by:itnifl
  • 3
  • 2
6 Comments
 
LVL 16

Expert Comment

by:Dale Harris
ID: 40341192
Try opening the Powershell (x86) version on your computer, then run the script again.  See if that's the key.
0
 
LVL 2

Author Comment

by:itnifl
ID: 40341195
I run the script from System Center Orchestrator, which by default starts 32-bit Powershell 2.0. When Invoke-Command is used, this starts a 64-bit powershell 4.0 session. This source says 3.0, but I am jumping to the assumption that 4.0 was not there at the time? http://windowsitpro.com/orchestrator/call-windows-powershell-orchestrator
0
 
LVL 68

Expert Comment

by:Qlemo
ID: 40341215
You'll need to call Invoke-Command (or in your case New-PsSession) with –ConfigurationName Microsoft.PowerShell32 to start a 32bit session.
0
Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

 
LVL 2

Author Comment

by:itnifl
ID: 40341419
Yeah, if that would only work. I have only seen documentation on Invoke-Command for PS 3.0 and PS4.0, not PS2.0 that Orchestrator uses by default. I have seen those suggestions on the internet/google, and it has not worked:

The error is simple when using the suggestion:
Invoke-Command : Parameter set cannot be resolved using the specified named parameters.

I have tried to out all the code in a function, then run invoke-command to run the function in PS4.0 64bit, then run invoke-command again inside that function remoting to the host with the following:

Invoke-Command -Session $session  –ConfigurationName Microsoft.PowerShell32 -ScriptBlock ${function:myFunction} -ArgumentList $var1, $var2, $var3,

Open in new window


Results in same error as above.
0
 
LVL 68

Accepted Solution

by:
Qlemo earned 500 total points
ID: 40341547
This is an invalid combination of parameres - you can't provide -Session and -ConfigurationName at the same time. Either use
Invoke-Command -Credential $cred -ComputerName "serverdnsname" -ConfigurationName Microsoft.PowerShell32 -ScriptBlock ${function:myFunction} -ArgumentList $var1, $var2, $var3

Open in new window

or
$session = New-PSSession -Credential $cred -ComputerName "serverdnsname" -ConfigurationName Microsoft.PowerShell32
$a = Invoke-Command -Session $session -ScriptBlock ${function:myFunction} -ArgumentList $var1, $var2, $var3

Open in new window

0
 
LVL 2

Author Closing Comment

by:itnifl
ID: 40343795
Thanks, would wish the error message was that specific..
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Suppress Configuration Issues and Warnings Alert displayed in Summary status for ESXi 6.5 after enabling SSH or ESXi Shell.
A brief introduction to what I consider to be the best editor for PowerShell.
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…

861 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now