• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 941
  • Last Modified:

Looks like System Center Orchestrator uses an old and different version of powershell

I have upgraded Powershell on our System Center Orchestrator 2012 server to 4.0. I still see there are cmdlets missing that should be in the 4.0 version when I run powershell scripts with Orchestrator. I than created a runbok to run a powershell script containing this:

$PSVersionTable.PSVersion > C:\temp\test1.txt
get-host > C:\temp\test2.txt
echo $PsHome > C:\temp\test3.txt

Open in new window


And this is what I get:


test1.txt
Major  Minor  Build  Revision
-----  -----  -----  --------
2      0      -1     -1    

test2.txt:
Name             : Default Host
Version          : 2.0
InstanceId       : 3abe31d9-42ac-4025-bd4a-d5be8a342e89
UI               : System.Management.Automation.Internal.Host.InternalHostUserIn
                   terface
CurrentCulture   : nb-NO
CurrentUICulture : en-US
PrivateData      :
IsRunspacePushed :
Runspace         :

test3.txt:
C:\Windows\SysWOW64\WindowsPowerShell\v1.0


When I start powershell.exe under C:\Windows\SysWOW64\WindowsPowerShell\v1.0 and run the same commands,it says it is 4.0.

So how do I get Orchestrator to use Powershell 4.0, and not 2.0?
0
itnifl
Asked:
itnifl
  • 2
  • 2
1 Solution
 
Leon TaljaardSystem Center Specialist - ArchitectureCommented:
Hi

What you could do is call the command like this within the Orchestrator activity, see link below with example of how it is done.

http://www.purgar.net/using-exchange-2010-cmdlets-in-system-center-orchestrator/

You could also install the PowerShell Integration Pack from the following site and use it this way instead.

http://orchestrator.codeplex.com/releases/view/76101

Hope this helps
0
 
itniflAuthor Commented:
Actually they have version 1.2 now of Integration Pack for PowerShell Script Execution. i was leaning towards these suggestions you came with, found them on Google. However, it would be great to just know how to upgrade the Powershell version that Orchestrator uses.
0
 
Leon TaljaardSystem Center Specialist - ArchitectureCommented:
HI

Yes they do, just upgraded the other day to use this.

I am not sure you can upgrade the one Orchestrator uses unless you maybe create your own Activity with the details of the new version of PowerShell in it then it should be able to use the version 4.0, so then you always use your newly created Integration Pack and custom activity rather all the time.

But as I said, I would just call the path within the existing one, that would be a quicker solution and should then call the version you want.

Thanks
0
 
itniflAuthor Commented:
The Powershell Integration Pack did the trick.
0

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now