SUMMARY: In this blog article I talk about my presentation to the first ever Windows PowerShell user group meeting in Copenhagen.
One of the great things about PowerShell: community
One of the great things about the Windows PowerShell community is the way they all pitch together to help one another. This is expressed via Twitter, Facebook groups, Liinked in groups, blogs, forums, and even videos. The community is extremely rich. Of course when talking about the Windows PowerShell community, it is hard to talk very long without speaking of the Scripting Wife. Teresa is just awesome when it comes to community. In fact, as an Honorary Scripting Guy, she has authored nearly a dozen blog posts. As a case in point take Windows PowerShell user groups. There are dozens all over the world, and many of them can trace their existence to the Scripting Wife. Her blog post about starting a PowerShell group has been read thousands of times, and has helped many in their quest to start a new group. Last night, a new one formed in Copenhagen, and while the Scripting Wife did not have anything to do with organization, she did help obtain their first speaker — me. Windows PowerShell MVP Claus Nielsen organized the event, and it sold out all 50 available tickets. I was fortunate to be invited to speak at the first event. A picture of me during the presentation appears here.
Some of the questions and comments from my presentation
I talked about using the new features in Windows PowerShell 3.0 to manage remote systems. In particular, I talked about using the CIM cmdlets and how this is a great new interface. I discuss this topic extensively in my new PowerShell 3.0 Step by Step book by Microsoft Press
Here are some of the comments and discussions I had during and after the meeting:
1. There is some confusion when running PowerShell as least privilege. This is because many of our new cmdlets do not report that access is denied. In fact, some just do not report back ANYTHING … no error, no data. Others say stuff like provider refused to respond. This is causing many of our customers to decide to begin always running PowerShell as ADMIN, which is a bad practice.
2. Some of our customers are just now getting around to deploying Windows 7. There were questions about how best to deploy Windows PowerShell 3.0 to the Windows 7 machines.
3. Our training partners are getting LOTS of requests for Exchange PowerShell … Not just exchange, or not just PowerShell. But would LOVE to see a consolidated course offering of Exchange PowerShell.
4. Our training partners would Love to see a PowerShell certification.
5. There were several requests for a BETTER console, but not all the overhead of the full blown ISE. Would like to see only the bottom half of the ISE, for a NEW console (instead of the legacy command prompt).
So why am I listing some of the questions and comments I got? To spur you to thinking. What would you like to see in terms of documentation around using Windows PowerShell … PowerShell and what? You see Windows PowerShell can do nearly anything, all you need to know is how to do it. So ask away, let me hear from you. Who knows, I may even write an entire weeks worth of Hey Scripting Guy blog articles that talk about it. Feel free to contact me at Scripter@Microsoft.Com.