SCCM for Linux EOL: The Best SCCM Linux Alternatives for Endpoint Management

Microsoft System Center Configuration Manager (SCCM), now part of Microsoft Endpoint Manager, stopped supporting Linux and UNIX endpoint management in version 1902. This deprecation of support left organizations that rely on SCCM to manage their Linux machines looking for alternatives.

In this blog, we'll cover a few options for sysadmins managing multiple operating systems to manage their Linux endpoints now that SCCM no longer supports the OS.

Does SCCM for Linux Still Work?

SCCM no longer supports Linux and UNIX endpoints. SCCM for Linux went EOL in March 2019 with the release of version 1902. Any organizations that used SCCM for Linux infrastructure management are forced to look for alternatives.

SCCM for Linux Alternatives

SCCM Linux alternatives include infrastructure automation and management software like Puppet, Ansible, Chef, Symantec, SolarWinds, and more.

SCCM for Linux EOL puts many organizations who still leverage the tool to manage multiple operating systems, including Linux, in a bit of a tough spot.

But it also presents two distinct opportunities: To migrate Linux and UNIX servers away from SCCM management and close the gaps in SCCM’s tooling; and to consolidate and simplify their infrastructure management with one single source of truth.

🤔 Need more help? Connect with the Puppet Community >>

Option 1: Pairing SCCM for Linux with Infrastructure Automation

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.

Other infrastructure automation and configuration management tools, like Ansible and Chef, have those capabilities, too.

Why Puppet is the best pair for SCCM Linux

• 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.

Option 2: Replacing SCCM for Linux with Infrastructure as Code (IaC)

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 infrastructure as code (IaC). Using IaC as an SCCM Linux alternative gives engineers and sysadmins an automated, reproducible, scalable, and self-documenting infrastructure.

Why Puppet IaC is a great SCCM Linux alternative

IaC, where the infrastructure configuration takes the form of a code file, guarantees consistent configuration across all systems and minimizes human error. With Puppet, teams don't need to know OS-specific commands or details to get their desired result. Puppet IaC lets system administrators describe the configs they want using PuppetDSL (Declarative State Language) and Puppet does the rest.

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.

Closing the Gaps Left by SCCM for Linux EOL

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. 

Puppet can help you start automating your infrastructure, and you can try Puppet Enterprise for free:

👉 Start Automating

Learn More

• Discover Puppet can be used for better infrastructure automation on Windows
• Learn how to automate Windows patching with Puppet
• Puppet + Windows: FAQs