Policies and contracts
Define once, centrally what Control does automatically on a customer's machines (checks, Windows updates, cleanup, reboots …) and tick it on the customer. New machines of the customer get everything automatically. Machines without a contract get nothing - e.g. customers without a service contract.
Everything happens on one page: Automation > Policies with the tabs Policies, Contracts and Customers. Every list has a search and filters.
Terms
| Term | Meaning |
|---|---|
| Policy | A building block with jobs, e.g. Windows · Basis Arbeitsplatz (checks + BitLocker). |
| Contract | A bundle of policies, e.g. Service contract workstation = base + updates + cleanup. A customer can have several contracts. |
| Change | A tick that differs from the contract or the customer - marked yellow, reset with ↺. |
Naming: policy Windows · Content, its jobs Content · Task, contracts Servicevertrag ….
Policies tab
The list on the left, the selected policy on the right with the buttons Edit (name, description), Deactivate/Activate (switches all jobs of the policy off or on, assignments stay) and Delete, below that
- its jobs - add them right here (New job), edit, switch on/off, delete. Whether a job applies to workstations or servers is set by the device type on the job.
- the contracts it is part of and the customers where it is active (click opens the customer).
If the same check or script for the same device type is in two policies, the page shows a warning - machines with both would get it twice.
Contracts tab
Create contracts and tick their policies. A changed contract applies at once to all its customers.
Customers tab
All customers on the left (filters With contract, Without contract, With changes), on the right:
- Tick contracts.
- Policies as a checklist: ticks come from the contracts. Untick = removed for this customer, tick = added. Changes are yellow, ↺ resets.
- Sites: expand, same checklist - now based on the customer's setting.
- Machines with own changes (click opens the machine).
- Save.
The customer dialog (Administration > Customers) only shows a summary; Edit in Policies jumps here.
On the machine
Detail panel, menu … > Policies: the same checklist. Ticks come from customer or site, the source is written out below (e.g. from customer (contract Service contract workstation)). Changes apply only to this machine. If a policy does not apply because of the device type (workstation jobs on a server), this is shown and the jobs are struck through.
What applies?
Machine before site before customer. Changes apply at once; a machine changing customer or site is picked up within a minute. Onboarding jobs (run on new host) of a policy also run when a machine joins the customer later.
Notes
- Members of a policy cannot be edited by hand (group management, group chips on the host) - use the ticks.
- Back to normal group removes all ticks of the policy; current members stay.
- Deleting a policy deactivates its jobs.
- Use existing group turns a group into a policy (members stay as machine changes).
- PBS has no policies (PBS jobs use their own groups).
- Rights: creating policies and contracts is admin-only; ticks on customer/site need Manage customers; on the machine Edit in the module. Customer-bound users only for their own customer.