/ Guide / Endpoint standard
Laptop provisioning, defined once and repeated at every site.
Laptop provisioning is where most multi-site operations lose predictability. Each location ends up with its own build, its own peripherals and its own idea of what a working machine looks like, so a replacement is a small project instead of a routine step.
Surya Endpoint replaces that with one approved configuration per role, prepared centrally and shipped to the site ready to work.
/ The build
One approved configuration per role.
The device standard is written before any equipment moves. It names supported Windows hardware and currently supported Windows releases from the release manifest, the approved applications and peripherals from the versioned catalogue, the security baseline, the identity model, and the protected data locations that must restore onto a replacement.
Existing equipment is reused only where hardware, firmware, support life, security capability and recovery tests meet the released specification. Where it does not, it is named during the review rather than quietly carried forward. Nothing about the standard is invented per site: an improvement to the approved build reaches every site on the standard at once.
/ Staging
Prepared at the Surya RTP distribution center.
Machines are staged and configured centrally, identified by serial number, and held as inventory against the standard they were built to. Equipment for new and moving people is prepared ahead of the start date, and replacement inventory is prepared before it is needed rather than sourced after a failure.
For an operations buyer, that is the practical difference: a laptop arriving at a plant, a clinic or a building is already on the approved build, already enrolled in device management, and already tested against the recovery procedure it will need later. The customer purchases and owns the devices, including the units held for replacement.
/ Day one
Join, move, leave: one path each.
- Join. The role is selected from the standard input and role catalogue, identity and access are provisioned to the released baseline, and the prepared device is at the site before the start date.
- Move. A change of role or location reuses the same catalogue: the approved configuration for the new role is applied, and the device record follows the person.
- Leave. Access is removed through the documented path, the device is returned under custody, and the unit is erased and routed for reuse, repair or retirement.
The employment and access decisions are yours. Surya operates the supported technology foundation. The business, its applications, its AI workflows, access decisions and data authority stay with your organization. Surya performs the supported technical actions the standard defines and produces the operational record of them; the business decision about who joins, moves or leaves stays with your organization. A bespoke HR integration is not implied unless a released profile covers it.
/ What it takes
Prerequisites are confirmed in writing.
Provisioning to a standard depends on a supported Microsoft commercial tenant with an approved identity model, supported endpoint hardware, and named business, access and data owners. Each released profile has a license and control matrix, so a capability your licenses do not include is named rather than assumed. Anything that must change first is stated in writing, with the approvals your organization needs to give, before an order is accepted.