Installation on Windows
QOps ships two MSI installers:
- QOps-Setup.msi — machine-wide install (all users)
- QOpsModule-Setup.msi — per-user install (current user only)
Both installers include the netstandard2.0 (Windows PowerShell 5.1) and net8.0 (PowerShell 7+) editions.
To install QOps, download and run the appropriate MSI file.
Select for which users QOps will be installed, whether for all users or for a current user. If the user doesn't have access to installing, admin credentials will be prompted.
Then, check and verify the QOps components to be installed.
In the next step, verify the Destination Folder and click Install.
After this QOps will be installed. Depending on the required components it may take some time for downloading and installing system components.
Installation on Linux
Copy the archive with the installer to any directory on your OS and unpack the archive using the command:
tar -xvf QOps_Installer.tar.xz
Run the installer using the command:
QOps_Installer/install.sh
If you do not have powershell installed, the installer will offer to download and install the package
The installation will then proceed automatically
Next, call the PowerShell using the command:
pwsh
To set QOps configuration use First Steps guide
Installation on macOS
macOS now has an installer of its own: QOps-3.0.11-macos-arm64.pkg, for Apple silicon. It puts the module where pwsh looks for it and the Portal beside it, inside your home folder, with no administrator password.
Starting it takes one step in the Terminal, and the reason is worth stating rather than leaving to be discovered: the package carries no Apple Developer ID signature, so Gatekeeper refuses a plain double-click on a file that arrived through a browser. Either clear the download flag first and then double-click, or install without opening Finder at all.
xattr -d com.apple.quarantine QOps-3.0.11-macos-arm64.pkg
then double-click, or from the terminal:
installer -pkg QOps-3.0.11-macos-arm64.pkg -target CurrentUserHomeDirectory
Both routes install the same thing. The refusal is what an unsigned package looks like, not a damaged download, and the console step goes away once the package is signed (QOPS-406).
To set QOps configuration use First Steps guide