Adaptiva User Portal Jun 2026

Deep Report: Adaptiva User Portal 1. Executive Summary Adaptiva User Portal is a self-service web interface that complements Adaptiva’s flagship product, OneSite , an intelligent peer-to-peer (P2P) content distribution engine for Microsoft Configuration Manager (ConfigMgr, formerly SCCM). The User Portal empowers end-users to perform critical software and OS deployment tasks on their own, reducing helpdesk tickets and improving operational efficiency. By shifting control to users—within defined IT guardrails—the portal reduces network congestion, accelerates deployment compliance, and enhances the digital employee experience. 2. Product Context & Ecosystem | Component | Role | |-----------|------| | Adaptiva OneSite | P2P content distribution over LAN/WAN (no VPN backhaul) | | Adaptiva User Portal | End-user self-service layer for OneSite-managed content | | Microsoft ConfigMgr | Underlying policy, inventory, and deployment engine | | Adaptiva Client | Installed on endpoints; orchestrates P2P transfers & portal interaction | The User Portal is not a standalone product; it requires OneSite and ConfigMgr in the backend. 3. Core Functionality & User Workflow 3.1 Available Self-Service Actions

Software Requests – Install approved applications (e.g., Zoom, Slack, antivirus updates) on demand. Operating System Deployments – Initiate in-place upgrades or fresh OS installs (Windows 10 → 11, etc.) during user-chosen windows. Patch Management – Trigger missing security updates manually if automatic deadlines are missed. Device Compliance Checks – View compliance status and remediate simple issues (e.g., restart required).

3.2 Typical User Journey

User clicks desktop notification or browses to https://<portal-fqdn>/userportal . Authenticates via Azure AD / Active Directory (SSO-enabled). Sees a curated catalog of software/updates available to their device or user group. Clicks “Install” → portal sends a real-time trigger to the Adaptiva client. Client retrieves content from local peers (not a central DP) and executes installation. User receives success/failure notification with optional admin contact. adaptiva user portal

4. Architecture & Data Flow graph LR U[End User] -->|HTTPS| P[Adaptiva User Portal] P -->|API calls| A[Adaptiva OneSite Server] A -->|ConfigMgr SDK| C[ConfigMgr Site Server] A -->|Control channel| AC[Adaptiva Client on endpoint] AC -->|P2P transfer| P2P[Peer Endpoints] AC -->|Local execution| OS[Windows OS]

Portal – Hosted on IIS (Windows Server) or as a cloud service (Adaptiva SaaS option). Backend communication – Uses REST APIs and ConfigMgr WMI calls to trigger deployments. Client-side agent – Listens on a lightweight TCP port (configurable) for portal commands; pulls content via OneSite’s P2P mesh.

5. Key Features in Depth | Feature | Description | Benefit | |---------|-------------|---------| | Role-based catalog | Different software sets for Finance, Engineering, Sales, etc. | Reduces clutter, improves security | | Scheduled execution | User can defer installation to lunch break or after hours | Avoids productivity disruption | | Bandwidth capping | Portal requests inherit OneSite’s throttling policies | Prevents LAN congestion | | Offline support | If device is disconnected, request is queued and retried | Works for mobile users | | Audit trail | All user actions logged to ConfigMgr or SIEM | Compliance, troubleshooting | | Conditional access | Require device health (e.g., antivirus running) before allowing install | Reduces support calls | 6. Security Model Deep Report: Adaptiva User Portal 1

Authentication – Integrates with AD/Azure AD; supports MFA via Conditional Access policies. Authorization – Permissions are mapped from ConfigMgr collections or AD groups. No local portal accounts. Transport – TLS 1.2+ for all portal-to-agent and portal-to-server traffic. Content integrity – Uses OneSite’s native hashing (SHA-256) and Microsoft’s signing (Authenticode). Least privilege – Agent runs as SYSTEM but only executes predefined deployment types; user cannot escalate. Audit logging – Event IDs: AdaptivaUserPortal/Request/Create , /Execute , /Fail .

7. Deployment & Infrastructure Requirements | Component | Minimum Spec | |-----------|---------------| | Portal Server | Windows Server 2019+, 4 vCPU, 8 GB RAM, 10 GB storage | | Database | SQL Server Express (or full) – stores request history and catalog | | OneSite Version | 6.0+ (for User Portal API support) | | ConfigMgr Version | 1906+ (Current Branch) | | Client OS | Windows 10/11 (64-bit) with Adaptiva Client 6.x | | Network | HTTPS inbound to portal (443), outbound to ConfigMgr & endpoints | Deployment steps (high-level):

Install OneSite Server and configure P2P mesh. Deploy Adaptiva Client to endpoints via ConfigMgr. Run AdaptivaUserPortalInstaller.msi on designated server. Configure catalog mappings in OneSite Admin Console. Grant user groups access via AD. Test with a pilot group. advanced approvals require external integration.

8. Operational Benefits & KPIs | KPI | Without User Portal | With User Portal | Improvement | |-----|---------------------|-----------------|--------------| | Helpdesk software install tickets / month | 250 | 15 | 94% reduction | | Average time to install approved app | 2 days (admin scheduled) | 5 minutes (self-service) | 99% faster | | OS upgrade compliance (60-day window) | 68% | 92% | +24% | | Peak WAN utilization during patch Tuesday | 85% | 32% | 62% reduction | Source: Adaptiva customer case studies (manufacturing, healthcare, finance). 9. Limitations & Considerations

Windows-only – No macOS/Linux support (unlike some competitors like ManageEngine Self Service). Requires ConfigMgr – Not for Intune-only or third-party MDM environments. Latency for large packages – Even with P2P, a 10 GB engineering app may take 10-15 minutes over Wi-Fi. No built-in request approval workflow – Relies on ConfigMgr’s native “request-only” deployments; advanced approvals require external integration. Portal HA – No native load balancing; use standard Windows NLB or external load balancer.