Administering SBOS deployments
Enterprise administration covers deployment, identity, certificates, policy, applications, services, gateways, diagnostics, backup, remote access, migration, delegated administration, support, and training.
Administration workflows
Administrators manage users, groups, devices, services, applications, App Collections, gateway rules, certificates, permissions, delegated roles, deployment state, service health, backup, remote access, compatibility reviews, and support cases. Dashboards show the current state and the policy that produced it rather than requiring an administrator to reconstruct events from unrelated tools.
Deployment and updates
Fleet work includes imaging, enrollment, server-authorized provisioning, application deployment, App Collection deployment, update rings or rollout groups, staged updates, recovery planning, device state, and service state. Administrators can see which systems received a change, which systems are waiting, and which systems reported a fault.
Identity, certificates, and policy
FST ID organizes directory objects and applies native SBOS User Policies. Policies can follow users, devices, applications, services, networks, or organizational structure. Certificate enrollment, authentication, SSO, federation, RADIUS, delegated administration, and Windows-facing policy translation are managed from the same identity foundation.
Mixed environments and migration
An organization can introduce SBOS services without replacing every existing system at once. FST ID can coexist with Active Directory, LDAP, or eDirectory. Deployment and policy tools can manage supported Windows, Linux, and macOS systems through the FST client. Existing SMB, NFS, WebDAV, VPN, remote-access, and application workflows can be reviewed and migrated in stages.
Operations, support, and training
Operators review effective policy, identity events, gateway events, application lifecycle state, App Collection health, service health, diagnostics, audit records, backup state, remote-access state, and compatibility events. Support and training can be based on the same recorded system state instead of relying only on user descriptions or screenshots.