> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/getting-started/onboarding/agent-deployment/qualys-intune-windows.md).

# Qualys - Intune Windows

*<mark style="color:$info;">Intune deployment for Windows</mark>*&#x20;

This guide walks you through deploying the Qualys Cloud Agent to Windows devices through Microsoft Intune. You’ll wrap the installer as a Win32 app and let Intune push it to your assigned device groups. The setup takes about 15–20 minutes the first time.&#x20;

### <mark style="color:$primary;">Before you Start</mark>&#x20;

Make sure you have the following ready:&#x20;

* Microsoft Intune admin access (Intune Administrator or Application Administrator role).&#x20;
* Access to CybaOps so you can open Asset Manager.&#x20;
* Target devices already enrolled in Intune.&#x20;
* A Windows PC for packaging the installer (the IntuneWinAppUtil tool is Windows-only).&#x20;

## <mark style="color:$primary;">Step 1 — Download the Installer and Copy the Install Command from Asset Manager</mark>

1. Sign in to CybaOps and open Asset Manager.
2. Click the Deploy Agent button in the top-right corner.
3. In the Deploy Agent window, set Select Agent to Qualys and Select Operating System to Windows.
4. Click Download Qualys and save QualysCloudAgent.exe into an empty local folder (for example, C:\IntuneCloudAgent).
5. Leave the Deploy Agent window open — it shows the install command with your CustomerId and ActivationId pre-filled. You’ll paste this into Intune in Step 4.&#x20;

{% hint style="warning" %}
**Keep this window open: The Deploy Agent window is the only place you can copy the install command with the correct CustomerId and ActivationId for your tenant — don’t close it until Step 4.**&#x20;
{% endhint %}

## <mark style="color:$primary;">Step 2 — Wrap the Installer as a .intunewin package</mark>

1. Download the Microsoft Win32 Content Prep Tool from GitHub: <https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool>
2. Extract the .zip into a local folder (for example, C:\IntunePrepTool).
3. Open Command Prompt and run IntuneWinAppUtil.exe from that folder.
4. When prompted, enter:

* &#x20;**Source folder** — the folder containing QualysCloudAgent.exe (e.g. C:\IntuneCloudAgent).&#x20;
* **Setup file** — QualysCloudAgent.exe&#x20;
* **Output folder** — where you want the packaged file saved.&#x20;

The tool produces QualysCloudAgent.intunewin in the output folder. This is the file you’ll upload to Intune.

## <mark style="color:$primary;">Step 3 — Add the app in Microsoft Intune</mark>

1. Sign in to the Microsoft Intune admin center at <https://intune.microsoft.com>.
2. Go to Apps → Windows → Add.
3. In the Select app type pane, choose Windows app (Win32) and click Select.
4. Click Select app package file, upload QualysCloudAgent.intunewin, and click OK.
5. On the App information page, fill in the app details (Name: Qualys Cloud Agent, Publisher: Qualys, etc.) and click Next.&#x20;

## <mark style="color:$primary;">Step 4 — Set the Program Information</mark>&#x20;

On the Program page, paste the install command from the Deploy Agent window. It looks like this, with your ActivationId in place of the placeholder:&#x20;

{% code overflow="wrap" %}

```
QualysCloudAgent.exe CustomerId={4ced42b6-21b2-e6d5-80a3-bf1f6d2597f6} ActivationId={YOUR ACTIVATION CODE} 
WebServiceUri=https://qagpublic.qg1.apps.qualys.co.uk/CloudAgent/ 
```

{% endcode %}

Use the following uninstall command:

{% code overflow="wrap" %}

```
 "%programfiles%\Qualys\QualysAgent\uninstall.exe" Uninstall=True Force=True 
```

{% endcode %}

* **Install behaviour:** System.&#x20;
* **Device restart behaviour:** No specific action.&#x20;
* **Allow available uninstall:** No.&#x20;

Click Next.&#x20;

{% hint style="info" %}
**Tip: Keep the curly braces { } around the CustomerId and ActivationId exactly as shown — Qualys requires them on Windows. Copying directly from Deploy Agent avoids typos.**&#x20;
{% endhint %}

## <mark style="color:$primary;">Step 5 — Set Requirements</mark>&#x20;

On the Requirements page:&#x20;

* **Operating system architecture:** 64-bit (tick both 32-bit and 64-bit only if you still run 32-bit Windows).&#x20;
* **Minimum operating system:** Windows 10 1607 or later (set to match your estate).&#x20;

Click Next.&#x20;

## <mark style="color:$primary;">Step 6 — Configure the Detection Rule</mark>&#x20;

On the Detection rules page:

1. Set Rules format to Manually configure detection rules and click Add.
2. Set Rule type to File.
3. Set the following values:&#x20;
   * **Path:** C:\Program Files\Qualys\QualysAgent&#x20;
   * **File or folder:** QualysAgent.exe&#x20;
   * **Detection method:** File or folder exists
4. Click OK, then Next.&#x20;

Click Next on the Dependencies, Supersedence, and Scope tags pages unless you need to set these for your environment.&#x20;

## <mark style="color:$primary;">Step 7 — Assign the app</mark>

1. On the Assignments page, under Required, click Add group.
2. Select the Entra ID group(s) you want to deploy the agent to (typically your Windows device group).
3. Click Select, then Next.&#x20;

## <mark style="color:$primary;">Step 8 — Review and Create</mark>&#x20;

On the Review + create page, check everything is correct, then click Create. Intune will start pushing the agent at the next device check-in. Devices will appear in CybaOps Asset Manager once the agent activates — usually within a few minutes of installing.&#x20;

### <mark style="color:$primary;">What the Parameters Mean</mark>&#x20;

* **CustomerId** — identifies your Qualys subscription. This is the same for every device in your organisation.&#x20;
* **ActivationId** — identifies your Qualys activation key. This is the same for every device in your organisation.&#x20;
* **WebServiceUri** — the Qualys platform the agent reports into (UK platform in this case).

### <mark style="color:$primary;">Troubleshooting</mark>&#x20;

* **App reports “Install failed” in Intune** — Check the install command — in particular that CustomerId and ActivationId are wrapped in curly braces { }. Re-copy the command from Deploy Agent.&#x20;
* **Devices not picking up the deployment** — Confirm the device is enrolled in Intune and synced. You can force a sync from Settings → Accounts → Access work or school, or via Company Portal.&#x20;
* **Agent installs but doesn’t appear in Asset Manager** — Confirm the device has internet access and that no firewall is blocking outbound HTTPS to qagpublic.qg1.apps.qualys.co.uk.&#x20;
* **“The system cannot find the file specified” in the install log** — Verify the detection rule path matches the actual install location (C:\Program Files\Qualys\QualysAgent by default).&#x20;

### <mark style="color:$primary;">Need Help?</mark>&#x20;

If the deployment still won’t complete, contact our support team and include the Intune deployment status and any device install log — that helps us identify the issue quickly.&#x20;

Please contact <support@cybaops.help> for assistance.


---

# 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.cybaops.com/getting-started/onboarding/agent-deployment/qualys-intune-windows.md?ask=<question>&goal=<endgoal>
```

`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.
