This year I attended the PowerShell Conference EU in Hannover and I decided to write a summary about this event. For this summary, I will only mention the key takeaways for me. Please feel free to add comments if you think something important is missing.
The keynote from Jeffrey Snover was about the state of the union. This presentation was the perfect beginning for the PowerShell Conference Europe. The organization did well on picking the sessions because everything told during the keynote came back during the rest of the conference. The big question everybody wants to know, is PowerShell done?
The answer is yes and no!
PowerShell for Windows is done, PowerShell has achieved critical mass as a general purpose Windows scripting tool. But for the cloud it’s just the beginning, managing a cloud asks different things so for that there is PowerShell Core. The mission of PowerShell Core is to be the connector of the Hybrid Cloud. Powershell Core should enable the IT Pro to connect from any client to manage any server running on any cloud or to connect on-premise using any hypervisor with any storage and any networking.
Now that PowerShell is done for Windows, I noticed that the PowerShell team starts to give more focus on the people working with the tools. The conference included more presentations about the DevOps way of working and thinking then PowerShell conferences in the past.
Jeffrey said: “PowerShell is done for Windows”. What this means is that PowerShell shipped with Windows will receive only incremental changes in the future. On the other side, it’s likely to have more transformative changes this is because the cloud ask different things from the IT Pro. This way of working asks a new way of thinking and that’s going to be hard. But it is something we must do if we want to bring more value to our company’s. We will if not already start working in a DevOps way. Like Kenneth Hansen mentioned, “DevOps is either gonna happen with you or to you”.
What transformative changes is the Windows IT Pro facing:
- Moving away from GUI to Automation (at least I hope 😊)
- Instead of working in silos company’s wants the IT Pro to manage the full portfolio
- Traditional IT becomes DevOps
- On Premises becomes the cloud
The most important transformative change on this conference is the fact that PowerShell is now available on Linux. Microsoft have big expectations for this one and its statement is clear.
“Linux is going to be a first-class citizen in a Microsoft world”
To support this statement, the PowerShell team made it possible to connect from a Windows machine to a Linux machine. At this moment the 2 options to connect are with SSH or WinRM.
To support this scenario even more, Microsoft introduced VSCode or even more important Editor Language Services. This is all about one single tool to complete all your tasks. In the future, it will probably be possible to run any editor of choice in VSCode like Sublime and VI.
Another important announcement is that Microsoft is going to use Swagger. Swagger is an open source project to autogenerate Cmdlets from a Rest API.
Cloud command console
Also, the Cloud Command Console well be available in the next weeks. This is an Azure console for Bash and PowerShell.
The PowerShell team did a great job on security in the latest versions of PowerShell. It even seems that Hackers nowadays don’t use PowerShell anymore because with other tools its easier to not get caught.
Tips for securing a PowerShell deployment:
- Command line logging
- Full transcription
- Install v5 and uninstall v2!
- Windows 10
Because it’s not always possible to uninstall PowerShell v2 here is a good blog post from Lee Holmes what to do else. http://www.leeholmes.com/blog/2017/03/17/detecting-and-preventing-powershell-downgrade-attacks/
Some important extra announcements:
- The PowerShell team is working on a way to provide Parallel execution in native PowerShell.
- To provide users a GUI tool on machines with only .Net Core there is a module Phosphor.
- The support of Classes is just about the level of class support as python.
- When configuring JEA this needs to be the only entrance to a system.
- Microsoft is working on a new LCM that makes it possible to have multiple LCM instances.
Its also important to mention, that the PowerShell team will focus more on building services and especially Azure services in the future.
It’s always great to meet people with the same passion, so if you’re a PowerShell enthusiast make sure you attend next year’s conference.