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

# Manifest V2 Installation

> Institutional deployment guide for the Scribe Web Companion — MV2 build (Chromium forks < 88)

<Warning>
  **MV2 is a legacy build** for Chromium forks with version below 88 (e.g. older Cent Browser). If your workstations run Google Chrome, Microsoft Edge, or any browser with Chromium >= 88, use the [Manifest V3 installation](/scribe-web-companion/mv3-installation) instead.
</Warning>

<Info>
  **Audience:** Hospital IT and Information Security teams.
  This guide covers the **Manifest V2** build — only for Chromium forks with version \< 88.
</Info>

## Extension ID

```
blohhkgibpajgnknfeokemldajkpnfjg
```

This is the 32-character identifier derived from the MV2 build's public signing key. Different from MV3 because each build is signed with its own key.

## Prerequisites

* Workstations run a Chromium fork with version **\< 88** (e.g. Cent Browser on older Chromium)
* HTTPS outbound connectivity to `cdn.telepatia.ai` is allowed (port 443)
* A policy management platform is available (ManageEngine, Intune, GPO, or equivalent)

<Tip>
  To confirm the Chromium version: open `cent://version` (or equivalent). The **Chromium version** (not the product version) determines the MV2/MV3 decision.
</Tip>

## Policy Snippet

```json theme={null}
{
  "blohhkgibpajgnknfeokemldajkpnfjg": {
    "installation_mode": "force_installed",
    "update_url": "https://cdn.telepatia.ai/scribe-extension/update-manifest.xml"
  }
}
```

### Fields

| Field                              | Description                                                                                                     |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| `blohhkgibpajgnknfeokemldajkpnfjg` | MV2 extension ID — different from MV3                                                                           |
| `installation_mode`                | `"force_installed"` — silent install, user cannot disable or remove                                             |
| `update_url`                       | Same Omaha XML endpoint as MV3 — the manifest serves both builds, each browser consumes the one matching its ID |

### Blocking other extensions (optional)

```json theme={null}
{
  "*": {
    "installation_mode": "blocked"
  },
  "blohhkgibpajgnknfeokemldajkpnfjg": {
    "installation_mode": "force_installed",
    "update_url": "https://cdn.telepatia.ai/scribe-extension/update-manifest.xml"
  }
}
```

## Obtaining the CRX

<Steps>
  <Step title="Check the manifest">
    Open `https://cdn.telepatia.ai/scribe-extension/update-manifest.json`.
  </Step>

  <Step title="Download the MV2 CRX">
    Use the URL from the `v2.crx.downloadUrl` field.
  </Step>

  <Step title="Verify integrity">
    ```powershell theme={null}
    Get-FileHash -Algorithm SHA256 .\extension-v2-<version>.crx
    ```

    Compare with `v2.crx.sha256`.
  </Step>
</Steps>

## Deployment via ManageEngine Endpoint Central

<Steps>
  <Step title="Navigate to Browsers → Manage → Extension Repository" />

  <Step title="Add Extensions → Add Extensions for Google Chrome → Upload Directly" />

  <Step title="Upload the MV2 CRX file">
    Confirm the Plugin Identifier matches `blohhkgibpajgnknfeokemldajkpnfjg`.
  </Step>

  <Step title="Apply policy to target hosts/groups" />

  <Step title="Wait for propagation" />

  <Step title="Validate (see below)" />
</Steps>

## Deployment via GPO

<Steps>
  <Step title="Open Group Policy Management Console">
    Edit the GPO targeting the clinical workstations OU.
  </Step>

  <Step title="Navigate to Computer Configuration → Administrative Templates → Google Chrome → Extensions → ExtensionSettings" />

  <Step title="Enable and paste the MV2 JSON snippet" />

  <Step title="Link the GPO to the target OU" />

  <Step title="Wait for GPO refresh (~90 min) or gpupdate /force" />

  <Step title="Validate (see below)" />
</Steps>

<Note>
  The `ExtensionSettings` policy is respected by most Chromium forks that honor Chrome policy keys, including Cent Browser. For forks with custom policy parsing, validate in pilot first.
</Note>

## Network Requirements

| Destination        | Port        | Purpose                              |
| ------------------ | ----------- | ------------------------------------ |
| `cdn.telepatia.ai` | 443 / HTTPS | Manifests, CRX download, auto-update |

Same requirements as MV3. See the [MV3 guide](/scribe-web-companion/mv3-installation#network-requirements) for SSL inspection details.

## Auto-Update

Same mechanism as MV3 — the browser checks for updates every \~5 hours. The `update_url` is the same endpoint; the manifest serves both MV2 and MV3 builds.

## Post-Installation Validation

<Tabs>
  <Tab title="Layer 1: Installed">
    * Open `chrome://extensions` (or fork equivalent)
    * Confirm **Telepatia Scribe Companion** appears
    * Confirm it says *Installed by your administrator*
  </Tab>

  <Tab title="Layer 2: Correct ID">
    * Expand details and confirm ID is `blohhkgibpajgnknfeokemldajkpnfjg`
    * If the ID is `fobdkddljbpmhnlclknlgcgbeeeojcnb`, the MV3 CRX was applied instead — re-do with the MV2 CRX
  </Tab>

  <Tab title="Layer 3: Auto-update">
    * Enable Developer mode, click "Update"
    * Or validate connectivity:

    ```powershell theme={null}
    Invoke-WebRequest -Uri https://cdn.telepatia.ai/scribe-extension/update-manifest.xml -UseBasicParsing
    ```
  </Tab>
</Tabs>

## Ongoing Operations

Same responsibility model as MV3. See the [MV3 guide](/scribe-web-companion/mv3-installation#ongoing-operations).

## Support

Same channels as MV3. Report unexpected behavior during installation through the agreed Telepatia channels.