Inside Activate
Services
Computer-based Services
7 min
computer based services are services that are ordered for a user but require an associated computer in order to be provisioned the service represents access or capability requested by a user, while the selected computer defines where the service is deployed the associated computer is used as the deployment target for computer based group membership, sccm deployments, or other device based provisioning mechanisms supported by activate overview of computer based services computer based services differ from user based services in that provisioning actions are performed against a computer object rather than directly against a user account, even though the service itself is still requested on behalf of a user a computer must be identified before provisioning can occur, ensuring that deployments are applied to the correct device computer selection requirement a computer based service is always associated with both a user, who is requesting the service a computer, which is the target for deployment a computer must be identified before provisioning can occur depending on configuration and request method, computer selection may occur during the initial service order after approval but before provisioning automatically through entitlement based deployment provisioning is deferred until a valid computer association is established decide later behaviour the decide later option controls when the computer must be selected when decide later is enabled the service can be ordered and approved without selecting a computer provisioning is deferred the service remains pending until a computer is selected when decide later is disabled a computer must be selected as part of the manual order process the service cannot proceed without an associated computer the availability of the decide later option is controlled by service configuration ordering paths and behaviour computer based services may be requested through multiple paths manual ordering via order service suggest access automatic deployment via entitlements when services are added via suggest access or deployed automatically through entitlements, computer capture follows the same process as decide later provisioning is deferred until a computer is identified provisioning mechanisms computer based services can perform provisioning actions against both the user and the computer this allows a single service to grant the user access to an application or resource deploy required software or configuration to the selected computer provisioning behaviour is controlled by service configuration user based provisioning user based provisioning actions are applied to the user who requested the service common examples include adding the user to a security or application access group granting entitlements required to access the application these actions ensure the user has the appropriate permissions once the application is available computer based provisioning computer based provisioning actions are applied to the selected computer common examples include adding the computer to a computer based group triggering sccm or other device deployment mechanisms applying device specific configuration or automation these actions ensure the application or service is deployed to the correct device service definition parameters computer based service behaviour is controlled by parameters defined on the service definition common parameters include usergroup – controls group membership or entitlements applied to the user computergroup – controls group membership or deployment actions applied to the computer by combining user and computer provisioning within a single service, activate ensures that access and deployment remain aligned key considerations when designing and configuring computer based services ensure users understand when computer selection is required validate behaviour across all ordering paths confirm downstream systems can correctly process the selected computer consistent configuration helps provide predictable provisioning outcomes across manual and automated requests