Puppet Labs announces the availability of two new modules for Microsoft PowerShell Desired State Configuration (DSC) and Windows Server Update Services.
Building on Puppet Labs’ extensive Windows support, customers can now manage PowerShell DSC and Windows Server Update Service — two critical components of Windows Server environments — with Puppet Enterprise, enabling wider adoption of DevOps practices by Windows teams.
Many large enterprise organizations manage heterogeneous infrastructure with separate teams and tools to manage their Linux and Windows environments, resulting in siloed operations and tool proliferation. Puppet Enterprise provides a single solution for managing multi-platform, multi-cloud environments, including networking and storage devices. It provides a common language for development, operations, networking and storage teams that eases collaboration and sharing. By defining Windows Server infrastructure as Puppet code, Windows teams can leverage DevOps practices, such as continuous delivery, to improve the quality and speed of deployments.
"Our goal is to give everyone the power to use the best tools to manage their infrastructure, whether it's Linux, Windows, or something else," said Nigel Kersten, CIO, Puppet Labs. "By adding DSC and Windows Server Update Service support we're making it easier for teams managing diverse infrastructure to embrace DevOps practices by providing a common language and workflow to automate all aspects of the system regardless of the underlying platform."
Windows PowerShell DSC is a platform for managing and deploying changes to Windows resources and currently supports over 200 resources, including Microsoft Azure Active Directory, Microsoft Internet Information Services, Microsoft Azure, and more. The Puppet Labs DSC module enables admins to manage those DSC resources with Puppet Enterprise. When used together, customers get the best of both worlds. They can manage more of their Windows Server environments by having access to the growing body of DSC resources Microsoft provides, while leveraging Puppet’s management capabilities — central reporting, node classification, RBAC, and others — to gain full visibility and control over those resources. A preview of the Puppet Labs DSC module is currently available on the Puppet Forge and will be fully supported in Q4.
“We are delighted to collaborate with Puppet Labs on their Windows PowerShell Desired State Configuration (DSC) platform integration to empower customers to use both Windows and Linux without complex management challenges,” said Jeffrey Snover, Technical Fellow, Microsoft. “Puppet Enterprise combines rich management tools and the PowerShell DSC platform to ensure users are able to manage our rapidly expanding ecosystem of PowerShell DSC resources across Windows or Linux.”
Windows Server Update Services is a critical service for deploying the latest Microsoft product updates. The Puppet Labs Windows Server Update Service module enables admins to configure settings on client nodes to point to the correct update servers; schedule updates and their frequency; and control update policies. This module gives admins centralized control over their Windows Server Update Service configuration settings and ensures that client nodes are consistently configured, and can provide reports showing that their machine patch settings meet compliance requirements. The fully supported Windows Server Update Service client module is currently available on the Puppet Forge.
The Latest
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.