LCFG vs OpenDSC

LCFG is a free, GPL-licensed system for automatically installing and managing configurations across large groups of Unix machines. It targets sites where systems differ and change frequently. Administrators keep source settings on a central server; LCFG compiles them into XML profiles that clients download when changes occur. Client components react to resource changes by generating configuration files and reconfiguring related daemons. A package component aligns installed software with each machine’s profile. New machines can be installed over a network file system after source files are created, using a boot floppy or PXE. LCFG is self-hosted and agent-based, with patch management and HTTP resource transport. Listed supported platforms include Ubuntu 20.04, 22.04, and 24.04; FAQ material also names Fedora Core 3, 5, and 6 and Scientific Linux 5. Solaris support is weaker and un-packaged, Mac OS X is experimental, and the demonstration Windows client lacks real components. Documentation covers configuration, dynamic networking, and build tools.

OpenDSC is a configuration management platform for Microsoft Desired State Configuration, intended for teams managing settings across infrastructure nodes. Its Local Configuration Manager monitors system state and can automatically correct configuration drift. For centralized management, the pull server registers nodes, distributes configurations, and provides compliance reporting through a web dashboard and REST API. Configurations can be versioned, assembled into composite deployments, and parameterized by region, environment, or node. Local file-based configurations support disconnected use as well as server-driven pulls. The resource library covers Windows administration, SQL Server, and file, JSON, XML, and archive tasks across Windows, Linux, and macOS. The Resource Development Kit provides .NET libraries and tools for developing custom resources. The pull server supports OpenID Connect providers, client-certificate mutual TLS, role-based access control, and retention policies. SQLite is supported for development, while production deployments can use SQL Server or PostgreSQL. The project is MIT licensed and self-hosted. Its roadmap lists native Linux and macOS LCM services, distribution packages, and official Docker deployment as planned work.