Remote Support Branding allows administrators to customize the appearance of the ScreenMeet Remote Support client, including the application name, download file name, icon, logo, and color scheme. This feature applies to the new Remote Support client on both macOS and Windows.Feature Enablement RequiredRemote Support Branding must be enabled for your organization before it can be configured. Contact ScreenMeet Support to request access.<hr><h3>Prerequisites</h3><ul><li>Remote Support Branding enabled by ScreenMeet Support for your organization</li><li>Administrator access to <a target="_new" rel="noopener" href="https://console.screenmeet.com">console.screenmeet.com</a></li><li>New Remote Support client (macOS and Windows)</li></ul><hr><h3>Configuring Remote Support Branding</h3><ol><li>Log in to <a target="_new" rel="noopener" href="https://console.screenmeet.com">console.screenmeet.com</a> as an administrator.</li><li>Navigate to Organization &gt; Settings &amp; Policies &gt; Remote Support Branding.</li><li>Configure your settings:<ul><li>App Name: The name of the application displayed in the client.</li><li>Download File Name: The name displayed as the downloaded file name.<ul><li>Applies to the EXE installer only. Not applicable to the MSI.</li></ul></li><li>App Icon File: The icon displayed in the title bar, taskbar, system tray, and installer.<ul><li>Applies to Windows devices only.</li><li>Applies to the EXE installer only. Not applicable to the MSI.</li></ul></li><li>Customize Logo and Colors:<ul><li>Enter your hex color code for the Brand and Accent colors. Click anywhere on the screen after entering a code to preview the result before saving.</li><li>Change Logo: Customizes the logo displayed in the Remote Support client. Maximum file size is 6.5 kB.</li></ul></li></ul></li><li>Click Save Branding to apply your changes.</li><li>To revert all settings to the original defaults, click Reset to Defaults.</li></ol><hr><h3>Pre-Staging Branding for MDM Deployment</h3>By default, the Remote Support client applies your organization's configured branding when it connects to its first session. At that point, the values from your console configuration are written to a local file named <code>cache.json</code>, located at <code>C:\ProgramData\Projector Inc\ScreenMeet Support</code>. If your deployment requires branding to be in place before any session is initiated, you can pre-stage this file by running the example PowerShell script below during the MDM deployment process.When to Use This ApproachPre-staging is optional. It is only necessary if your organization requires branding to be applied immediately upon installation, before the client connects to a session, to avoid end-user concerns about a non-branded app on their first ScreenMeet launch.If this is not a concern, the default behavior will apply branding automatically on first use and be used for all sessions moving forward.<h4>Prepare the PowerShell Script</h4>The script below creates <code>cache.json</code> at the correct path, creates the directory if it does not exist, and logs activity to both <code>C:\ProgramData\ScreenMeet\Logs\cache-deploy.log</code> and the Windows Application Event Log under the source <code>ScreenMeet-Deploy</code>.Update Branding Values Before DeployingReplace the placeholder values for <code>app_name</code>, <code>BrandColor</code>, <code>AccentColor</code>, and the two <code>value</code> fields in the <code>colors</code> array with your organization's actual values from your Remote Support Branding configuration before deploying the script.<pre><code class="language-powershell">#Requires -Version 5.1
$ErrorActionPreference = 'Stop'

# Output path - do not modify unless your ScreenMeet installation uses a non-default location
$OutputPath = "C:\ProgramData\Projector Inc\ScreenMeet Support"
$OutputFile = Join-Path $OutputPath "cache.json"
$LogFile = Join-Path $env:ProgramData "ScreenMeet\Logs\cache-deploy.log"
$EventSource = "ScreenMeet-Deploy"

function Write-Log {
 param(
 [string]$Message,
 [ValidateSet("INFO","WARN","ERROR")]
 [string]$Level = "INFO"
 )
 $timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
 $entry = "[$timestamp][$Level] $Message"
 try {
 $logDir = Split-Path $LogFile
 if (-not (Test-Path $logDir)) { New-Item -ItemType Directory -Path $logDir -Force | Out-Null }
 Add-Content -Path $LogFile -Value $entry -Encoding UTF8
 } catch { }
 try {
 if (-not [System.Diagnostics.EventLog]::SourceExists($EventSource)) {
 [System.Diagnostics.EventLog]::CreateEventSource($EventSource, "Application")
 }
 $entryType = switch ($Level) {
 "ERROR" { [System.Diagnostics.EventLogEntryType]::Error }
 "WARN" { [System.Diagnostics.EventLogEntryType]::Warning }
 default { [System.Diagnostics.EventLogEntryType]::Information }
 }
 Write-EventLog -LogName Application -Source $EventSource -EntryType $entryType -EventId 1000 -Message $Message
 } catch { }
 Write-Host $entry
}

# Replace placeholder values with your organization's Remote Support Branding configuration
$cacheJson = @'
{
 "app_name": "Your Organization - ScreenMeet",
 "download_file_name": "ScreenMeet.Support",
 "branding_data": {
 "colorFunction": "SupportNativeClientColorCalculator",
 "samplePage": "native-client-branding.html",
 "isOnlyUsingCoreColors": true,
 "colors": [
 {
 "name": "brand",
 "label": "Brand",
 "value": "#000000",
 "isCoreColor": true
 },
 {
 "name": "accent",
 "label": "Accent",
 "value": "#000000",
 "isCoreColor": true
 }
 ],
 "BrandColor": "#000000",
 "AccentColor": "#000000"
 }
}
'@

Write-Log "ScreenMeet cache.json deployment started. Target: $OutputFile"

try {
 if (-not (Test-Path $OutputPath)) {
 New-Item -ItemType Directory -Path $OutputPath -Force | Out-Null
 Write-Log "Created output directory: $OutputPath"
 }

 $utf8NoBom = New-Object System.Text.UTF8Encoding $false
 [System.IO.File]::WriteAllText($OutputFile, $cacheJson, $utf8NoBom)
 Write-Log "cache.json written successfully."
 exit 0

} catch {
 Write-Log "Deployment failed: $_" -Level "ERROR"
 exit 1
}</code></pre><h4>Verification</h4><ol><li>On a target endpoint, navigate to <code>C:\ProgramData\Projector Inc\ScreenMeet Support</code> and confirm <code>cache.json</code> is present.</li><li>Open <code>cache.json</code> in a text editor and verify the <code>app_name</code>, <code>BrandColor</code>, and <code>AccentColor</code> values match your branding configuration.</li><li>Review the deployment log at <code>C:\ProgramData\ScreenMeet\Logs\cache-deploy.log</code> for a successful write entry.</li><li>In Event Viewer, navigate to Windows Logs &gt; Application and filter by source <code>ScreenMeet-Deploy</code> to confirm the script completed without errors.</li></ol><hr>

Remote Support Branding

ScreenMeet 2025 Release Notes

403 Forbidden while making API request

404 NO_ACCESS

Installing ScreenMeet for Salesforce

Advanced CSS customization

AI Assist

AI Assist Overview

Overview

AI Release Notes Q4 24

Requirements

AI Summarization

AI Summary History

AI Summary Privacy

AI Summary Studio

Android SDK Quickstart

How-to: Setup the app for Laser Pointer

How-to: Display a video stream to the end-user

Egress IP Addresses

AWS S3 File Storage

Configuring ScreenMeet / Microsoft Entra ID integration

Signing into ScreenMeet console with Microsoft Entra ID (Azure AD)

Beam Client: Installation, Deployment, and Configuration Guide

Beam Groups: Setup, Settings, and Access Management

Beam Release Notes Q1 22

Beam Release Notes Q1 23

Beam Release Notes Q1 24

Beam Release Notes Q2 22

Beam Release Notes Q2 23

Beam Release Notes Q2 24

Beam Release Notes Q3 23

Beam Release Notes Q3 22

Beam Release Notes Q4 22

Beam Release Notes Q4 24

New Remote Support Client for Mac

Canvas

Certificate-Based Device Validation

Clone - Remote Support Release Notes Q4 23

Clone - Test ScreenMeet 2025 Release Notes

File Storage on AWS

Configuring Information Security & PII

Creating a Custom UI

Custom Copy

Cobrowse Demo

CoBrowse Deployments

Events

Hotkeys

Localization

CoBrowse Release Notes Q1 23

CoBrowse Release Notes Q1 22

CoBrowse Release Notes Q1 24

CoBrowse Release Notes Q2 22

CoBrowse Release Notes Q2 23

CoBrowse Release Notes Q2 24

CoBrowse Release Notes Q3 22

CoBrowse Release Notes Q3 23

CoBrowse Release Notes Q3 24

CoBrowse Release Notes Q4 22

CoBrowse Release Notes Q4 23

CoBrowse Release Notes Q4 24

Remote Control

Remove End Cobrowse Button

Cobrowse Script

Cobrowse Settings

Starting a Session with a URL

Configuration and validation troubleshooting

Configure API service

Configure ScreenMeet for a New Salesforce Sandbox

Configure ScreenMeet to only show on specified tables

Configuring Environment Variables

Configuring Webhooks for Data Sync

Connecting to ChromeOS devices

Connecting to Mac devices

Connection Information

Create Multiple Sessions

Creating a Replay Recording

Creating a session

Custom Consent Message

Custom permission configuration for ServiceNow

Custom URL

Custom Windows Tools

Deploying a Pre-installed Client

Developer Notes

Developer Notes (3.0.11)

Device Requirements

Enable ScreenMeet for Omnichannel Chat Widget

Enabling features within the Salesforce + ScreenMeet component