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.
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)
Windows policies can be deployed via ADMX templates (Group Policy), Microsoft Intune, or Registry keys through your MDM solution.
Microsoft Intune (ADMX ingestion)
Group Policy (domain-joined devices)
Registry-based MDM (Workspace ONE, etc.)
Manual registry configuration
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 |
Your organization token is available on the Comet Setup page. This token is used to associate installed browsers with your organization for centralized management.
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"
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.
To pass partner parameters to your analytics tool:
comet\_installer\_latest.exe --partner=partner\_name
To deploy Comet for Enterprise via Microsoft Intune, you will need to upload 4 files in total:
|
File |
Description |
|
|
Parent template (defines the Perplexity category) |
|
|
Language strings for parent template |
|
|
Comet browser policies |
|
|
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.
Download the ADMX template files from your organization's Comet Setup page.
Go to Microsoft Intune admin center → Devices → Configuration → Import ADMX
Click Import and upload perplexity.admx first
Upload the corresponding en-US/perplexity.adml language file
Wait for import to complete before proceeding
Click Import again and upload comet.admx
Upload the corresponding en-US/comet.adml language file
Wait for the import to complete (may take a few minutes)
Go to Devices → Configuration → Create → New Policy
Select Windows 10 and later → Templates → Imported Administrative templates (Preview)
Name your profile (e.g., "Comet Browser Policies")
In Configuration settings, browse to Perplexity → Comet (e.g., \Perplexity\Comet\Extensions)
Configure your desired policies
Assign to device or user groups
After importing the ADMX files, policies also appear in the Settings Catalog:
Go to Devices → Configuration → Create → New Policy
Select Windows 10 and later → Settings catalog
Click Add settings and search for "Comet" or the specific policy name
Configure the policies and assign to groups
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.
After importing the ADMX templates, configure the CloudManagementEnrollmentToken policy:
In your Configuration Profile, browse to Perplexity → Comet
Find and enable Cloud Management Enrollment Token
Enter your organization token value
Assign to device groups
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"
Once devices are enrolled, configure additional browser policies through the same Configuration Profile by browsing the available settings under Perplexity → Comet.
Policies configured through Intune are written to:
HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Perplexity\Comet\\
For domain-joined Windows devices, you can deploy Comet policies using Group Policy.
Extract perplexity.admx to C:\Windows\PolicyDefinitions\\
Extract perplexity.adml to C:\Windows\PolicyDefinitions\en-US\\
Extract comet.admx to C:\Windows\PolicyDefinitions\\
Extract comet.adml to C:\Windows\PolicyDefinitions\en-US\\
Open Group Policy Management Console (gpmc.msc)
Create or edit a GPO
Navigate to Computer Configuration → Administrative Templates → Perplexity → Comet
Configure desired policies
Link GPO to target OUs
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.
In your GPO, navigate to Computer Configuration → Administrative Templates → Perplexity → Comet
Find and enable Cloud Management Enrollment Token
Enter your organization token value
Run gpupdate /force on target devices or wait for policy refresh
Once devices are enrolled, configure additional browser policies through the same GPO by browsing the available settings under Perplexity → Comet.
Open Comet browser on the target device
Navigate to comet://policy
Verify that your policies appear in the list
Policies marked as "Mandatory" cannot be overridden by users
Policies not appearing: Run gpupdate /force or restart the browser
Sync delays: Allow time for Group Policy to sync across your domain
For MDMs that support direct registry configuration (Workspace ONE, etc.), you can deploy policies via registry keys.
HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Perplexity\Comet\\
HKEY\_CURRENT\_USER\SOFTWARE\Policies\Perplexity\Comet\\
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"
Once devices are enrolled, you can deploy additional registry keys to enforce browser policies.
Windows Registry Editor Version 5.00 \[HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Perplexity\Comet\URLBlocklist] "1"="chatgpt.com" "2"="\*.competitor.com"
Windows Registry Editor Version 5.00 \[HKEY\_LOCAL\_MACHINE\SOFTWARE\Policies\Perplexity\Comet\ExtensionInstallBlocklist] "1"="nkbihfbeogaeaoehlefnkodbefgpgknn"
Open Comet browser on the target device
Navigate to comet://policy
Verify that your policies appear in the list
Policies marked as "Mandatory" cannot be overridden by users
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