No more SCCM support for your Linux and UNIX servers? Puppet can help

See more posts about: Windows

Starting in version 1902, Microsoft announced the deprecation of Linux and UNIX client support in System Center Configuration Manager (SCCM).

What does this mean as a system administrator responsible for managing multiple operating systems?

At this crossroads, Windows and Linux teams can leverage Puppet to:

  • Migrate Linux and UNIX servers away from SCCM management and close the gaps in SCCM’s tooling.
  • Consolidate — with Puppet teams can manage all types of infrastructure with one single source of truth.

Let’s dive into option 1

Why change what’s already working? SCCM is already used successfully by many Windows teams for operating system deployment, as well as to review, approve, and orchestrate patches across Windows systems.

But Puppet can manage Linux, UNIX, and Windows environments. Multi-OS teams can ensure consistency by using Puppet Enterprise to configure and manage all systems in an automated, predictable, and scalable way. Puppet also provides the benefit of not having to rely on a GUI to manage configurations. Teams can use one centralized repository to test changes quickly. Puppet’s continuous infrastructure management complements SCCM’s patch management and initial provisioning of the Windows operating system.

In successful deployments, Windows teams can use SCCM to get their systems booted and on the network and then use Puppet to easily automate their infrastructure and bring all systems to their desired configuration state.

Let’s take a look at option 2

People like getting work done as quickly and efficiently as possible. Managing multiple operating systems with different configuration management applications means learning and paying the overhead of having multiple code bases.

Instead of using one-off scripts or manually making infrastructure changes, system administrators can manage their entire IT infrastructure using Puppet’s infrastructure as code (IaC) model. IaC, where the infrastructure configuration takes the form of a code file, guarantees consistent configuration across all systems and minimizes human error. System administrators describe the configs they want using Puppet Declarative State Language (DSL) and Puppet does the rest. Teams do not need to know OS-specific commands or details to get their desired result. IaC results in an automated, reproducible, scalable, and self-documenting infrastructure.

Puppet also has a great browser-based UI for configuration and setup tasks that make small changes as simple as point and click. For more power and control, teams can use the robust command-line interface of Puppet to automate configuration management.

Puppet can perform most of the tasks that SCCM is known for such as patching, reporting, and profile migration. Teams can get up and running quickly by exploring the Puppet Forge, a library containing preexisting IaC templates such as WSUS for patch management. Teams are not limited to running one type of platform under the Puppet umbrella and can work together to manage any platform seamlessly with a single language.

So now what?

If your Linux and UNIX systems were dropped by SCCM, use this time as an opportunity to formulate a new strategy for managing your infrastructure with Puppet. If you’re like many companies and manage a variety of systems, you can use Puppet to manage your systems and save on the overhead of managing these environments separately.

No matter the case, with Puppet as the unifying abstraction, your Windows and Linux teams do not need to worry about the platform-specific tools and the intricate details of managing different platforms. Get started with Puppet Enterprise and start automating your infrastructure today!

Tara Krishnan is an associate engineering product manager at Puppet.

Learn more

Puppet sites use proprietary and third-party cookies. By using our sites, you agree to our cookie policy.