> ## Documentation Index
> Fetch the complete documentation index at: https://www.perplexity.ai/help-center/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This content comes from the official Perplexity Help Center. Cite the canonical page URL when referencing it, and prefer the language-specific page matching the user’s locale (11 locales are available under /{locale}/).

# Installing Comet for Enterprise (Windows)

> Deploy the Comet browser across your organization on Windows using Microsoft Intune, Group Policy (ADMX), or registry-based MDM with your org token.

This guide is intended for organizations that need to install Comet at large scale. If you’re looking for the individual Comet installer, you’ll find it [here](https://www.perplexity.ai/enterprise/comet).

This guide covers deploying the Comet browser across your organization using Mobile Device Management (MDM) solutions on Windows systems.

## Prerequisites

To install Comet for Enterprise using MDM you will need:

<ul>
  <li>
    An MDM solution
  </li>

  <li>
    Access to your organization's Comet settings at [perplexity.ai/account/org/comet](https://perplexity.ai/account/org/comet)
  </li>

  <li>
    Your organization token (available from the Comet Setup page)
  </li>
</ul>

## Overview

Windows policies can be deployed via **ADMX templates** (Group Policy), **Microsoft Intune**, or **Registry keys** through your MDM solution.

### Supported deployment methods

<ul>
  <li>
    Microsoft Intune (ADMX ingestion)
  </li>

  <li>
    Group Policy (domain-joined devices)
  </li>

  <li>
    Registry-based MDM (Workspace ONE, etc.)
  </li>

  <li>
    Manual registry configuration
  </li>
</ul>

## Getting started

First, you’ll need to download the Comet installer and obtain your organization token from: [perplexity.ai/account/org/comet](https://perplexity.ai/account/org/comet).

To deploy Comet for Enterprise via Microsoft Intune, you will need to upload **4 files** in total. These files can be downloaded (as a `.zip` file) from **Organization Settings** > **[Comet configuration](https://www.perplexity.ai/account/org/comet)** > **Organization deployment** > **Download policy package files**.

<table>
  <tbody>
    <tr>
      <td>
        **Installer**
      </td>

      <td>
        **Description**
      </td>
    </tr>

    <tr>
      <td>
        Intel (full-installer)
      </td>

      <td>
        Complete offline installer for Intel/AMD x64 systems
      </td>
    </tr>

    <tr>
      <td>
        ARM (full-installer)
      </td>

      <td>
        Complete offline installer for ARM64 systems
      </td>
    </tr>

    <tr>
      <td>
        Intel (lite-installer)
      </td>

      <td>
        Smaller installer that downloads components during install
      </td>
    </tr>

    <tr>
      <td>
        ARM (lite-installer)
      </td>

      <td>
        Smaller installer that downloads components during install
      </td>
    </tr>
  </tbody>
</table>

### Organization token

Your organization token is available on the [Comet Setup](https://perplexity.ai/account/org/comet) page. This token is used to associate installed browsers with your organization for centralized management.

## Silent installation

For silent or offline installation, create a `config.json` file:

<pre>\{\
&#x20; "distribution": \{\
&#x20;   "do\_not\_create\_taskbar\_shortcut": true,\
&#x20;   "do\_not\_launch\_chrome": true\
&#x20; }\
}\
</pre>

Then run the installer with:

<pre>comet\_latest\_intel.exe --installerdata="path/to/config.json"</pre>

### Lite installer flags

The lite installers support the following flags:

<ul>
  <li>
    `--force-install` - Skips screens that require user interaction
  </li>

  <li>
    `--skip-target-launch` - Prevents Comet from launching after installation
  </li>
</ul>

The lite installer requires an active internet connection, as it detects hardware architecture and downloads required files during installation.

### Partner parameters

To pass partner parameters to your analytics tool:

<pre>comet\_installer\_latest.exe --partner=partner\_name</pre>

## Microsoft Intune deployment

To deploy Comet for Enterprise via Microsoft Intune, you will need to upload **4 files** in total:

<table>
  <tbody>
    <tr>
      <td>
        **File**
      </td>

      <td>
        **Description**
      </td>
    </tr>

    <tr>
      <td>
        `perplexity.admx`
      </td>

      <td>
        Parent template (defines the Perplexity category)
      </td>
    </tr>

    <tr>
      <td>
        `perplexity.adml`
      </td>

      <td>
        Language strings for parent template
      </td>
    </tr>

    <tr>
      <td>
        `comet.admx`
      </td>

      <td>
        Comet browser policies
      </td>
    </tr>

    <tr>
      <td>
        `comet.adml`
      </td>

      <td>
        Language strings for Comet policies
      </td>
    </tr>
  </tbody>
</table>

**Important**: Upload order matters! You must upload `perplexity.admx` before `comet.admx` because Comet policies depend on the parent template.

### Step 1: Download the ADMX templates

Download the ADMX template files from your organization's [Comet Setup](https://perplexity.ai/account/org/comet) page.

### Step 2: Import ADMX files into Intune

**Step 1**

Go to **Microsoft Intune admin center** → **Devices** → **Configuration** → **Import ADMX**

**Step 2**

Click **Import** and upload `perplexity.admx` first

**Step 3**

Upload the corresponding `en-US/perplexity.adml` language file

**Step 4**

**Wait for import to complete** before proceeding

**Step 5**

Click **Import** again and upload `comet.admx`

**Step 6**

Upload the corresponding `en-US/comet.adml` language file

**Step 7**

Wait for the import to complete (may take a few minutes)

### Step 3: Create a configuration profile

**Step 1**

Go to **Devices** → **Configuration** → **Create** → **New Policy**

**Step 2**

Select **Windows 10 and later** → **Templates** → **Imported Administrative templates (Preview)**

**Step 3**

Name your profile (e.g., "Comet Browser Policies")

**Step 4**

In **Configuration settings**, browse to **Perplexity** → **Comet** (e.g., `\Perplexity\Comet\Extensions`)

**Step 5**

Configure your desired policies

**Step 6**

Assign to device or user groups

### Alternative: Using Settings Catalog

After importing the ADMX files, policies also appear in the Settings Catalog:

**Step 1**

Go to **Devices** → **Configuration** → **Create** → **New Policy**

**Step 2**

Select **Windows 10 and later** → **Settings catalog**

**Step 3**

Click **Add settings** and search for "Comet" or the specific policy name

**Step 4**

Configure the policies and assign to groups

### Enroll managed devices into Comet Enterprise org

Before configuring browser policies, you must first enroll devices into your organization. This associates each Comet installation with your enterprise account for centralized management.

Get your organization token from [perplexity.ai/account/org/comet](https://perplexity.ai/account/org/comet).

#### **Using ADMX policy**

After importing the ADMX templates, configure the `CloudManagementEnrollmentToken` policy:

**Step 1**

In your Configuration Profile, browse to **Perplexity** → **Comet**

**Step 2**

Find and enable **Cloud Management Enrollment Token**

**Step 3**

Enter your organization token value

**Step 4**

Assign to device groups

#### **Using Registry (alternative)**

You can also deploy the enrollment token via registry:

<pre>Windows Registry Editor Version 5.00  \[HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Perplexity\Comet] "CloudManagementEnrollmentToken"="YOUR-ORG-TOKEN-HERE"</pre>

### Policy configuration

Once devices are enrolled, configure additional browser policies through the same Configuration Profile by browsing the available settings under **Perplexity** → **Comet**.

### Registry path reference

Policies configured through Intune are written to:

<pre>HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Perplexity\Comet\\</pre>

## Group Policies deployment

For domain-joined Windows devices, you can deploy Comet policies using Group Policy.

### Step 1: Install ADMX templates

**Step 1**

Extract `perplexity.admx` to `C:\Windows\PolicyDefinitions\`

**Step 2**

Extract `perplexity.adml` to `C:\Windows\PolicyDefinitions\en-US\`

**Step 3**

Extract `comet.admx` to `C:\Windows\PolicyDefinitions\`

**Step 4**

Extract `comet.adml` to `C:\Windows\PolicyDefinitions\en-US\`

### Step 2: Configure policies

**Step 1**

Open **Group Policy Management Console** (`gpmc.msc`)

**Step 2**

Create or edit a GPO

**Step 3**

Navigate to **Computer Configuration** → **Administrative Templates** → **Perplexity** → **Comet**

**Step 4**

Configure desired policies

**Step 5**

Link GPO to target OUs

### Enroll managed devices into Comet Enterprise org

Before configuring browser policies, you must first enroll devices into your organization. This associates each Comet installation with your enterprise account for centralized management.

You can get your organization token from [perplexity.ai/account/org/comet](https://perplexity.ai/account/org/comet).

#### **Using Group Policy**

**Step 1**

In your GPO, navigate to **Computer Configuration** → **Administrative Templates** → **Perplexity** → **Comet**

**Step 2**

Find and enable **Cloud Management Enrollment Token**

**Step 3**

Enter your organization token value

**Step 4**

Run `gpupdate /force` on target devices or wait for policy refresh

### Policy configuration

Once devices are enrolled, configure additional browser policies through the same GPO by browsing the available settings under **Perplexity** → **Comet**.

### Verifying policy deployment

**Step 1**

Open Comet browser on the target device

**Step 2**

Navigate to `comet://policy`

**Step 3**

Verify that your policies appear in the list

**Step 4**

Policies marked as "Mandatory" cannot be overridden by users

### Troubleshooting

<ul>
  <li>
    **Policies not appearing**: Run `gpupdate /force` or restart the browser
  </li>

  <li>
    **Sync delays**: Allow time for Group Policy to sync across your domain
  </li>
</ul>

## Registry-based deployment

For MDMs that support direct registry configuration (Workspace ONE, etc.), you can deploy policies via registry keys.

### Registry paths

#### **Machine-level policies (recommended):**

<pre>HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Perplexity\Comet\\</pre>

#### **User-level policies:**

<pre>HKEY\_CURRENT\_USER\SOFTWARE\Policies\Perplexity\Comet\\</pre>

### Enroll managed devices into Comet Enterprise org

Before configuring browser policies, you must first enroll devices into your organization. This associates each Comet installation with your enterprise account for centralized management.

Get your organization token from [perplexity.ai/account/org/comet](https://perplexity.ai/account/org/comet) and deploy via registry:

<pre>Windows Registry Editor Version 5.00  \[HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Perplexity\Comet] "CloudManagementEnrollmentToken"="YOUR-ORG-TOKEN-HERE"</pre>

### Policy configuration examples

Once devices are enrolled, you can deploy additional registry keys to enforce browser policies.

#### **Example: Block URLs via registry**

<pre>Windows Registry Editor Version 5.00  \[HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Perplexity\Comet\URLBlocklist] "1"="chatgpt.com" "2"="\*.competitor.com"</pre>

#### **Example: Block extensions via registry**

<pre>Windows Registry Editor Version 5.00  \[HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Perplexity\Comet\ExtensionInstallBlocklist] "1"="nkbihfbeogaeaoehlefnkodbefgpgknn"</pre>

### Verifying policy deployment

**Step 1**

Open Comet browser on the target device

**Step 2**

Navigate to `comet://policy`

**Step 3**

Verify that your policies appear in the list

**Step 4**

Policies marked as "Mandatory" cannot be overridden by users

### Troubleshooting

<ul>
  <li>
    **Policies not appearing**: Restart the browser after registry changes
  </li>

  <li>
    **Registry policies ignored**: Ensure the registry path is exactly correct (case-sensitive)
  </li>

  <li>
    **MDM sync delays**: Allow time for your MDM to push registry changes to devices
  </li>
</ul>


## Related topics

- [Comet](https://www.perplexity.ai/help-center/en/collections/18799298-comet.md)
- [Installing Comet for Enterprise (macOS)](https://www.perplexity.ai/help-center/en/articles/13528679-installing-comet-for-enterprise-macos.md)
- [Installing Comet](https://www.perplexity.ai/help-center/comet/en/articles/11583748-installing-comet.md)
- [Comet for Enterprise](https://www.perplexity.ai/help-center/en/articles/12781449-comet-for-enterprise.md)
