PrimalScript PowerShell Execution Policy

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
robwm1
Posts: 90
Joined: Wed May 07, 2008 6:46 am

PrimalScript PowerShell Execution Policy

Post by robwm1 » Tue Feb 07, 2017 12:19 pm

Product, version and build: 7.3.98.0
(*** Please do not write "latest" as a version, specify a version number ***)
32 or 64 bit version of product: 64-bit
Operating system: Windows 10 Enterprise
32 or 64 bit OS: 64-bit

Hi,

I am trying to run a PowerShell script from the PrimalScript environment. Our network policy is RemoteSigned. When I try to execute the script, I am blocked by a message that says: "Your 32-bit or your 64-bit PowerShell Execution Policy will prevent your script from running properly. Would you like to change your settings now?"

When I click Yes, nothing happens. I went into Options > Script Security and changed the Security Setting to RemoteSigned but I still cannot run my script.How do I configure PrimalScript so I can execute PowerShell scripts while in the environment? I recall that clicking Yes used to bring up another window where you could change the settings but that isn't happening with this version. I can't seem to find it anywhere in Options either.

Thank you!
Rob Moorhead

DevinL
Site Admin
Posts: 1098
Joined: Mon Aug 17, 2015 2:25 pm

Re: PrimalScript PowerShell Execution Policy

Post by DevinL » Tue Feb 07, 2017 12:24 pm

We recently discovered the cause of this bug and have a fix ready for the next service release of PrimalScript.

In the meantime, please try executing Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine and see if that grants you the correct permissions.
DevinL
SAPIEN Technologies, Inc.

User avatar
robwm1
Posts: 90
Joined: Wed May 07, 2008 6:46 am

Re: PrimalScript PowerShell Execution Policy

Post by robwm1 » Tue Feb 07, 2017 12:45 pm

Hi Devin,

It looks like the command line that you gave is working. Thanks a lot for the quick response! I was blocked on a critical project.


-Rob

DevinL
Site Admin
Posts: 1098
Joined: Mon Aug 17, 2015 2:25 pm

Re: PrimalScript PowerShell Execution Policy

Post by DevinL » Tue Feb 07, 2017 12:56 pm

Not a problem, in critical situations such as this we do our best to get back as soon as possible. Keep an eye out for the next update which will include a fix to resolve this issue should it ever pop up again.

And lastly, if you have any other issues please don't hesitate to post again :)
DevinL
SAPIEN Technologies, Inc.