The Buddha once said that, “A jug fills drop by drop”. In this case, the jug is universal PowerShell cmdlet coverage which is a really large jug! We’ve never been confused on this point – I’ve often referred to it as the “30 year hole” that we needed to dig ourselves out of. When PowerShell V1 shipped, it had a very small number of cmdlets. It was mostly used by advanced scripters to script their own solutions. Soon afterwards, the Exchange team released 400+ cmdlets and then it was reasonable for Exchange admins to manage their Exchange tasks. Quarter by quarter, release by release, more and more teams shipped cmdlet support or extended the cmdlet support they had already shipped and the bucket got more and more full.
That is a great bit of philosophy but the reality is that if you need cmdlet coverage and it isn’t there, you are sucking wind. If your job involves working much with PKI, you know what I mean. Today you have to run certutil.exe and parse the output or just use the GUI.
With that, it’s time for another great phrase, “Nature abhors a vacuum”. Where there is a need, the need get’s filled over time. Sadly, the OS release cadence means that vacuums can exist for a while which is why god invented the community. Quest – the superstars that brought us the first AD cmdlets and PowerGUI have just released a new set of PKI cmdlets. These are part of their QAD cmdlets so they are FREE and available without registration.
With these cmdlets, the number of things that become easy to do with PowerShell grows yet again. If it was hard to use PowerShell yesterday because you didn’t have PKI support, now it is easy. Drop by drop, the jug fills. Day be day, more and more users will find that PowerShell meets their needs.
Jeffrey Snover [MSFT]
Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx