PowerShell-Scripts VS platform-compat

We're using the Remote Support API to manage create, delete and mutate Session Policies, Group Policies, Jump Groups and Jump Clients based on another internal datasource, here is a function I've made to interface with it using PowerShell: https://github.com/RobinBeismann/PowerShell-Scripts/blob/master/API-Functions/Invoke-BomgarQuery.ps1 It takes care of Authentication and Pagination.

I tend to just write one function per API I query that has pagination builtin, some APIs just return them as Headers so you can't use Invoke-RestMethod and have to fallback to Invoke-WebRequest. Have a look at the existing ones here: https://github.com/RobinBeismann/PowerShell-Scripts/tree/master/API-Functions

This is not how orchestration groups work, you need to define your own pre- and postscripts for it. Here are some examples for Hyper-V (FOCM for Failover Clusters), SHHV for single hosts. Make sure to set your timeout values high enough and test on non productive clusters first. https://github.com/RobinBeismann/PowerShell-Scripts/tree/master/SCCM/OrchestrationGroups

There you go. :) https://github.com/RobinBeismann/PowerShell-Scripts/blob/master/SCCM/Get-OSInstallDisk.ps1

DotNet offers the SecureString class to keep a string encrypted in Memory, but as long as the OS does not natively support this concept, the only advantage is that it resides in memory for a shorter time, the disadvantage is that SecureStrings are easier to search for.

Note the KeePass's resistance to the attack mentioned depends on the security of .NET's secure string, which, here's what Microsoft has to say about it (https://github.com/dotnet/platform-compat/blob/master/docs/D...)

As for KeePassXC, last I checked it didn't even bother.

TIL. Looks like the deprecation note recommends MailKit.

Well of course, but it does have to be passed to the module that generates the hashes AD uses in the first place. And as I said, the standard password reset screen is bound to store the password in plain text somewhere as well.

This won’t help you with your question, but I figured I should warn against using send-mailmessage.

points you here.

Some of the reasons for not using Hashtable or other non-generic collection types are outlined here. That's why Microsoft doesn't recommend their usage in new implementations across all of its API documentation.

And if you really want to be secure you need to something better than a SecureString: https://github.com/dotnet/platform-compat/blob/master/docs/DE0001.md