The rules of affectations deal with automatic affectation of packages. These are useful in the case of redistribution servers when we opt for a distributed OCS-NG inventory setup, but there might be exceptions to this. This is the third option of the Deployment menu (first icon of the yellow admin toolbar). By default, there is no rule. It is shown in the following screenshot:
Should we want to add a rule, the interface is intuitive. Each rule needs to have a priority. This benefits scenarios in which multiple rules are meant to be implemented. Under most circumstances, the syntax of an affectation rule is: if MACHINE VALUE equals ''='', does not equal "<>", or is LIKE, SERVER VALUE, both the MACHINE VALUE and SERVER VALUE can have one of the following options: NAME, @IP, IPSUBNET, DOMAIN, and USER.
The next screenshot shows how to define an affectation rule:
Setting up more than one redistribution server might require rules of affectations. Imagine...