I've seen lots of guidance on storing credentials for consumption by a PowerShell script. ConvertTo/From-SecureString seems to be the most common method, but has some serious limitations when it comes to sharing credentials between computers. In this post I'll introduce a PowerShell module I wrote which will allow you to store self-signed certificate encrypted credentials in a SQL database and consume them at a later date or from another machine.
Based on some of my experiences in the field, I saw a need for a tool to view the relationships between collections and their limiting collections. This tool should assist you in seeing a big picture of how your collections relate to one another.
Collections. There is a certain art to organizing them. There is also a science behind how the update schedules work and how you can use them to your advantage - or how you might be using them to your disadvantage. That's why it's important to know the relationship between collections and their limiting collections.