This article provides information on using certificates to ensure only approved devices can connect to ScreenMeet Remote Support.Supported on both Windows and macOS devices. The Remote Support client for macOS must be version 3.115.1544 or higher.<hr><h3>What is Certificate-Based Device Validation?</h3>This is an enhanced security feature built into our ScreenMeet Remote Support Client for Windows. When enabled, this feature will cause the service to reject any incoming requests from endpoints without the appropriate certificate installed, thus preventing any unmanaged Windows clients from connecting to your organization's ScreenMeet Remote Support services.<h3>When should you use Certificate-Based Device Validation?</h3>If you would like to restrict access to your ScreenMeet Remote Support service to specific Windows endpoints that are managed by your organization. These are typically endpoints managed by an MDM solution that can install/manage certificates on the endpoints.<hr><h3>How to configure Certificate-Based Device Validation</h3><ol><li>Issue and install certificates on managed devices that should be allowed to connect to the ScreenMeet Remote Support service (This is typically done by your IT Administrator)</li><li>Decide on a Issuer Common Name to use for the certificate. This is the name that will be:<ul><li>specified in the issuing certificate (pem)</li><li>encoded in the certificate (p7b) as part of the Issuer name during issuance</li><li>configured in the ScreenMeet Portal as a filter to be used during certificate validation</li></ul></li><li>Issue the device certificates for your managed devices<ul><li>Using your trusted issuing certificate (<code>pem</code>), issue the device certificates for your managed devices. This is typically done by your IT organization</li></ul></li></ol><hr><h3>Install the certificates on your managed devices</h3>This is typically done by your IT organization through an MDM tool. If doing this manually, follow the steps below:Install on a Windows device:<ol><li>Distribute the device certificates (<code>p7b</code>) to your managed devices</li><li>Open the <code>p7b</code> file to open the certificate container</li><li>Locate the actual device certificate for installation</li><li>Double-click on the actual device certificate</li><li>Click the <code>Install Certificate...</code> button to open the install wizard</li><li>Select the option for installing for the <code>Local Machine</code></li><li>Click the <code>Install</code> button</li><li>Let the wizard automatically select which certificate store and click the <code>Finish</code> button</li><li>You should see a dialog specifying that <code>The import was successful</code></li></ol>Install on a macOS device:<ol><li>Distribute the device certificate to the macOS device (commonly provided as a .cer, .crt, or .p12 file).</li><li>Open <code>Keychain Access</code> on the device.</li><li>Select the <code>System</code> keychain from the left-hand pane.</li><li>If prompted, authenticate with administrator credentials to make changes.</li><li>Drag and drop the certificate file into the <code>System</code> keychain, or double-click the certificate and select <code>System</code> when prompted for the keychain location.</li><li>Confirm the certificate appears under <code>System</code> → <code>Certificates</code>.</li><li>If required, open the certificate and ensure it is trusted appropriately.</li></ol><hr><h3>Verify the certificate is installed on your device</h3>NoteThe location where your certificates are installed on your device may differ from this example. Please contact your IT Administrator to verify your certificate installations if needed.For this functionality to work properly in escalated scenarios, the certificate needs to be installed for the local machine and NOT just for the local user.&nbsp;To check a certificate on a Windows device:<ol><li>On your Windows device, open the certificate manager by searching for the tool <code>Manage Computer Certificates</code>, opening this tool should open a window showing the <code>Certificates - Local Computer</code></li><li>Navigate to <code>Other People</code> --&gt; <code>Certificates</code> to see the default location where these certificates are installed</li><li>Confirm that your certificate is installed in the listing</li></ol>To check a certificate on a macOS device:<ol><li>On your macOS device, open <code>Keychain Access</code> by using Spotlight Search (Command + Space) and searching for Keychain Access</li><li>In Keychain Access, select the <code>System</code> keychain from the left-hand panel, then select <code>Certificates</code> under the Category section</li><li>Review the certificate list and confirm that the expected certificate is present and issued by the correct certificate authority</li></ol><hr><h3>Enable this feature this in the ScreenMeet Portal</h3><ol><li>Login to <a target="_blank" rel="noopener noreferrer nofollow" href="http://console.screenmeet.com">console.screenmeet.com</a> as an administrator</li><li>Navigate to <code>Organization</code> --&gt; <code>Settings and Policies</code> --&gt; <code>Device Validation</code> &nbsp; </li><li>Enable the <code>Device Validation Enabled</code> toggle and <code>Enforce On Windows</code> and/or <code>Enforce On macOS</code> &nbsp; </li><li>Enter the <code>Common Name Filter</code> you have selected</li><li>Paste the issuing certificate contents into the <code>Issuing certificate 1 - PEM Format</code> field &nbsp; </li><li>Click the <code>Save</code> button to save your configuration &nbsp;</li></ol><h3>Error Codes</h3>If validation fails during a connection from a managed device, the end-user will receive one of the following error codes:<table style="width: 1322px;"><tbody><tr><th colspan="1" rowspan="1">Code</th><th colspan="1" rowspan="1">Meaning</th></tr><tr><td colspan="1" rowspan="1">4043</td><td colspan="1" rowspan="1">The device certificate was not properly installed. &nbsp;A fitting certificate was not found on the device.</td></tr><tr><td colspan="1" rowspan="1">4044</td><td colspan="1" rowspan="1">The certificate is either malformed or invalid.</td></tr></tbody></table>

Certificate-Based Device Validation

Getting Application from ServiceNow Store

Using your Azure Blob for ScreenMeet File Storage

Minimal Cobrowse Script

Frequently Asked Questions

Timeout Settings

July

Remote Control

IP Access Control Feature

Live Release Notes Q2 2024

Video Chat Integration

Cobrowse Settings

CoBrowse Release Notes Q2 23

Connecting to Mac devices

Connecting to a Device Using Beam

Windows Tools

Starting a session

CoBrowse Release Notes Q1 22

Remote Support Release Notes Q4 24

Clipboard

Release Summer 21 (1.14)

Virtual Agent Integration w/ ScreenMeet

Android SDK Quickstart

Security

Remote Support Release Notes Q3 23

Replay Settings

Custom Copy

CoBrowse Deployments

AI Summary History

Integration Signing Key

Microsoft D365 Release Notes Q4 2022

Replay Release Notes Q2 24

October

Live Settings

ScreenMeet Console Customers

Hosting a Desktop Session

Remote Support Release Notes Q2 23

Creating a Replay Recording

AI Assist Overview

Included Reports and how to add them into Dashboards

Custom Domain

Networking Configuration

AI Summarization

Remote Support

Overview

Remote Support Settings

CoBrowse Release Notes Q2 24

Sign in to console.screenmeet.com

Multiple Domain and Subdomain support

February

File Transfer Settings

Exporting ScreenMeet + Salesforce data to third party visualization tools

Beam Release Notes Q1 24

Regional Geo-Fencing

Custom Branding

AI Assist

Configure API service

Beam Release Notes Q3 23

Joining & Completing a Live Plus session

Egress IP Addresses

Custom URL

Starting a Session from within Salesforce

Settings and Policies

Requirements

How To Install ScreenMeet in Your Genesys Instance

Localization

Configuring Environment Variables

Reviewing a Session

August

Remote Support Release Notes Q1 23

Live Release Notes Q2 22

Release Summer 2020 (1.9)

Device Requirements

System Information

Create Multiple Sessions

ServiceNow Release Notes Q4 24

403 Forbidden while making API request

Manage Beam Group Permission Set

ScreenMeet Platform Release Notes Q3 23

Remote Support Release Notes - Q1 22

Screen Annotation

Creating a Session

Custom Background

Remote Support Release Notes Q2 24

AI Summary Studio

Instructions to Person at End Point Device

Beam Client: Installation, Deployment, and Configuration Guide

Beam Groups: Setup, Settings, and Access Management

Component settings

Customer initiated sessions with a chatbot

ScreenMeet 2024 Release Notes

Package Installation Error - Case-Case Layout: feedLayout is not supported for this layout

Developer Notes (3.0.11)

Starting a Session from Dynamics

ScreenMeet Platform Release Notes Q1 23

Remote Support Release Notes Q2 22