The document discusses the evolution of automation on Windows Server, Microsoft's involvement with open source, and how Chef can be used with Microsoft Azure and Windows. It outlines how Windows PowerShell has improved automation capabilities over time, and how Microsoft contributes to open source projects. It then describes how Chef can be used to provision Azure VMs, leverage test-kitchen for testing, and manage Windows nodes and workstations, while noting some challenges of remote management, security contexts, and performance.

1. Chef, Microsoft, and Community
Steven Murawski

2. Chef, Microsoft, and the Community
• The Evolution of Automation on Windows Server
• Microsoft and Open Source
• Chef and Azure
• Chef and Windows

4. The Evolution of Automation on Windows Server
• Before 2006, things were bad. Cmd.exe and VBScript were the defaults in
automation.
• 2006 - Windows PowerShell V1 shipped
• 2009 – Windows PowerShell V2 shipped
• 2012 – Windows PowerShell V3 shipped
• 2013 – Windows PowerShell V4 shipped
• 2015 – Windows PowerShell V5 production preview

5. Microsoft and Open Source

10. A couple of handy links
• https://microsoft.github.io
• https://github.com/powershell

12. Chef and Azure

13. Chef and Azure
• Chef Azure VM Agent Extension
• Chef Provisioning
• Test-Kitchen
• Knife Azure

14. Chef and Windows

15. Chef on Windows as a Managed Node
• Traditional command line apps
• PowerShell
• Desired State Configuration
• Challenges:
Remote Management
Security Contexts
Performance

16. Chef on Windows as a Workstation
• ChefDK
Chocolatey Packages
chef shell-init powershell
PowerShell wrappers for chef, chef-client, and knife
• Test-Kitchen
kitchen-dsc
kitchen-pester
kitchen-hyperv