Know your fleet. Understand your contract.

01

Start with an approved company

A company administrator completes verification and requests a sales-approved enterprise contract. An independent platform owner records the service period, purchased capacity and agreed pricing. A subscription does not grant application or agent execution permission.

02

Count computers once

Each registered computer uses one machine identity. Multiple employee accounts and Windows SID bindings on that identity do not consume additional computer seats. Preserve the identity during a controlled reinstall; retire old identities when replacing equipment. Capacity is reserved at inventory registration, before Windows installation.

03

Separate inventory from protection

Registered means an inventory identity exists. Online means a recent authenticated heartbeat was received. Reported software version is device-reported information. None of these alone proves that every Windows sign-in path is protected.

04

Understand the estimate

The contract may specify an employee rate, a computer rate or both for a monthly or annual period. The estimate uses purchased quantities, not the number currently online. Currency, rates and contract version must match. Taxes, proration, invoicing and payment collection require separate commercial arrangements.

05

Organize your deployment

Within a company, group computers by site, department and device group. These labels help operate the fleet; they do not create new tenants or grant administrators broader access.

06

Pilot before expansion

Enroll employee authenticators first. Test on a separate recovery-capable computer with an approved package and a reachable trusted HTTPS service. Validate logon, unlock, refusals and recovery before expanding. Production machine renewal, signed distribution and complete Windows mediation remain release requirements.

Company topology

1. Company workspace and contract
2. Sites, departments and device groups
3. Distinct computer identities
4. Employee account bindings and authenticators
5. Authenticated heartbeat, approval events and audit evidence

Topology labels describe organization. Authorization stays bound to the company tenant and explicit roles.