Player Setup/Provisioning

bsn control and bsn content were formerly named control cloud and content cloud, respectively player setup as covered in the start here docid\ d1tz0hy4bh9ngcvuoe3of section, new players must first be set up before they can do much of anything this process involves applying a setup to the player the setup applies various settings to the player (network settings, publishing mode, logging, etc ) and includes a player app which provides instructions for what the player should do upon startup player provisioning as was also mentioned in the start here docid\ d1tz0hy4bh9ngcvuoe3of section, the term provisioning refers to using bsn cloud to set up a player, and given that bsn cloud (either the bsn control or bsn content tiers) is used the vast majority of time to set up players, the term provision is often used when referring to player setup the primary cases where a player can be properly set up instead of provisioned (i e , bsn cloud is not used to apply the setup to the player) are standalone player configurations where the setup is manually copied to a storage device and then the storage device is connected to a player uncommon situations where a partner chooses to set up players without using bsn cloud with bsn cloud, provisioning a new player can be nearly automatic if things are properly set up beforehand, new players can be automatically provisioned just by plugging them in! for customers who can’t or don’t want to connect their players to the internet, offline provisioning options are also available provisioning of players can be done for free using either brightauthor\ connected or the unbranded bsn control interface at control bsn cloud however, since control bsn cloud is the interface preferred by most partners, this guide will largely focus on using control bsn cloud setup setups can be created using the free and unbranded bsn control interface at control bsn cloud setups can be saved to the setup library docid\ hzy2w0meeeryiforz9xfr to be used or modified in the future once created, setups can be applied to a player or group of players using control bsn cloud alternatively, the information contained in a setup can be directly incorporated into the player app (described below) and manually copied to the player’s storage device player settings the setup establishes various player settings which include things like publishing modes docid\ resciigy djrpuzgwaa4e , network settings (ethernet, wifi, etc ), player identification (name and description), logging, and more player app the set of files and folders that instruct the player what to do upon boot up is collectively known as the player app at a minimum, the player app must contain an autorun brs file (the brs extension denotes a brightscript file) which instructs the player what to do upon startup when a setup is applied to a player via bsn cloud, an autorun brs file is automatically created on the player partners can write custom player apps according to their specific needs for example, the player app may be designed to connect to the partner cms to download content from the cms for the player to display the term partner app may sometimes be used when referring to the partner’s player app more info about setups can be found setup docid\ xnnxywmv09iegziit7rwa and more info about provisioning can be found provision docid\ cyl9kpm02co5rgcb9wqqv provisioning & recovery docid\ jen 1oedb74 d94u8klyf