Player provisioning at scale transforms a box of players into a coordinated fleet of configured, content-loaded, and monitored screens. For 10 players, manual setup takes a day. For 500 players, manual setup takes months. Automated provisioning — zero-touch via Arya, scripted via API, or pre-staged in a lab — reduces per-player deployment time from hours to minutes.
Provisioning Methods
Zero-Touch (Arya Cloud)
The fastest path: connect the player to the internet, register its serial number in Arya, and assign it to a group. The player auto-downloads its configuration profile and content. Installer workflow: unbox → mount → connect HDMI + Ethernet → done. All configuration happens from the Arya dashboard.
Pre-Staging (Lab Configuration)
Configure players in a central location before shipping to installation sites. Set network parameters, upload content, verify display output, and label each player with its target location. Ship pre-configured players to site — installers only handle physical mounting and cabling.
Scripted Provisioning (REST API)
For on-premises deployments without Arya, use scripts. A provisioning script discovers new players on the network, applies REST API configuration (network, security, display settings), uploads content, and verifies output. The script processes 50 players in the time it takes to manually configure one.
Provisioning Checklist
| Step | Action | Automation |
|---|---|---|
| 1. Identity | Record serial, MAC, assign location | Inventory spreadsheet |
| 2. Network | IP address, DNS, proxy, NTP | DHCP + config profile |
| 3. Security | Player password, HTTPS, access control | Config profile / script |
| 4. Display | Resolution, orientation, CEC settings | Config profile / script |
| 5. Content | Assign and publish initial content | Arya group / WebDAV script |
| 6. Verify | Screenshot, status check, display output | API screenshot + status |
| 7. Document | Update fleet inventory | Auto-populate from Arya |
Key Parameters
| Parameter | Value | Why It Matters |
|---|---|---|
| Zero-touch | Auto-config on first boot | No technician needed at site |
| Pre-stage | Lab → ship → install | Verified before field deployment |
| Config profiles | Group-based settings | Consistent config across fleet |
| Fleet inventory | Central tracking document | Know what's deployed where |
| Verification | API + screenshot | Confirm success remotely |
Common Mistakes
- Manual provisioning at 100+ scale. Configuring each player individually through the web interface is unsustainable above 50 units. Use Arya groups, config profiles, or API scripts for batch provisioning.
- No fleet inventory. Without a tracking document, you don't know which serial number is in which room. Maintain a spreadsheet or asset management database from day one.
- Default security settings. Deploying players with default passwords (or no password) exposes them to unauthorized access. Include security configuration in the provisioning profile.
- No post-install verification. Assuming a player works after mounting is risky. Capture a screenshot via API after installation to verify content renders correctly on the actual connected display.