Example (CMS URL/App URL)

in this example, we will be provisioning a player to use the cms url/app url publishing mode and brightsign author players can also be provisioned in the brightsign control player setup section player preparation to better reflect the most likely experience of a real world user, we will proceed as if the player is brand new if you had previously used the player to follow along with the manual setup example, you can simply erase/reformat the storage device and reinsert into the player since the player was not explicitly provisioned with bsn cloud (the default setup was used), the player does not need to be reprovisioned if you had previously activated the player for use with bsn cloud, however, refer to the directions here docid\ cyl9kpm02co5rgcb9wqqv on how to delete the player’s provisioning record and then return here in this example, we will be provisioning the player prior to booting up the player for the first time if a new player does not already have a provisioning record with bsn cloud, powering up the player will take the user to the activate docid\ oof rmqhqfvlhokxi8ypj screen activation provisions the player with the current default setup file unless another default setup file has been created, the player will be provisioned with the brightsign default setup file which uses brightsign author plus (bsn content) as the publishing mode reprovisioning the player would then be required to apply a different setup file provisioning the player prior to activating the player thus saves the step of having to reprovision the player provision player do not power up the player write down the player’s serial number the serial number can be found on the label on the bottom of the player itself or on a label on the box that the player was packaged in go to admin > provision > add player enter the serial number you wrote down if desired, you can also enter an optional player name and player description select add player the player should now appear in the list of players note that it has been assigned the default setup file if you have not explicitly created a new default setup file, this default setup file will be the brightsign default setup file next select the player you wish to provision this should be the player with the serial number you just added above select apply app url from the drop down menu in the pop up window, select app url and enter the url where the desired autorun zip file resides if you like, you can use the example url here https //www brightsign biz/examples/autorun zip https //brightsign biz/examples/autorun zip select apply the player is now provisioned for the cms url/app url publishing mode all of the other player settings, since they have not been explicitly changed, remain per the brightsign default setup power up player power up the player once the player has booted, it will search for a provisioning record on bsn cloud if a record is found, the player will apply the settings according to its provisioning record since we created a provisioning record for this player in the previous steps, the player will apply those settings in this case, the provisioning record instructs the player to go to the designated url, download the autorun zip file there, unzip that file, and then reboot to run the autorun brs within the autorun zip file the autorun brs file has been configured to display the html presentation contained in the autorun zip file the same presentation that was previously displayed with the manual copy example should now be shown on the screen whereas with the previous example, the autorun zip file was manually copied to the player’s storage device, the player now has been remotely provisioned to retrieve the autorun zip file from a url next developer tools > docid\ wfjrzubbuvewohjo tf3q