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 Required
Remote Support Branding must be enabled for your organization before it can be configured. Contact ScreenMeet Support to request access.
Prerequisites
Remote Support Branding enabled by ScreenMeet Support for your organization
Administrator access to console.screenmeet.com
New Remote Support client (macOS and Windows)
Configuring Remote Support Branding
Log in to console.screenmeet.com as an administrator.
Navigate to Organization > Settings & Policies > Remote Support Branding.
Configure your settings:
App Name: The name of the application displayed in the client.
Download File Name: The name displayed as the downloaded file name.
Applies to the EXE installer only. Not applicable to the MSI.
App Icon File: The icon displayed in the title bar, taskbar, system tray, and installer.
Applies to Windows devices only.
Applies to the EXE installer only. Not applicable to the MSI.
Customize Logo and Colors:
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.
Change Logo: Customizes the logo displayed in the Remote Support client. Maximum file size is 6.5 kB.
Click Save Branding to apply your changes.
To revert all settings to the original defaults, click Reset to Defaults.
Pre-Staging Branding for MDM Deployment
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 cache.json, located at C:\ProgramData\Projector Inc\ScreenMeet Support. 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 Approach
Pre-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.
Prepare the PowerShell Script
The script below creates cache.json at the correct path, creates the directory if it does not exist, and logs activity to both C:\ProgramData\ScreenMeet\Logs\cache-deploy.log and the Windows Application Event Log under the source ScreenMeet-Deploy.
Update Branding Values Before Deploying
Replace the placeholder values for app_name, BrandColor, AccentColor, and the two value fields in the colors array with your organization's actual values from your Remote Support Branding configuration before deploying the script.
#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
}Verification
On a target endpoint, navigate to
C:\ProgramData\Projector Inc\ScreenMeet Supportand confirmcache.jsonis present.Open
cache.jsonin a text editor and verify theapp_name,BrandColor, andAccentColorvalues match your branding configuration.Review the deployment log at
C:\ProgramData\ScreenMeet\Logs\cache-deploy.logfor a successful write entry.In Event Viewer, navigate to Windows Logs > Application and filter by source
ScreenMeet-Deployto confirm the script completed without errors.