# Active Directory GPO

Machines bound to an Active Directory domain can have the MyZen agents installed via Group Policy, allowing administrators to deploy across their entire network without touching individual machines.

## Step 1: Create a Distribution Point

1. Log on to the domain server as an Administrator.
2. Create a **shared network folder** (this will hold the MSI package).
3. Set share permissions to allow read access for the computers/groups that need the agent.
4. Copy the MyZen MSI file into this shared folder.
   * Download the **MSI** file from the We360.ai admin portal for silent deployment.

{% hint style="danger" %}
**Do not rename the stealth installer file.** The **stealth** installer filename is tied to your organization's license. Renaming it, or allowing extra characters to be appended (e.g. `(1)` or `(2)` from duplicate downloads), will cause the installation to fail.
{% endhint %}

## Step 2: Create a Group Policy Object

1. Open **Active Directory Users and Computers** (Start > Programs > Administrative Tools).
2. Right-click your domain name and select **Properties**.
3. Select the **Group Policy** tab and click **New**.
4. Name the policy (e.g. `We360 Agent`).
5. Click **Properties**, select the **Security** tab.
6. Enable the **Apply Group Policy** checkbox only for the groups to which this policy should apply.
7. Click **OK**.

## Step 3.1:  MSI - Assign the MSI Package

The agent should be assigned on a **per-machine** basis so it installs silently at machine startup.

1. Open **Active Directory Users and Computers**.
2. Right-click your domain name and select **Properties**.
3. Go to the **Group Policy** tab, select the GPO you created, and click **Edit**.
4. Expand **Computer Configuration > Software Settings**.
5. Right-click **Software Installation**, select **New > Package**.
6. In the Open dialog, enter the **full UNC path** to the MSI in the shared folder (e.g. `\\server\share\<installer>.msi`).
7. Click **Open**.
8. Select **Assigned** and click **OK**.
   * Alternatively, select **Published** to make the app available for all users under the AD UNC.
9. Close the Group Policy snap-in and exit Active Directory Users and Computers.

## Step 3.2:  Via Powershell&#x20;

* Please download the EXE installer from the portal
* Please download the powershell install helper script from [here](/deployment-and-it-ops/agent-deployment-hub/download-links.md#utilities).
* Please replace the `$DownloadUrl` variable in the script with the correct exe URL from [here](/deployment-and-it-ops/agent-deployment-hub/download-links.md#desktop-agents).
* If installing **stealth** app, please rename the `$InstallerName` variable to your downloaded exe name (along with .exe) part.
* Add this powershell script in startup scripts. You can also run this script directly via Group Policy.&#x20;

{% hint style="info" %}
For debugging failed installations etc, please see [Command Line / MSI / EXE](/deployment-and-it-ops/agent-deployment-hub/mass-deployment/command-line-msi.md)for more details
{% endhint %}

## What Happens Next

* When a client computer **starts or restarts**, Active Directory synchronises and the assigned package installs automatically.
* The installation is silent; no user interaction is required.
* MyZen will begin operating in Stealth mode (if the Stealth MSI was used) after the next user login. For instant start, please use the powershell script path or EXE installer via other MDM tools / manually.


---

# Agent Instructions: 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:

```
GET https://docs.we360.ai/deployment-and-it-ops/agent-deployment-hub/mass-deployment/active-directory-gpo.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.