This article guides you though the process of integrating PowerShell scripts in the powerful InTrust Real-Time Monitoring feature "Response Action"
With PowerShell rapidly becoming major tool for Windows administrators, it is very important to unite InTrust and PowerShell capabilities.
Other considerations:
If it appears that all settings are correct but the PowerShell script is not executing, even though the system execution policy is set to unrestricted, Windows may still block execution of the PS1 file. An Event ID 4100 may be (but not necessarily) recorded in the PowerShell event log found in Event Viewer with details similar to:
"File cannot be loaded. The file is not digitally signed. The script will not execute on the system"
To overcome this, include ExecutionPolicy parameter in the "Parameters" line to execute the script Unrestricted.
For example:
-ExecutionPolicy UnRestricted C:\myscript.ps1
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center