/build/static/layout/Breadcrumb_cap_w.png

how to open 64bit powershell console via kace scripting

I am trying to deploy a script from kace . In the script there is a work flow and every time I try, I get following error;

PS>TerminatingError(Import-Module): "Windows PowerShell Workflow is not supported in a Windows PowerShell x86-based console. Open a Windows PowerShell x64-based console, and then try again."


Thanks in advance. 



0 Comments   [ + ] Show comments

Answers (3)

Posted by: Mashby1 3 years ago
Purple Belt
0

I have been down this road and I was not successful, but you could try this:

Kace agent is a 32bit binary so it invokes 32-bit powershell.

Stick this at the very top of your script to prevent this issue.

https://gist.githubusercontent.com/ArtisanByteCrafter/91167d5178a13f7c038236a5d7881ca7/raw/eac25942cdef695b178c31c954f286b6988f8388/Relaunch-as-x64.ps1

Also, check out the Kace powershell module if you haven't already.

Install-module kacesma


From: Powershell and KACE - Get-ChildItem in C:\windows\systerm32\winevt\logs not working : PowerShell (reddit.com)

Posted by: jencam 3 years ago
Orange Belt
0
Above solution did not work for me. I gave up on the subject. to the admin; please close this thread.
Posted by: Kiyolaka 3 years ago
Third Degree Green Belt
0

As others have mentioned, the KACE agent by default launches stuff in 32-bit context. 

I have the following check in my scripts so that they are launched in the native environment for 32 or 64 bit systems.

R6JbXTegDtQAAAABJRU5ErkJggg==

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ