> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/windows-workstation-mfa/system-requirements.md). # System Requirements *** ### Supported Operating Systems * RHEL 6, 7, 8, and 9 * Ubuntu Server 20, 22, and 24 * Ubuntu Desktop/Workstation 20, 22, and 24 ### Hardware | Component | Minimum Requirement | Notes | | -------------------- | --------------------------------------------------------- | -------------------------------------------------------------- | | RAM | 16 GB | — | | Processor | 4 physical cores, Intel 8th Gen / AMD Ryzen 2000 or newer | Clock speed alone is not a sufficient indicator of performance | | Disk Storage | 256 GB SSD (NVMe preferred; SATA SSD acceptable) | Spinning HDDs are not supported for production deployments | | .NET Framework | 4.7.2 or higher | — | | VC++ Redistributable | 2015–2022 | — | ### Supported Operating Systems | Operating System | Support Status | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Windows 11 | ✅ Fully Supported | | Windows 10 | ⚠️ Currently supported. While no immediate changes are planned, support will be deprecated in a future release as Microsoft no longer provides security updates for this OS (EOL: October 14, 2025). Customers are advised to plan their upgrade path accordingly. | | Windows Server 2022 | ✅ Fully Supported | | Windows Server 2019 | ✅ Fully Supported | | Windows Server 2016 | ⚠️ Currently supported. While no immediate changes are planned, support will be deprecated in a future release as Microsoft mainstream support ended January 2025. Customers are advised to plan their upgrade path accordingly. | ### Runtime Dependencies | CP Version | Installer | .NET Requirement | VC++ Requirement | Auto-Installed | | ---------- | --------- | -------------------- | ---------------------------------------- | ------------------------- | | v2.x | MSI | .NET Framework 4.8.1 | VC++ Redistributable 2015–2022 (v14.42+) | Must be pre-installed | | v2.x | EXE | .NET Framework 4.7.2 | VC++ Redistributable 2015–2022 | Auto-installed (EXE only) | | v1.x | EXE | .NET Framework 4.6 | VC++ Redistributable 2015 | Auto-installed (EXE only) | {% hint style="info" %} MSI installer does not auto-install dependencies. Must be pre-installed or included in SCCM/Intune package. {% endhint %} *** ### Network & Connectivity Requirements #### Required Outbound Access | Destination | Port | Protocol | Purpose\*. | | -------------- | ---- | ---------------- | ------------------------------- | | \*.1kosmos.net | 443 | HTTPS / TLS 1.2+ | 1Kosmos platform authentication | {% hint style="info" %} **Note:** Firewall rules based on IP addresses are not recommended, as endpoints may change. Use FQDNs. {% endhint %} #### TLS Requirements The agent requires TLS 1.2 or higher. TLS 1.0 and TLS 1.1 are not supported. #### Proxy Configuration | Proxy Type | Supported | | ----------------------------------------- | --------- | | Unauthenticated proxy | ✅ | | Authenticated proxy (username + password) | ✅ | | PAC file proxy | ✅ | | NTLM proxy | | See Configuration Reference for configuration steps. *** ### 1Kosmos Platform Prerequisites Complete these steps in AdminX **before** deploying the agent. Installing the agent before completing these steps will cause authentication failures. * [ ] **Tenant / Community is set up** — Tenant must be provisioned. Contact your 1Kosmos representative if this has not been done. * [ ] **Active Directory** — Configured via the AdminX Broker. Users must exist in the directory before they can authenticate. See Authentication Broker. * [ ] **Windows MFA application is configured in AdminX** — Navigate to **Applications > Windows MFA** and confirm the application exists. * [ ] **At least one Adaptive Auth Journey is configured** — Users without a matching journey will see the default authentication options. See AdminX Configuration. * [ ] **Users are enrolled in their authentication method** — the mobile app must be linked for Push / TOTP / QR Code authentication; 1Key must be enrolled for FIDO; Behavior Auth + PIN enrolls at first login. *** ### Installer Selection Guide Two installer formats are available. Choose the appropriate format before you begin, switching formats later requires a full uninstall and reinstall. #### EXE vs MSI | Feature | EXE | MSI | | -------------------------- | -------------------------------------------------------------------- | ----------------------------------------- | | Recommended for | Existing v1.x deployments, manual installs | ✅ All new deployments | | Silent install | ✅ (`/SILENT`, `/VERYSILENT`) | ✅ (`/qn`) | | SCCM / Intune / GPO | ⚠️ Possible but more complex | ✅ Native support | | Auto-installs dependencies | ✅ Yes | ❌ Must be pre-installed | | Configuration method | `config.json` (v1.x) or command-line params + `REGCONFIG.ini` (v2.x) | Windows Registry via `registryconfig.ini` | | `config.json` required | v1.x only | ❌ Not used | | Supported CP version | v1.x and v2.x | v2.x only | {% hint style="info" %} **Migrating from v2.1 to v2.2?** See Upgrade & Migration. Note that `config.json` is not used in v2.x MSI installations, all configuration moves to the Windows Registry. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.1kosmos.com/authentication/windows-workstation-mfa/system-requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.