AI Docs
Navigated to page CerteroX SaaS Management - AI Docs

Deploy the Windows Native Messenger

Avatar for Unknown author
Created by Unknown author
4 min read

Scope: This guide covers deployment of the Native Messenger to Windows endpoints only. macOS is not covered here.

Overview

The CerteroX Native Messenger is a client-side application that enables seamless authentication for the CerteroX browser extension. It is currently a Windows application.

Its primary function is to automatically authenticate the user signed into the browser extension by using the credentials of the currently logged-in Windows user. This provides a Single Sign-On (SSO) experience, removing the need for users to perform a manual sign-in.

Prerequisites

Before deployment, please ensure the following requirements are met:

  • Administrative privileges are required on the target endpoint for installation.

  • Your CerteroX Client Key. See the About the Client Key section below.

  • The CerteroX browser extension is deployed to the users' web browsers (e.g., Chrome, Edge).

  • Target devices are running a supported Windows operating system (e.g., Windows 11).

About the Client Key

The Client Key associates an installation of the Native Messenger with your CerteroX tenant. It is customer-specific and is supplied by Certero as part of your onboarding. If you do not have yours to hand, contact Certero Support.

The Client Key is required for every installation, manual or silent, and the installer will not proceed without it. Have it available before you begin.

The key is a GUID, in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. The installer validates the format and rejects anything else.

The Native Messenger reads the key at runtime from the Windows registry, at HKLM\SOFTWARE\Certero\CerteroX (string value ClientKey). The installer writes this value for you, so there is normally no need to create it by hand.

The Client Key is not yet surfaced anywhere in the CerteroX interface. Onboarding is the only source for it at present.

Deployment Steps

The deployment process involves downloading the installer and native client from your CerteroX platform and then installing it on the target endpoints.

Step 1: Download the Installer

You can obtain the installation media directly from your CerteroX portal.

  1. Navigate to Settings → Platform Settings.

  2. Locate the CerteroX Native Messenger section.

  3. Download the installer. You can choose between two formats:

    • A .ZIP file containing the MSI installer.

    • The .MSI file directly.

Step 2: Install the Native Messenger

The application can be installed manually for testing or silently for mass deployment across your organization.

Manual Installation (GUI)

For individual installations, simply run the downloaded .MSI file. The installation wizard will guide you through the necessary steps. This method is ideal for testing or small-scale deployments.

After the welcome page, the wizard presents a Client Key Configuration page. Enter your Client Key in the Client Key field and click Next.

The wizard will not let you past this page until a valid key is entered:

  • Leaving the field blank raises a Client Key Required message.

  • A value that is not a well-formed GUID raises an Invalid Client Key message showing the expected format.

Silent Installation (Automated Deployment)

For deploying at scale, a silent installation is recommended. This method uses the standard Windows Installer (msiexec.exe) and is suitable for deployment tools like the Certero Unified Platform, Microsoft SCCM/Intune, or other Remote Monitoring and Management (RMM) systems.

Use the following command in a script or your deployment tool:

msiexec /i "C:\Path\To\CerteroXNativeMessenger.msi" CLIENTKEY=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX /qn /norestart

Command Breakdown:

  • msiexec /i: Invokes the installer package.

  • "C:\Path\To\CerteroXNativeMessenger.msi": The full path to the downloaded installer file.

  • CLIENTKEY=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX: Your Client Key, supplied by Certero during onboarding.

  • /qn: Sets the user interface level to "no UI" for a completely silent installation.

  • /norestart: Prevents the installer from forcing a reboot after completion.

Notes on the CLIENTKEY property:

  • CLIENTKEY is mandatory for a silent installation. If it is omitted, the installation fails with the message "CLIENTKEY is required for silent install."

  • The value must be a well-formed GUID. A malformed value aborts the installation with an error naming the value that was supplied.

  • The property name must be typed in uppercase. Windows Installer property names are case-sensitive, and a mixed-case form such as ClientKey= is ignored, which will present as the "required" failure above.

  • Upgrades and reinstallations do not inherit the key from the existing installation. Supply CLIENTKEY every time, including when upgrading.

Post-Installation Verification

After a successful deployment, you can verify the installation using one of the following methods:

  • Check Installed Programs: Navigate to Apps & features (or Add or Remove Programs) in Windows Settings and confirm that CerteroX Native Messenger is listed.

  • File System: Verify that the CerteroX.NativeMessenger.exe file has been created in the installation directory (typically C:\Program Files\Certero\CerteroX Client).

  • Client Key: Confirm the key recorded on the endpoint matches the one you intended to deploy. Run the following command from an elevated prompt:

    reg query "HKLM\SOFTWARE\Certero\CerteroX" /v ClientKey

    The command returns the ClientKey string value. This is useful for confirming which key an endpoint is associated with, particularly after an upgrade.