Windows 10: Powershell script, custom module call crashing session

Hey,Currently running into an issue with a custom PowerShell script that I own.The script has been in production almost daily for the past 4-5 years but the past couple weeks it's been erroring out on me for reasons I don't understand. The script in question is an AD mgmt script which checks 800+ users and updates, deactivates and creates users based on a master data file which is imported from our payroll system.The script crashes, along with the PS session every time when the script hits a specific point, which is running a custom module that runs through and deactivates a list of AD users t

:)

 

PowerShell script run - Cmdlets

As SQL-IP and Cosmos are still internal to Microsoft, I wonder why you are not simply contacting the person who provided you with the scripts.

For point 1: see PowerShell: Bypass ExecutionPolicy to run downloaded scripts

For point2: this is specific to the script: "Cosmos.Document" is probably in a module which is not found.

 

PowerShell scripts not working with Call operator

Hi,



Thank you for writing to Microsoft Community Forums.



I understand that you are facing issues while developing a PowerShell script using the Call operator. I would suggest you to refer the articles

The Windows PowerShell ISE.



However, as the issue is related to developing PowerShell scripts, I would suggest you to post your query on

MSDN forums, where we have expertise and developers who are well equipped with the knowledge of developing PowerShell scripts in Windows.



Regards,

Prakhar Khare

Microsoft Community – Moderator

 

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?