Skip to main content

Installing Comet for Enterprise (Windows)

Guide to installing Comet at large scale in Windows environments

Written by Emilio Morales
Updated over 3 weeks ago

This guide is intended for organizations that require to install Comet at large scale. If you’re looking for the individual Comet installer, you’ll find it here.

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:

  • An MDM solution

  • Access to your organization's Comet settings at perplexity.ai/account/org/comet

  • Your organization token (available from the Comet Setup page)

Overview

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

Supported Deployment Methods

  • Microsoft Intune (ADMX ingestion)

  • Group Policy (domain-joined devices)

  • Registry-based MDM (Workspace ONE, etc.)

  • Manual registry configuration

Getting Started

First, you’ll need to download the Comet installer and obtain your organization token from: 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 > Organization deployment > Download policy package files.

Installer

Description

Intel (full-installer)

Complete offline installer for Intel/AMD x64 systems

ARM (full-installer)

Complete offline installer for ARM64 systems

Intel (lite-installer)

Smaller installer that downloads components during install

ARM (lite-installer)

Smaller installer that downloads components during install

Organization Token

Your organization token is available on the Comet Setup 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:

{
  "distribution": {
    "do_not_create_taskbar_shortcut": true,
    "do_not_launch_chrome": true
  }
}

Then run the installer with:

comet_latest_intel.exe --installerdata="path/to/config.json"

Lite Installer Flags

The lite installers support the following flags:

  • --force-install - Skips screens that require user interaction

  • --skip-target-launch - Prevents Comet from launching after installation

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:

comet_installer_latest.exe --partner=partner_name

Microsoft Intune Deployment

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

File

Description

perplexity.admx

Parent template (defines the Perplexity category)

perplexity.adml

Language strings for parent template

comet.admx

Comet browser policies

comet.adml

Language strings for Comet policies

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

Step 2: Import ADMX Files into Intune

  1. Go to Microsoft Intune admin center → Devices → Configuration → Import ADMX

  2. Click Import and upload perplexity.admx first

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

  4. Wait for import to complete before proceeding

  5. Click Import again and upload comet.admx

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

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

Step 3: Create a Configuration Profile

  1. Go to Devices → Configuration → Create → New Policy

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

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

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

  5. Configure your desired policies

  6. Assign to device or user groups

Alternative: Using Settings Catalog

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

  1. Go to Devices → Configuration → Create → New Policy

  2. Select Windows 10 and later → Settings catalog

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

  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.

Using ADMX Policy

After importing the ADMX templates, configure the CloudManagementEnrollmentToken policy:

  1. In your Configuration Profile, browse to Perplexity → Comet

  2. Find and enable Cloud Management Enrollment Token

  3. Enter your organization token value

  4. Assign to device groups

Using Registry (Alternative)

You can also deploy the enrollment token via registry:

Windows Registry Editor Version 5.00  [HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Perplexity\\Comet] "CloudManagementEnrollmentToken"="YOUR-ORG-TOKEN-HERE"

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:

HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Perplexity\\Comet\\

Group Policies Deployment

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

Step 1: Install ADMX Templates

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

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

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

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

Step 2: Configure Policies

  1. Open Group Policy Management Console (gpmc.msc)

  2. Create or edit a GPO

  3. Navigate to Computer Configuration → Administrative Templates → Perplexity → Comet

  4. Configure desired policies

  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.

Using Group Policy

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

  2. Find and enable Cloud Management Enrollment Token

  3. Enter your organization token value

  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

  1. Open Comet browser on the target device

  2. Navigate to comet://policy

  3. Verify that your policies appear in the list

  4. Policies marked as "Mandatory" cannot be overridden by users

Troubleshooting

  • Policies not appearing: Run gpupdate /force or restart the browser

  • Sync delays: Allow time for Group Policy to sync across your domain

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):

HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Perplexity\\Comet\\

User-level policies:

HKEY_CURRENT_USER\\SOFTWARE\\Policies\\Perplexity\\Comet\\

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 and deploy via registry:

Windows Registry Editor Version 5.00  [HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Perplexity\\Comet] "CloudManagementEnrollmentToken"="YOUR-ORG-TOKEN-HERE"

Policy Configuration Examples

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

Example: Block URLs via Registry

Windows Registry Editor Version 5.00  [HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Perplexity\\Comet\\URLBlocklist] "1"="chatgpt.com" "2"="*.competitor.com"

Example: Block Extensions via Registry

Windows Registry Editor Version 5.00  [HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Perplexity\\Comet\\ExtensionInstallBlocklist] "1"="nkbihfbeogaeaoehlefnkodbefgpgknn"

Verifying Policy Deployment

  1. Open Comet browser on the target device

  2. Navigate to comet://policy

  3. Verify that your policies appear in the list

  4. Policies marked as "Mandatory" cannot be overridden by users

Troubleshooting

  • Policies not appearing: Restart the browser after registry changes

  • Registry policies ignored: Ensure the registry path is exactly correct (case-sensitive)

  • MDM sync delays: Allow time for your MDM to push registry changes to devices

Related Articles
Getting Started with Comet
Comet for Enterprise
Installing Comet for Enterprise (macOS)
Comet Policies and Controls
Comet Telemetry
Prerequisites
Overview
Getting Started
Silent Installation
Microsoft Intune Deployment
Group Policies Deployment
Registry-Based Deployment