This area shows all created configuration groups within your tenant.

Groups overview

Table View

Here you can find the following columns.

  • Name: The name of the group.

  • Configuration: The configuration attached to the group.

  • Policy: The Life Cycle Management (LCM) policy which is attached to the group.

  • Version: As soon as you choose a configuration that was created with the DSC Configuration Wizard a version field is available from where you can choose the desired version.

Edit groups version

  • Application Role: If you enabled the application.XO module in your tenant you are able to assign application roles to a node group.

  • Node Count and Node Status: The number of nodes and their status.

Action Menu

Click on the Gear to select further functions.

Groups select action menu


This will open a pop-up with more information about the node, which are listed below.

Edit groups

  • Name: Opportunity to adjust the name of the group.

  • Configuration: This is the DSC Configuration that should be attached to the group. The DSC Configuration must be created and must be available under configurations before you can assign it to the group.

  • Policy: The LCM policy that should be attached to this group. The policy must be created before you can assign it to the group.

  • Application Role: If you have the application.XO module enabled in your tenant you can also assign application roles to a node group.

  • Selected Nodes: The selected nodes tab shows you the assigned nodes to the group. You can unassign nodes from the group here.

  • Available Nodes: The available nodes tab shows you the nodes you can assign to the group.


You can download a registration script for Windows based nodes. This script should be run on all nodes you want to register with config.XO. An example script looks like this:

#Requires -RunAsAdministrator
Configuration LCMDefault

        $regKey 		= 'GUID'
            RefreshFrequencyMins            = 360;
            RefreshMode                     = 'PULL';
            ConfigurationMode               = 'ApplyAndAutoCorrect';
            AllowModuleOverwrite            = $true;
            RebootNodeIfNeeded              = $true;
            ConfigurationModeFrequencyMins  = 60;

        ConfigurationRepositoryWeb 'infra XO'
            ServerURL         			    = ''
            RegistrationKey                 = $regKey
            ConfigurationNames              = 'ConfigurationNameReference'
            AllowUnsecureConnection			= $true

        ReportServerWeb 'infra XO'
            ServerURL = ''
            RegistrationKey   = $regKey
            AllowUnsecureConnection = $true
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v2.0.50727' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12

winrm quickconfig -quiet
Enable-PSRemoting -Force -SkipNetworkProfileCheck
Set-Item -Path WSMan:\localhost\MaxEnvelopeSizeKb -Value 16384
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 4096

Write-Warning 'Restarting WinRM'
Restart-Service WinRM -Force

Set-DSCLocalConfigurationManager  -Path .\LCMDefault\ -Verbose
Update-DscConfiguration -Verbose -Wait


Deleting a node group deletes the group. However, assigned policies, application roles or configurations will not be deleted.