From time to time you may want to deligate control of an AD security group to an unprivileged user. Business people like this because it allows them to be in control of resources they consume, IT people like this because we don't have to handle support tickets to add people to a group. Ok, we can all agree that this may be a good idea; now lets say you want to automate this process. PowerShell has great AD integration and if that doesn't work it's just LDAP right? Well kind of, I'll show you what I mean by that.
When writing a Powershell script that will be running for an extended period of time, you should be aware of how to scope your variables to be garbage collection friendly.
PowerShell itself is written on the .Net framework butits GC is a bit different.
On the MWA Podcast when asked about a Unisaw (power saw) his response was, "Real men use alcohol powered tools."
So as a follow up to my previous post about enumerating DFS namespaces with C#, here's a PowerShell wrapper around that function. It's implemented as a PowerShell advanced function with some Get-Help documentation. I hope you find it useful. (If you don't see any code below, try refreshing, Github can be hit or miss)
At work, word has gotten out that I like to program, so being a system administrator I write a lot of PowerShell. I've used/shoehorned it into projects where it didn't really belong and have experienced some strange behavior from the PowerShell ISE that I thought I'd share before you fall into the same rabbit hole.