xPSDesiredStateConfiguration

repository·main·Indexed 42 days ago

https://github.com/dsccommunity/xpsdesiredstateconfiguration

A community-driven extension of PowerShell Desired State Configuration (DSC) resources. It provides enhanced features, bugfixes, and new resources beyond the standard Microsoft PSDscResources module, including resources like xService, xRegistry, and xWindowsFeature. It is automatically tested on PowerShell 5.1 with Windows Server 2016 and 2019, with specific support for Nano Server.

Tokens
5.1K
Snippets
7
Records
43
Agent score
52%

What's inside xPSDesiredStateConfiguration

  1. Overview of xPSDesiredStateConfiguration

    main

    The xPSDesiredStateConfiguration module is a community-supported collection of Desired State Configuration (DSC) resources. It contains the same resources as the Microsoft-supported PSDscResources module but includes additional features, bugfixes, and new resources.

    Key distinctions:

    • Prefix 'x': Some resources use an 'x' prefix (e.g., xService) to avoid conflicts with built-in Windows PowerShell resources. This prefix does not imply the resource is experimental.
    • Lifecycle: Unlike PSDscResources, which is maintained by Microsoft as a 1:1 replacement for built-in resources, xPSDesiredStateConfiguration is actively developed by the DSC community with a focus on new features.
    • Compatibility: Automatically tested on PowerShell 5.1 with Windows Server 2016 and 2019. While it may work on PowerShell 4 or other operating systems, compatibility is not guaranteed.
  2. Use the DSC_xWindowsOptionalFeature resource to manage Windows optional features

    main

    The DSC_xWindowsOptionalFeature resource allows you to enable or disable Windows optional features via Desired State Configuration (DSC). This resource is compatible with Nano Server.

    Requirements

    To use this resource, ensure the following conditions are met:

    • The target machine must be running a Windows client operating system, Windows Server 2012 or later, or Nano Server.
    • The target machine must have access to the DISM PowerShell module.