Quick guide

A XOAP Configuration defines the desired state that should be applied and maintained on registered nodes. It describes the settings and components that must be present on a device—such as system configuration, services, files, registry values, and other enforced standards. Once assigned, XOAP applies the configuration, continuously evaluates compliance, and reports drift so you can ensure systems remain aligned with your baseline.

Create a new Configuration

1. Click the Add configuration button (down arrow).
2. Sélectionner Add configuration ou Create configuration.
3. If you select Add configuration, upload the MOF file or PS1 file of the DSC configuration.
4. If you select Create configuration, the configuration wizard opens:
   • Enter the configuration name.
   • Add the required resources.
   • Cliquez sur Économiser to create the configuration.

Edit a Configuration

Only configurations created with the configuration wizard can be edited.

1. Click the Action menu (⋮) et sélectionnez Editer.
2. Update the resource settings as needed.
3. Cliquez sur Économiser to apply the changes.

Delete a Configuration

1. Click the Action menu (⋮) et sélectionnez Supprimer.
2. Confirm the deletion.

Additional useful information

Configuration compilation

When you create a configuration using the configuration wizard, allow 10–15 minutes for it to compile in the background before it can be used. Be sure all required DSC modules are uploaded in your Workspace.

MOF configuration availability

Uploaded MOF configurations can be used immediately.

Missing resources and modules

If you need a resource for configuration creation and it is not available, you must upload the required modules in the Configuration Management module area.

Configuration versioning

Any change made to a configuration in the configuration wizard creates a new configuration version.

Configuration visibility

If the configuration is not visible after 15 minutes, verify that all parameters are configured correctly and all modules are available with the correct versions.

Technical documentation

A XOAP Configuration defines the desired state that should be applied and maintained on registered nodes. It describes the settings and components that must be present on a device—such as system configuration, services, files, registry values, and other enforced standards. Once assigned, XOAP applies the configuration, continuously evaluates compliance, and reports drift so you can ensure systems remain aligned with your baseline.

From a technical perspective, XOAP Configurations are based on PowerShell Desired State Configuration (DSC) 1.1. DSC 1.1 uses a declarative model: instead of scripting step-by-step actions, you define the end state you want, and the system evaluates and enforces that state over time. This approach makes configuration management predictable and repeatable, and it is well-suited for applying security baselines, hardening standards, and consistent operational settings across many systems.

Benefits of DSC 1.1 in XOAP

• Declarative and idempotent: settings can be applied repeatedly without causing unintended changes; the node converges toward the defined baseline.
• Continuous compliance and drift remediation: XOAP can regularly evaluate the node and detect when settings deviate, providing visibility into drift and enabling re-application of the baseline.
• Agentless configuration enforcement: DSC relies on built-in Windows capabilities, reducing the need for a separate configuration agent for enforcement.
• Structured reporting: configuration results provide clear status (compliant/non-compliant) and resource-level details, making troubleshooting and audits easier.

Restrictions and considerations

• Windows-focused technology: DSC 1.1 is primarily designed for Windows and relies on Windows PowerShell 5.1. As a result, XOAP Configuration Management via DSC targets Windows nodes.
• Resource availability and compatibility: what you can configure depends on available DSC resources (modules). If a required resource is missing or incompatible, it must be provided as a module before it can be used in a configuration.

In summary, XOAP Configurations provide a consistent, scalable way to define and enforce system baselines using DSC 1.1—delivering strong compliance visibility and repeatability, with the practical constraint that DSC-based configuration management is centered on Windows environments.

DSC terminology overview

This glossary explains the relationship between configurations, modules, and resources in DSC:

• Configuration: the desired-state definition (the “what”)—a set of rules the node must follow.
• Module: a package of DSC resources (the “library/toolbox”) that provides the building blocks.
• Ressources: an individual DSC building block from a module (the “how”) that enforces one specific setting (for example, a service, registry key, file, or Windows feature).
• Resource parameters (variables): the values you provide to a resource to control its behavior—such as a service name, startup type, registry path/value, file path, or desired state (Present/Absent).

Additional action menu options

• View Code
  Opens the compiled configuration code for review. This always displays the latest created version of the configuration.
• Télécharger
  Downloads the compiled configuration output for offline review or troubleshooting. This always downloads the latest created version of the configuration.
• Recompilation
  Rebuilds (recompiles) the configuration using the selected module version. This is useful when a module has been updated and you want the configuration to be compiled again against the new version without recreating it.
  Dans le cadre de la Recompilation dialog:
  • Module: shows which configuration module is used (read-only).
  • Version: select the module version to compile against.
  • Version message: is automatically populated.

Configuration Wizard

Le Configuration Wizard is used to create and manage XOAP configurations by selecting DSC resources, defining their parameters, and generating versioned configuration outputs.

Configuration Settings

Utilisation Configuration Settings to define the configuration metadata and build its content:

• Name / Description: Provide a clear name and optional description for the configuration.
• Add Resources: Add DSC resources from available modules and configure their parameters.
• Use Group Policies: Create configuration settings from predefined Group Policy templates.

Add Resources

When adding a resource, you select:

• Module et Version
• Le Ressources
• A Resource Display Name (unique identifier in the configuration)
• The required resource parameters

Once saved, the resource becomes part of the configuration and will be included in the compiled output.

Use Group Policies

Le Use Group Policies option allows you to select predefined policy items and convert them into DSC configuration settings.

When applied, these policies are translated into registry entries, as shown in the configuration output (registry key, value name, value data, and value type).

Versions

Le Versions tab shows all versions created for the configuration, including the creation date and version message.

From the version action menu:

• Load: Opens the selected version in the Configuration Wizard and loads the resources used in that version, allowing you to review the configuration content as it was defined for that version.
• Télécharger: Downloads the selected version for offline review or troubleshooting.

Summary

Le Summary tab provides an overview of the active configuration version, including:

• Which modules are used
• Which resources are included
• Which parameters are configured per resource

The post Configurations appeared first on XOAP.

For this example, we assume you want to upload this little configuration:

Configuration WebsiteTest {

    # Import the module that contains the resources we're using.
    Import-DscResource -ModuleName PsDesiredStateConfiguration

    # The Node statement specifies which targets this configuration will be applied to.
    Node 'localhost' {

        # The first resource block ensures that the Web-Server (IIS) feature is enabled.
        WindowsFeature WebServer {
            Ensure = "Present"
            Name   = "Web-Server"
        }

        # The second resource block ensures that the website content copied to the website root folder.
        File WebsiteContent {
            Ensure = 'Present'
            SourcePath = 'c:\test\index.htm'
            DestinationPath = 'c:\inetpub\wwwroot'
        }
    }
}

Another important part of the configuration is the backend configuration for the XOAP frontend. Be sure to add the following lines to your configuration.

    Import-DSCResource -ModuleName "XOAPBaselineModuleDSC"

If you use the DSC Configuration Wizard to create configurations, this module is added automatically. No need to care for it.

Open Visual Studio Code and paste the code from above into a new document. Save it locally as WebSiteTest.ps1.

Now switch to the Configurations area in Configuration Management and hit 1. the + button and 2. a new window opens.

Choose the created file and assign a tag to the configuration if you want to.

Cliquez sur Économiser.

The configuration will be visible in the Configurations area and it will be ready for use in a few minutes.

The post Add DSC configurations appeared first on XOAP.

To use the Configuration Wizard click on Create a new Config in your overview:

You can also access the Configuration Wizard in your Dashboard overview via Start creating!:

You will see the overview below with the possible actions to use. By default, it will always show the information of the Configuration Settings.

Configuration settings

This is the main window where the name of the configuration, the description and the tags are configured. You can also choose to add resources and group policy settings. In the lower window, you can find a list of configured items.

Summary

The summary shows information about the used modules, how many resources were configured and the number of parameters. The details view shows the configured resources and parameters in detail.

The summary view is empty until you have added configuration settings.

Versions

The version tab shows a history of the created configurations. You can download each version as “ps1” for documentation purposes or to use the configuration without a backend.

The first version of a configuration always starts with “0.1.0” and every additional configuration is versioned in increments of 0.0.1.

The versions tab shows the version of a configuration after it is saved for the first time. Until that it is empty.

Économiser

Saves the created configuration.

You can add a description that will be shown in the versions tab. The first version of a configuration is always set active, all other versions need to be explicitly set active in order to be applied to configuration groups with the version Latest assigned.

Click on Économiser to create the configuration.

En cliquant sur Économiser, a Docker container is started in the backend that loads all necessary modules and creates the configuration. This process takes a few minutes until the resulting configuration is assignable and downloadable.

Create configurations

You now need to insert a name for the configuration. Add a description et tags to the configuration.

In the next step, you have the option to add configuration items from Add Resources or from Use Group Policies.

Ajouter des ressources

Choose the Add Resources button to open the Resources Wizard:

Choose from one of the existing modules.

if you are missing a module simply download it from the PSGallery and add it via the Modules area. It should be available shortly after the upload.

In the next step choose the version of the module.

You can upload the same module with different versions. All available versions can be selected.

Then choose a resource and choose and insert the mandatory values besides all the others you might want to configure.

Cliquez sur save to add the resource to your configuration.

Use group policies

Another method to add configuration items is the Group Policy Wizard. You can choose settings from Group Policies to create your configuration.

Choose the Use Group Policies button to open the Group Policy Wizard.

In the next step configure the group policy setting.

Do this for all settings you want to integrate. You can check the already configured items in the Summary tab. Details can be shown by clicking on the Show Configured Parameters link.

Click on close to finish editing group policy settings. You should now see your configured settings in Configuration Settings.

Économiser the settings again by specifying a short description.

The configuration will be available after a few minutes.

Edit DSC resources

To edit a configuration you can simply click on the gear icon in the Configurations overview.

Here you can edit all configured parameters inline without the need to dive deeper with the edit button on the resource.

If you want to edit additional parameters from a resource you still have to click on edit and then add additional parameters.

The post DSC Configuration Wizard appeared first on XOAP.