Starting Up TelemetryOS

TelemetryOS device initialization involves provisioning, network configuration, and account pairing to enable content delivery and remote management.

Provisioning Options

TelemetryOS supports two provisioning methods with distinct workflows:

Provisioning Method	Configuration Location	Use Case
Device Provisioning	Local device interface	Network, time zone, screen layout, security settings configured directly on device
Token Provisioning	Pre-configured before deployment	Wi-Fi, time zone, display options, proxy settings, passwords preconfigured via provisioning tokens

The Checklist for Customers Using TelemetryOS details comprehensive provisioning workflows.

Security and Management

TelemetryOS includes enterprise security and management capabilities:

Platform characteristics:

Locked-down operating system optimized for signage applications
Logging and health metrics collection (enabled by default)
Controlled update system with configurable maintenance windows

🔐
Settings passwords and WPA2-Enterprise network authentication deliver enhanced security for policy-compliant deployments.

Security Features

Security Feature	Implementation	Benefit
Locked-down OS	No unauthorized software installation	Reduced attack surface
Settings passwords	Prevent unauthorized configuration changes	Configuration integrity
WPA2-Enterprise	Certificate-based network authentication	Network security compliance
Controlled updates	Configurable maintenance windows	Managed update timing

Performance and Caching

TelemetryOS optimizes performance for reliable content delivery:

Optimization strategies:

Streamlined playback pipeline: Eliminates non-essential background services for dedicated playback performance
Deterministic content caching: Staged downloads with predictable cache behavior enable reliable offline playback

Content caches locally to ensure playback reliability during network degradation or outages.

Hardware Compatibility

TelemetryOS runs on multiple hardware platforms:

Platform	Deployment Method	Use Case
Node Pro	Ships with TelemetryOS preinstalled (recommended)	Production deployments, validated hardware
BYOD installations	Custom hardware with TelemetryOS installation	Cost-conscious deployments, existing hardware

Recommended approach: Node Pro delivers lower total cost of ownership through validated compatibility, preinstallation, and enterprise support.

BYOD approach: Custom hardware installations require hardware validation and ISO approval from TelemetryOS support.

Initial Device Setup

TelemetryOS devices require network connectivity (Ethernet or Wi-Fi) during initial power-on:

Setup workflow:

Power on device
Network configuration interface displays
Configure network (Ethernet or WiFi)
Provisioning tokens or local configuration complete setup
Device pairing to TelemetryOS account (6-digit code entry)
Content publishing and remote management enabled

Device pairing to a TelemetryOS account enables content publishing and remote management capabilities.

Provisioning Workflow Comparison

Device Provisioning (Local Configuration)

Workflow:

Power on device
Configure network via on-screen interface
Configure time zone, screen layout, security settings
Complete pairing with 6-digit code

Advantages:

No pre-configuration required
Suitable for small deployments (< 10 devices)
Immediate setup without token creation

Disadvantages:

Manual configuration per device (not scalable)
On-site configuration required
Inconsistent settings across fleet (manual entry errors)

Token Provisioning (Pre-Configuration)

Workflow:

Create provisioning token in TelemetryOS dashboard (pre-deployment)
Write token to USB drive
Insert USB drive into device during boot
Device auto-configures from token
Device auto-pairs to account

Advantages:

Zero-touch deployment (no manual configuration)
Scalable for large fleets (10+ devices)
Consistent settings across fleet (pre-configured)
Remote site deployment (no on-site configuration required)

Disadvantages:

Requires token creation before deployment
USB drive required per device or group
Token expiration (180 days typical)

Common Deployment Patterns

Small business (< 10 devices): Device provisioning with manual configuration

Enterprise deployment (10-100 devices): Token provisioning with pre-configured settings

Large-scale fleet (100+ devices): Token provisioning with staging process and bulk USB preparation

Multi-tenant deployment: Separate provisioning tokens per tenant with tenant-specific settings

Regional deployment: Location-specific provisioning tokens with regional network credentials

Configuration Specifications

TelemetryOS devices configure during initial setup (provisioning and pairing) and through TelemetryOS dashboard (content and settings) after pairing.

Required Configuration

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

Optional Configuration

Time zone
Screen layout (single, dual, video wall)
Security settings (settings password)
Proxy configuration
Display brightness and orientation
Audio settings

Limitations

Initial setup requires local device access or provisioning token
Network reconfiguration after pairing requires physical device access (security)
Settings password resets require factory reset (password cannot be recovered)
Provisioning tokens expire (180 days typical, renewable)
WPA2-Enterprise requires certificate infrastructure (PKI)
Some configurations available only pre-pairing (token provisioning) or post-pairing (dashboard)
Offline devices cannot receive configuration updates (require network connectivity)
Custom hardware requires validation and ISO approval from support