Script execution policy set to restricted.

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
TCCDesktopOps
Posts: 11
Joined: Tue Jan 28, 2014 4:05 pm

Script execution policy set to restricted.

Post by TCCDesktopOps » Thu Oct 24, 2019 9:32 pm

To help you better we need some information from you.

*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***

Product, version and build:Primalscript 7.4.124
32 or 64 bit version of product: x64
Operating system: Windows 10 build 1809
32 or 64 bit OS:x64

*** Please add details and screenshots as needed below. ***
Screenshot Attached.

Tool Output
** Your Microsoft Windows PowerShell Script execution policy is set to "Restricted" on 32 bit and 64 bit **
For the PowerShell cache building process to execute, your execution policy must be at least set to "RemoteSigned"
Please exit and restart the application after changing the PowerShell execution policies for 32 and 64 bit

- Just wondering if this is a problem, do I need to change something.

Group policy sets our execution policy as indicated by the following (run from both x86 and x64 powershell shells - same result.)

PS C:\WINDOWS\system32> Get-ExecutionPolicy
AllSigned

in the script security center in primalscript,
- the execution policy is the same for both x86 and x64 - allSigned.
- Trust policy is "Always run Unsigned script.
- there is a * next to current user with a note of "Current User is shared."
- I'm not sure if it is relevant, but the Script Security Center Description at the top of the window has (Non-Administrator). Primalscript is running elevated with a domain account that is in the local Administrators group.
Attachments
scriptSecurity.jpg
scriptSecurity.jpg (88.89 KiB) Viewed 687 times

User avatar
brittneyr
Site Admin
Posts: 243
Joined: Thu Jun 01, 2017 7:20 am

Re: Script execution policy set to restricted.

Post by brittneyr » Fri Oct 25, 2019 1:03 pm

Can you please provide a screenshot of the Script Security Center running as an administrator?

You can do this from the ribbon (Home -> Platform):
PSR_SecurityElevated.png
PSR_SecurityElevated.png (39.09 KiB) Viewed 661 times
Brittney Ryn
SAPIEN Technologies, Inc.

User avatar
TCCDesktopOps
Posts: 11
Joined: Tue Jan 28, 2014 4:05 pm

Re: Script execution policy set to restricted.

Post by TCCDesktopOps » Sun Oct 27, 2019 3:19 pm

Attached Screenshot as requested
Attachments
SSC-Elevated.jpg
SSC-Elevated.jpg (37.25 KiB) Viewed 606 times

User avatar
Alexander Riedel
Posts: 7129
Joined: Tue May 29, 2007 4:43 pm

Re: Script execution policy set to restricted.

Post by Alexander Riedel » Mon Oct 28, 2019 5:50 pm

The next build will treat the local policy as a warning and still execute the cache building process. Thank you for letting us know.
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
TCCDesktopOps
Posts: 11
Joined: Tue Jan 28, 2014 4:05 pm

Re: Script execution policy set to restricted.

Post by TCCDesktopOps » Wed Nov 06, 2019 11:39 pm

thankyou. :D