The Groups area shows all created configuration groups within your tenant.

Table views

The Groups table view shows the following columns.

Name

This is the name of the Group.

Configuration

This is the DSC configuration attached to the Group.

Policy

This is the LCM policy 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.

Application Role

If you enabled the application.XO Module in your tenant you are able to assign application roles to a node Group.

Actions

This column provides functions for the shown items.

Edit

The Edit function opens a pop-up with further information about the Node.

Name

You can 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 applications.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.

Download

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
[DscLocalConfigurationManager()]
Configuration LCMDefault
{

        $regKey 		= 'GUID'
        Settings
        {
            RefreshFrequencyMins            = 360;
            RefreshMode                     = 'PULL';
            ConfigurationMode               = 'ApplyAndAutoCorrect';
            AllowModuleOverwrite            = $true;
            RebootNodeIfNeeded              = $true;
            ConfigurationModeFrequencyMins  = 60;
            
        }
        ConfigurationRepositoryWeb 'infra XO'
        {
            ServerURL         			    = 'https://config.infraxo.com/api/dsc'
            RegistrationKey                 = $regKey
            ConfigurationNames              = 'ConfigurationNameReference'
            AllowUnsecureConnection			= $true

        }
        ReportServerWeb 'infra XO'
        {
            ServerURL = 'https://config.infraxo-dev.com/api/dsc'
            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

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

Delete

Deleting a node group deletes the group. Assigned LCM polices, application roles or configurations are not deleted.