Last updated
Hosts network licenses for QIAGEN CLC applications
$ winget install --id QIAGEN.CLCNetworkLicenseManager --exact --version 5.5.5Run in Command Prompt, PowerShell, or Windows Terminal. Prompts for any agreements.
CLC Network License Manager uses EXE. The silent install switches are -q -Dinstall4j.suppressUnattendedReboot=true.
CLCNetworkLicenseManager_5_5_5_64.exe -q -Dinstall4j.suppressUnattendedReboot=true
See the full silent install reference for CLC Network License Manager →
For Intune admins
Automated application patching for Microsoft Intune. Pckgr keeps a curated library of 1,000+ apps continuously up-to-date in your tenant via Microsoft Graph - no manual repackaging, no chasing vendor sites.
Start free 30-day trialNo credit card required.
The CLC Network License Manager hosts network licenses for QIAGEN CLC applications.
Network licenses are checked out when client software starts running, and are checked back in when the software is closed. This allows a single license to be used on different machines at different times. For modules (commercial plugins), a network license is only checked out at the time the first tool delivered by that module is launched in a given Workbench session. If people wish to run a licensed application while offline, they can borrow a license for a certain period of time.
Access to and reserving of licenses for particular users or machines can be configured, as can the maximum number of licenses that can be used by certain users, groups, or sets of machines, and the maximum length of time a license can be borrowed.
Network licenses are required if the CLC software is installed on systems with more than 64 cores, or if the software will be accessed remotely
| Architecture | Type | Scope | Install | Download |
|---|---|---|---|---|
| x64 | EXE | machine | Direct |
Copy a command tailored to that specific architecture, type, and scope - useful when winget would otherwise pick a different default.
No known CVEs for CLC Network License Manager.
Coverage is best-effort and depends on a winget package mapping to an NVD CPE entry. Absence here is not a guarantee of safety.