Essentially, because Syslog Server NG uses PowerShell Runtime libraries for the scripting engine (vs. relying on preinstalled powershell.exe / pwsh.exe), it also has to use .NET libraries for .NET Framework integration. Currently, only the .NET 8 Runtime libraries are installed/referenced. Unfortunately, .NET 8 Runtime is missing several assemblies which native Windows PowerShell modules require in order to run correctly (e.g. ActiveDirectory). At minimum, the WCF (Windows Communication Foundation) assemblies are missing (see https://dotnet.microsoft.com/en-us/platform/support/policy/corewcf and https://dotnet.microsoft.com/en-us/platform/support/policy/wcf-client ).
Developing scripts using Windows PowerShell or PowerShell 7 for Windows for developing scripts can lead to non-functioning scripts in Syslog Server NG, as these both have the required assemblies available and Syslog Server NG does not. Windows PowerShell has the WCF built in and PowerShell 7 for Windows includes the full .NET 8 Framework (including WCF and possibly more).
For full functionality, Syslog Server NG should have the same .NET libraries/assemblies installed as PowerShell 7 for Windows; or at minimum the WCF assemblies.
NOTE: I have made a post in the Forums ( PowerShell script requires missing .NET packages ) explaining the problems. I also opened a support ticket (#01821772) regarding it.
