> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/microsoft-intune.md).

# Microsoft Intune (Windows)

Deploy We360.ai agent via Microsoft Intune — Endpoint Manager setup for mass Windows employee monitoring software deployment.

{% hint style="info" %}
This page covers the **Windows** MSI agent. To deploy the **macOS** agent via Intune (PKG app, PPPC and background-items profiles), see [macOS MDM Deployment → Microsoft Intune (macOS)](/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/macos-mdm/microsoft-intune-macos.md).
{% endhint %}

To deploy the MyZen Windows agent via Microsoft Intune, the MSI file must first be converted to the `.intunewin` format using the Microsoft Win32 Content Prep Tool.

## Prerequisites

* The MyZen Windows MSI installer downloaded from the We360.ai admin portal.
* The [Microsoft Win32 Content Prep Tool](https://github.com/Microsoft/Microsoft-Win32-Content-Prep-Tool) (`IntuneWinAppUtil.exe`).
* Access to Microsoft Endpoint Manager (Intune).
* The installer file must **not** be renamed or have extra characters appended to the filename. The stealth installer filename is tied to your organization's license.

{% hint style="danger" %}
**Preserve the organization-specific Stealth installer filename.** Its name is tied to your organization's license. Don't give a portal download or prepared installer a different name, and don't allow duplicate-download suffixes such as `(1)` or `(2)`. A generic public download must first receive your organization's filename or configuration through [Stealth installer preparation](https://github.com/zenstack-we360/documentation/tree/main/docs-we360-ai/it-ops/deployment/agent-deployment-hub/download-links.md#important-notes-for-stealth-installer-downloads).
{% endhint %}

## Step 1: Convert the MSI to .intunewin Format

Run the Win32 Content Prep Tool from a Command Prompt or PowerShell:

```powershell
IntuneWinAppUtil.exe -c <folder-containing-msi> -s <msi-filename> -o <output-folder> -q
```

| Flag | Description                                      |
| ---- | ------------------------------------------------ |
| `-c` | Folder containing the MSI file                   |
| `-s` | The MSI filename (not including the folder path) |
| `-o` | Output folder for the `.intunewin` file          |
| `-q` | Quiet mode                                       |

### Example

```powershell
IntuneWinAppUtil.exe -c C:\Users\admin\Downloads\ -s zs.msi -o .\intune -q
```

> For full command-line parameter documentation, see the README in the [Microsoft Win32 Content Prep Tool GitHub repository](https://github.com/Microsoft/Microsoft-Win32-Content-Prep-Tool).

## Step 2: Upload to Intune

1. Open **Microsoft Endpoint Manager** (endpoint.microsoft.com).
2. Navigate to **Apps > All apps > Add**.
3. Select **Windows app (Win32)** as the app type.
4. Upload the `.intunewin` file generated in Step 1.
5. Configure the install command:

   ```
   MSIEXEC /i <msi-filename>.msi /QN
   ```
6. Configure the uninstall command:

   ```
   MSIEXEC /x <msi-filename>.msi /QN
   ```
7. Set detection rules (e.g. check for the existence of `MyZenV2.exe` or `MyZenV2s.exe` in Program Files).
8. Assign the app to the appropriate device groups.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.we360.ai/deployment-and-it-ops/deploy/agent-deployment-hub/mass-deployment/microsoft-intune.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.