Checklist for Customers Using TelemetryOS Edge

Customer checklist for using Edge

TelemetryOS Edge Deployment Checklist

TelemetryOS deployment requires understanding of system architecture, network requirements, security protocols, and configuration options. This guide covers prerequisites and considerations for successful TelemetryOS integration.

TelemetryOS Platform Overview

Ecosystem and Security

TelemetryOS operates as a locked-down, purpose-built operating system within the TelemetryOS ecosystem:

Security FeatureImplementationBenefit
Software controlPrevents unauthorized software installationEnhanced security and stability
Hardware integrationValidated hardware compatibilityReliable operation
Purpose-built OSOptimized for digital signageReduced attack surface

The platform prevents installation of unauthorized software, ensuring enhanced security and stability. Hardware and software integration prioritizes security and controlled operation.

Network Security Requirements

TelemetryOS devices support WPA2-Enterprise network configurations for secure network access:

Network protocol support:

  • WPA2-Enterprise (certificate-based authentication)
  • WPA2-PSK (pre-shared key)
  • Open networks (not recommended for production)

Network infrastructure must accommodate these security protocols, particularly for IoT and enterprise deployments. Wi-Fi security protocols require verification against organizational network policies before deployment.

Updates and Maintenance

TelemetryOS devices automatically update to the latest TelemetryOS platform versions:

Update characteristics:

  • Automatic delivery (no manual intervention required)
  • Configurable maintenance windows (schedule update timing)
  • Continuous feature access (new features delivered automatically)
  • Fleet consistency (all devices maintain current versions)

Automatic updates simplify fleet maintenance and ensure consistent software versions across deployments.

Pre-Deployment Provisioning

TelemetryOS supports two provisioning approaches with distinct workflows:

Provisioning MethodConfiguration TimingUse Case
Device-LevelOn-device during setupSmall deployments (< 10 devices), testing
Token-BasedPre-configured before deploymentLarge deployments (10+ devices), zero-touch setup

Device-Level Configuration

Device-level settings configure directly on the TelemetryOS device before or during deployment:

Network Configuration:

  • Wired: DHCP automatic IP allocation or static IP configuration
  • WiFi: Standard and hidden SSID networks with WPA2/WPA2-Enterprise security

Time Zone and Screen Layout:

  • Time zone settings for accurate time synchronization
  • Screen layout options: mirrored, horizontal, vertical, grid, mixed, disabled

Security Settings:

  • Password protection (prevents unauthorized device access)
  • Context menu disabling (maintains device integrity)
  • Remote debugging (troubleshooting access for TelemetryOS support)

Token-Based Provisioning

Provisioning tokens preconfigure device settings through the TelemetryOS interface before device activation:

Configuration categories:

Setting CategoryConfigurable ParametersBenefit
NetworkWireless SSID, passwordAutomatic network connection
DisplayTime zone, orientation, 4K, rotation, brightnessDeployment-ready displays
ProxyHTTP proxy hostname, port, credentialsCorporate proxy integration
SecuritySettings passwordsEnforced security policies

Provisioning configuration ensures devices deploy with correct security and operational settings before production use.

Hardware and Procurement

Supported Hardware

TelemetryOS requires TelemetryOS-approved hardware for reliable operation:

Hardware sources:

Unsupported hardware lacks compatibility with the TelemetryOS platform and may experience stability issues.

Configuration Timing

Configuration settings divide into pre-deployment and post-deployment categories:

Configuration TimingSettingsConfiguration Method
Pre-DeploymentTags, WiFi (standard networks), time zone, secondary screenDevice interfaces or provisioning tokens
Post-DeploymentAudio channels, secondary screen adjustments, hidden networksDirect device configuration

Network Security

Firewall implementation and network segmentation enhance security for TelemetryOS deployments:

Security patterns:

  • Network segmentation: Separate subnets isolate IoT devices from primary network infrastructure
  • Firewall rules: Restricted outbound connections to TelemetryOS endpoints only
  • VLAN isolation: Dedicated VLANs for signage device traffic

See firewall documentation for detailed network security guidance.

Deployment

Network Connectivity

Network connection types support TelemetryOS devices with varying reliability characteristics:

Connection TypeReliabilityDeployment Recommendation
Wired (Ethernet)Superior stabilityProduction deployments, permanent installations
Wireless (WiFi)Moderate stabilityTesting, temporary installations, retrofit scenarios

Wired connections deliver superior stability and reliability compared to wireless connectivity.

Audio Configuration

Audio channel configuration occurs after display connection:

Configuration workflow:

  1. Connect display via HDMI
  2. Power on device
  3. Access device interface
  4. Configure audio settings (HDMI audio, analog out, volume)

Audio settings adjust through the device interface after physical hardware connection.

Display Configuration

Screen layout and video wall configurations optimize at deployment locations:

Configuration considerations:

  • Physical display arrangements (single, dual, video wall)
  • Viewing requirements (viewing distance, audience patterns)
  • Content layout (full-screen, zoned, synchronized)

On-site configuration accounts for specific physical display arrangements and viewing requirements.

Device Management

Remote Management Capabilities

The TelemetryOS interface supports remote management for:

Remotely configurable:

  • System time and time zone
  • Screen layout and orientation
  • Operational settings (active window, update window)
  • Content assignment (playlists, applications)

Requires physical access:

  • Network reconfiguration (security)
  • Settings password changes (security)
  • Hardware diagnostics (physical inspection)

Some configuration options require physical device access for security reasons.

Remote Troubleshooting

Remote debugging capabilities support troubleshooting through the TelemetryOS platform:

Remote diagnostics:

  • Live screenshots (current display state)
  • Log access (error diagnosis)
  • Remote commands (restart player, clear cache)

Physical device access may be necessary for certain diagnostic or configuration scenarios (network issues, hardware failures, physical inspection).

Update Management

Update windows and active hours control when TelemetryOS devices apply system updates:

SettingFunctionConfiguration
Update windowScheduled maintenance time for updatesHour-of-day selection
Active hoursOperational hours (no updates)Time range specification

Configurable update schedules prevent disruptions during operational hours and optimize device maintenance timing.

Deployment Checklist

Pre-Deployment Tasks

  • Verify hardware compatibility (approved devices)
  • Configure network infrastructure (firewall rules, VLANs)
  • Create provisioning tokens (for token-based provisioning)
  • Prepare network credentials (WiFi SSIDs, passwords)
  • Define security policies (settings passwords, WPA2-Enterprise)

Deployment Tasks

  • Connect devices to displays
  • Power on devices
  • Configure network connectivity (Ethernet or WiFi)
  • Apply provisioning configuration (device-level or token-based)
  • Pair devices to TelemetryOS account
  • Assign content (playlists, applications)
  • Verify playback (screenshots, live monitoring)

Post-Deployment Tasks

  • Configure audio settings
  • Optimize display layouts
  • Set update windows and active hours
  • Document device locations and configurations
  • Establish monitoring and alerting

Configuration Specifications

TelemetryOS Edge devices configure through local device interfaces (during setup) or TelemetryOS dashboard (after pairing).

Required Configuration

  • Network connectivity (Ethernet or WiFi)
  • Account pairing (provisioning token or manual pairing code)

Optional Configuration

  • Time zone
  • Screen layout and orientation
  • Security settings (password protection)
  • Proxy configuration
  • Display brightness and 4K support
  • Audio settings

Limitations

  • Unsupported hardware not validated (compatibility issues possible)
  • Some configuration requires physical device access (security)
  • Remote debugging requires enabled setting (disabled by default)
  • Provisioning tokens expire (180 days typical)
  • WPA2-Enterprise requires certificate infrastructure
  • Network reconfiguration requires physical access after initial setup
  • Update windows minimum 1 hour duration
  • 32-bit systems not supported (64-bit Intel/AMD only)