We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Improved logging in Cireson PowerShell activities (log file being used by another process)
Rather than using a file on disk where we get file locks, please consider logging in the Windows Event Logs, ideally in its own log for ease of filtering/capture.
Our auditing requirements are such that I have to write code into each script with a bunch of details about them.
$psaDisplayName invoked a PowerShell script on $env:ComputerName<br><br>Parent Work Item: $srDisplayName<br>Affected User: $affectedUserDisplayName $affectedUserUpn<br><br>Script: $psaScriptId : $psaScriptName<br>Description: $psaScriptDescription<br>Parameters: $psaScriptParameters<br><br>Results:<br>$scriptResults
If we're already improving logging, we could make the logging useful for audit purposes as well.