http://blogs.msdn.com/powershell/archive/2008/02/07/10-cool-things-you-can-do-with-windows-powershell.aspxCheck out Jody Gilberts TechRepublic's article HERE .&#160; It is a surprisingly eclectic list.&#160; It shows that she's been kicking the tires.&#160; I can wait to see what else she comes up with. I especially liked her caveat: Note: Be careful, veryen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/powershell/archive/2008/02/07/10-cool-things-you-can-do-with-windows-powershell.aspx#7523448Thu, 07 Feb 2008 22:09:12 GMT91d46819-8472-40ad-a661-2c78acb4018c:7523448BioSensorAB » 10 Cool things you can do with Windows PowerShell<p>PingBack from <a rel="nofollow" target="_new" href="http://www.biosensorab.org/2008/02/07/10-cool-things-you-can-do-with-windows-powershell/">http://www.biosensorab.org/2008/02/07/10-cool-things-you-can-do-with-windows-powershell/</a></p> http://blogs.msdn.com/powershell/archive/2008/02/07/10-cool-things-you-can-do-with-windows-powershell.aspx#7828105Thu, 21 Feb 2008 06:10:54 GMT91d46819-8472-40ad-a661-2c78acb4018c:7828105trackerball<p>We are a Microsoft ISV, we build server products that run on the Windows Server platform. </p> <p>We are very seriously considering moving our management SDk to Powershell (right now, our SDK is COM/VB script based). I am looking to make a business case to upper management and execs to convince them to move to Powershell. </p> <p>Can you help me make my case/justification? I have seen tonnes of technical stuff on Powershell - example scripts, snippets, how tos etc.. What I am looking for is business analysis eg: How much $$ of savings can I acheive my moving to Powershell? How much faster/easier/more intuitive it is with Powershell? Looking for lots of numbers...</p> <p>Thanks. </p>