Provision

overview as covered in the brightsign primer docid\ d1tz0hy4bh9ngcvuoe3of section, setting up a player for use involves applying a setup docid\ xnnxywmv09iegziit7rwa to the player, and applying a setup file to a player using brightsign cloud is known as provisioning when powering up a new or factory reset docid\ yncf7p2pyzo2qedf1jyim player that has previously been provisioned, the player will automatically retrieve and apply the setup file that was previously applied to it in many cases, it is best to provision the player prior to powering up the player players can be provisioned using the methods described below, and once provisioned, the player will configure itself per the applied setup file upon bootup image 20241218 183242 png prerequisites you must be logged in to a brightsign cloud account note the player serial number, which can be found on the bottom of the player or on the side of the packaging box connect the player(s) to an active network connection and to a display screen through hdmi ® the player(s) must have a blank, properly formatted storage device you must have a setup file docid\ xnnxywmv09iegziit7rwa note the setup file name make sure that the setup file is in the library (when creating the setup file, choose add setup to library ) provisioning individual players add player go to admin > provision select add player to add a player to the provisioning list you will be prompted to enter the following information serial number the serial number of the player player name and player description an optional name and description for the player if these are not specified, the values in the setup will be used image 20241218 183334 png player already registered if you enter a serial number of a player that has already been provisioned, you will get an error as shown to the right if the player was brand new when obtained, then you or someone in your organization likely already provisioned the player and you should be able to find the player in the player provisioning list however, if the player was previously owned and provisioned, the previous owner / administrator must delete the player's provisioning record from their brightsign cloud network before you can provision the player for your brightsign cloud network for security reasons, only the current administrator of a player is able to delete that player's provisioning record brightsign is generally unable to remove player provisioning records if you have a player that was previously provisioned, contact the previous owner / administrator and request that they delete the player's provision record docid\ cyl9kpm02co5rgcb9wqqv apply setup from admin > provision select the checkbox next to the player(s) you want to provision select apply setup if the players have not been previously provisioned, they will download the appropriate setup from the brightsign cloud servers when they boot up if the players have had a setup file applied previously, the new setup file will take effect only when that player has been explicitly re provisioned it is important to note that apply setup strictly establishes what should be applied to the player when the player is re provisioned if a previously provisioned player reboots or even if it is factory reset, it will not adopt the new setup until the player has been explicitly re provisioned re provisioning is covered below the apply app url option lets you assign an application, via a player accessible url, to selected players in the list upon boot up, the players will download the application package from the specified app url and set up the player for that application app url will shortly be renamed to cms url image 20241218 183436 png you can also delete player(s) from the provisioning list if you delete a player's provisioning record, it will be disassociated from its brightsign cloud network and will no longer automatically retrieve a setup package from brightsign cloud when a player is booted up without an associated provisioning record, it will display an activation code, which you can use to create a provisioning record for the player other methods of provisioning the player are the brightsign author provision tab or the b deploy api bulk provisioning bulk provisioning is the process of provisioning multiple players at once go to admin > provision select the download icon to download the provisioning template as a csv file enter the serial number (required) player name setup name (required) app url description save the csv file select upload provisioning file to upload the saved csv file once the file has been uploaded, players listed in the file will be automatically provisioned per the file review the player list for bulk provisioning and select submit the players will automatically download and apply the new setup files from the cloud note that the csv template includes a column for setup as well as app url if a player is desired to be provisioned for app url, it can be done with a setup file where the setup file includes the app url information alternatively, the app url can be directly entered in the csv file, negating the need for a setup file if a setup file that includes an app url is specified and an app url is entered in the csv column, the app url in the setup file will take precedence default provisioning if a setup file is not explicitly applied to a player, the default setup docid\ xnnxywmv09iegziit7rwa will be applied to the player when it is provisioned reprovisioning as mentioned above, apply setup strictly establishes what should be applied to the player when the player is reprovisioned if a previously provisioned player reboots or even if it is factory reset, it will not adopt the new setup file until the player has been explicitly re provisioned the re provisioning process performs the following actions clears the player storage clears the registry settings used by brightsign cloud but retains some register settings, specifically the player’s networking settings (e g , wifi configuration) reboots the player upon reboot, the player will download and apply the setup file associated with its provisioning record if no setup file has been applied to the player, the player will boot to the activate docid\ oof rmqhqfvlhokxi8ypj screen re provisioning a player consists of the following steps apply a new setup file to the player when a player is added (either via provision > add player or via a provisioning file using the provisioning template) with no setup file explicitly applied, the default setup file will be applied explicitly re provision the player so that the new setup takes effect apply a new setup to re provision the player, first go to admin > provision where you should see your player(s) listed from here, follow the steps below image 20241218 203140 png select the player from the list multiple players can be selected to apply the same setup to click apply setup image 20241218 203300 png 3\ a pop up will appear with a drop down list of all the setup files in the setup library choose the desired setup file from the drop down list and click apply setup reprovision the player when a new setup file is applied to a player, the new setup file does not automatically go into effect on the player after applying the setup file, the player must be explicitly reprovisioned (after which the player will reboot) in order for the new setup file to be active on the player find the player in the network tab and select the settings (gear) icon image 20241218 203424 png from there, navigate to the control tab, reprovision player note the actions that will occur and select reprovision image 20240424 184507 png there may be a message asking to confirm that there is indeed a setup that has been applied to the player if a setup has not been first applied to the player, the player will connect to bsn cloud to download and apply the default setup deleting a provision record go to admin > provision and delete the player from the provision table by clicking the delete (trash can) icon go to the network tab and find the player click the gear icon to access the player's rdws navigate to the control tab of the player’s rdws and click the reprovision button which will cause the player to reboot since no setup has been applied to the player, the player will boot to the activate docid\ oof rmqhqfvlhokxi8ypj screen after the player has rebooted, go the network tab and click the delete (trashcan) icon to delete the player from the network this is more of a housecleaning step and while recommended, is not strictly necessary if not done, the player will continue appearing in the network tab but show an inactive status brightsign does not remove provision records from players because of the potential for theft we also do not provide information about the network they are provisioned to for privacy reasons if you purchase a secondhand player, the seller must remove the provision record if an ex employee is the only administrator on the bsn cloud network, your it department must access their email to reset their password and remove the network provision record/add administrators reprovisioning vs factory reset users should understand some key differences between reprovisioning and a factory reset docid\ yncf7p2pyzo2qedf1jyim reprovisioning applies a new setup without affecting network settings, while a factory reset is a more comprehensive reset that clears all settings reprovision factory reset clears the player storage does not clear the player storage clears most registry settings but importantly does not clear the player’s network settings (e g , wifi configuration) clears all registry settings including the player’s network settings if a new setup has been applied, the new setup will take effect upon bootup if a new setup has not been applied, the player will boot to the activation screen does not affect the player’s provisioning record on bsn cloud the player’s setup on record will be applied again after the player boots back up changing the player’s setup requires reprovisioning the player additional info see this video https //vimeo com/350338863 for more information about provisioning players and creating player groups to display different setups in different groups pdf version