Check the beginning of the story here.
By 2005, things were changing quickly. DesktopStandard was acquired by Microsoft, and I went from watching the future unfold from the outside to helping build it from the inside.
Walking into Microsoft felt like stepping onto a moving train. PowerShell was maturing, Windows management was evolving, and the company was realizing automation wasn’t just a feature—it was a strategy. In the middle of it all sat Group Policy, the backbone of enterprise configuration.
Moving Beyond Early Automation
One of my early leaders at Microsoft was Praerit Garg (now CEO of One Identity). In 2006, he told me we had a chance to solve real customer problems—not by building bolt-ons to Windows, but by changing things from the inside.
One of the first big transitions I watched was GPOVault, our DesktopStandard product, becoming Advanced Group Policy Management (AGPM) in the Microsoft Desktop Optimization Pack. It brought real change management to Group Policy: versioning, approvals, and workflows.
From there, my world expanded quickly. My team delivered the Microsoft PowerShell Module for Group Policy, a milestone for the Windows management ecosystem. Admins finally had a clean, supported, PowerShell-native way to automate one of the most critical parts of Windows, without digging through COM objects or relying on fragile scripts. It marked a broader shift: automation was becoming an expectation.
The Rise of Scalable Windows Management
PowerShell itself was evolving just as fast. Jeffrey was driving the language forward and engaging deeply with the community. Desired State Configuration (DSC) began to take shape, pointing toward a future where configuration wasn’t just scripted but declared. And while PowerShell Core was still some time down the road, you could already hear early cross-platform ideas in the team’s conversations.
My responsibilities expanded to include early visioning and execution of what would become Microsoft Intune. It was scrappy and full of unknowns, but we were already trying to imagine device management in a world where the cloud was the center of gravity.
New Tools, New Expectations
Outside Microsoft, the ecosystem was evolving just as quickly. SDM Software pushed PowerShell deep into Group Policy internals with its Group Policy Automation Engine. Specops Software, with Thorbjörn Sjövold and team, blended Configuration Manager scenarios into Group Policy in creative ways. It was a reminder that PowerShell was a real platform the broader community could build on.
By the end of my time in Redmond, I’d lived through a transformative stretch in Windows management. PowerShell had become foundational. AGPM strengthened configuration governance. The Group Policy PowerShell module gave admins new control. Intune had taken its first steps. And across the community, the ecosystem felt alive.
Laying the Groundwork for Modern Configuration Management
Looking back, 2005 to 2011 was an acceleration point: automation stopped being niche and became expected. PowerShell grew up, DSC emerged, Intune was born, and the broader ecosystem proved innovation didn’t only come from inside Microsoft.
The next chapter would take me back to Microsoft again, into a world defined by the cloud, the Microsoft Graph, and a new generation of tools. But the seeds were planted in these years, when automation culture took root, and everything began to change.