# Activating Features on Selected Clients

The module activation override configuration enables the activation of features on specific clients.

Apply the configurations shown in the Open iT server.

In the module activation configuration file, add an override subobject after the value. The override node changes the active/inactive values written in the main node or submodule node depending on the architecture, operating system, or host.

If the main node has active value set to false, but the override is set to true, the feature will still be activated.

It has seven child options:

Child Options	Description
type	Accepts `list` as value
arch	The architecture of the client machine where the feature will be activated if set to true and deactivated if set to false
os	The operating system of the client machine where the feature will be activated if set to true and deactivated if set to false
host	The hostname of the client machine where the feature will be activated if set to true and deactivated if set to false
exclude-arch	The architecture of the client machine that will not be included in feature activation
exclude-os	The operating system of the client machine that will not be included in feature activation
exclude-host	The hostname of the client machine that will not be included in feature activation

Module Activation Override Child Options

The arch, os, and host follow this format:

<arch|os|host> : <value> : <true|false>

Example
override
{
    type=list
    os:.*:true
    arch:.*:false
    host:mnl.*:false
}

If the machine's os, host, or arch matches the specified regex pattern, then the active value of the main node will be set to the value configured on this override node.

If the child options have different Boolean values, the last one to match the regex will be the active value. In the example above, the os has a regex pattern of .* and its value is set to true, while the host has pattern of mnl.* and a value of false, then the active value will still be false if the hostname starts with mnl.

The exclude-arch, exclude-os, and exclude-host follow this format:

<exclude-arch|exclude-os|exclude-host> : <value>

Example
override
{   
    type=list
    exclude-os:win.*
    exclude-arch:.*64.*
    exclude-host:(?i)mnl.*
}

If the machine's exclude-os, exclude-host, or exclude-arch matches the specified regex pattern, then the active value of the main node will be excluded.

For example, you want to activate DSLS Autoconfigurator on all hostnames starting with mnl, except on RHEL machines and mnl1555win:

license_analyzer.conf
dsls
{
    display=DSLS
    description=Job for autoconfigurating DSLS License Servers.
    active
    {
        type=bool
        value=true
        override
        {
            type=list
            host:(?i)mnl.*:true     
            exclude-os:rhel.*
            exclude-host:mnl1555win
        }
    }         

Another example, you want to activate FreezeMonitor on all machines with Windows 64-bit operating systems:

license_optimizer.conf
 standalone
 {
	display=Optimizer Agent
	description=Job to log, suspend, or terminate idle application
	active
	{
		type=bool
		value=true
        override
        {
            type=list
            os:win.*:true 
            arch:64-bit:true
        }
	}

Save the changes in the module activation configuration file.
To immediately reflect the changes on the client machine, delete the dist-config folder and dist-config.[platform].tar.gz file in the temp directory, which is by default in C:\Program Files\OpeniT\Core\Log\temp. Then, follow the instructions in the Manual File Distribution to a Client section.