Windows 10: How to turn on or off Windows PowerShell script execution

If you want to turn on or off Windows PowerShell script execution in Windows […]

This article How to turn on or off Windows PowerShell script execution first appeared on TheWindowsClub.com.

read more...

 

Powershell Scripts in the Windows 10 OS and script execution policy of "Allow only Signed scripts"

We have the group policy " Turn on Script execution" enabled and set to "Allow only Signed scripts".

Will this affect the powershell scripts used in the Windows 10 operating System or does windows have something inbuilt that overrides the settings we apply. I'm thinking that it would block even the W10 built in scripts.

An example of what I am talking about are the 246 .ps1 files in the various diagnostic directories in c:\windows\diagnostics\system\ . our diags never come back with issues even when deliberately disabling components before running.

other areas that Powershell scripts live that I have found with a quick search -

C:\Windows\WinSxS\wow64_microsoft.powershell.odatautils_31bf3856ad364e35_10.0.17763.1_none_d60dcab1d9234fab

C:\Program Files (x86)\WindowsPowerShell\Modules\Microsoft.PowerShell.Operation.Validation\1.0.1\Diagnostics\Comprehensive

C:\Program Files\WindowsPowerShell\Modules - various folders in here.

Do we need to sign all powershell scripts that come with the OS?

Does Microsoft have a method of doing this?

Is there a list of script files that come with the OS so we don't just do a sign all approach, then find we have signed malware files.

we could probably configure something in the build task sequence to sign what is there initially. Is there any plan in place for Microsoft to start signing their scripts?

Will this be an ongoing process as updates are applied and files replaced, do we need to have a process in place to sign all PS1 files in the OS?

 

Powershell Scripts in the Windows 10 OS and script execution policy of "Allow only Signed scripts"

OK, thanks. I have asked the question in Technet.

Here if anybody in future is looking - Powershell Scripts in the Windows 10 OS and script execution policy of "Allow only Signed scripts"

 

Issue faced when PowerShell script executed through SQL Server Agent Job

I have a PowerShell script that searches for an excel file at a particular location, if found copies it as a CSV file to another location.

This CSV is used as a source in ADF - Copy Activity.

This script is not interacting with any database, nor performing any db tasks - just reading an excel and converting it to CSV at particular location.

It is working fine as intended, when executed through PowerShell ISE, but when I scheduled it as a SQL server agent job it is not doing anything. The job successfully as per the message in Job History, but it does not do anything. The message says :

=====================================================================================

Message

The job succeeded. The Job was invoked by User PMCI\VermaRachna. The last step to run was step 1 (Load_Radiotherapy_Machine_Utilization_File_Org_Src).

Message

Executed as user: PMCI\SVC_DASH_SQLDevAGT. The step did not generate any output. Process Exit Code 0. The step succeeded.

=====================================================================================

I have scheduled the Job with type as "Powershell" and the script code is pasted in Command area of the Job Step.

Since I am not getting any error message how do I know what is the issue due to which script is not doing anything when run through SQL Server agent job. Can some one help with this please. I can share the script code if required.