![]() ![]() The Azure DSC extension uses the Azure VM Agent framework to configure and report on DSC configurations running on Azure VMs. Fun fact, every Azure VM deployed within your subscriptions is a LCM, so DSC runs naturally, whether evoked from a pull server or through a DSC extension. The LCM runs on every target node and is responsible for parsing and enacting configurations that are sent to the node. Now, the Local Configuration Manager (LCM) is the engine of DSC. The MOF file is then parsed and executed on the target server using DSC features that know how to configure the system. In a regular configuration management flow, DSC is comprised of both a data file and a configuration file that are compiled into a text file following the Managed Object Format (MOF). Desired State Configuration is one of the tools I talk about and I personally feel it can be one of the unsung heroes of any Windows server system environment. With the cloud, many sysadmins are looking at ways to build and manage infrastructure without manual intervention. Many sysadmins have come to me over the years and asked how to manage systems at scale. Now that the troubleshooting and caveats for re-running a DSC extension have been covered, let us move into the DSC code itself. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |