control.bsn.cloud

bsn control is a solution that allows partners to automate new player set up through device provisioning (also known as b deploy), monitor networks through brightauthor\ connected, and examine problems through a remote diagnostic web server this page will go over the basics on how to use these new features to manage brightsign players in your network the bsn control can be accessed through control bsn cloud http //control bsn cloud device provisioning (b deploy) device provisioning is a service that allows for automated provisioning of brightsign players over the internet in order to use device provisioning, cms partners need to provide and maintain an application url on an accessible http file server host the package should be contained in an autorun zip file containing presentation files along with an autozip brs boilerplate script in most cases, the script will not need to be modified once the package has been hosted, device setups made through brightauthor\ connected can point players directly to the application url open brightauthor\ connected and sign into bsn cloud to select the cloud network desired under device setup , two options make use of externally hosted applications the custom application url option requires the link to be manually input into the field the partner application option provides a drop down menu of applications that have been officially registered with device provisioning servers to get an application url added to the drop down, contact the partner integration team add the setup file to the library when done go to device provisioning in the admin tab select add device and enter the serial number of all players desired this process will register the player to currently selected bsn cloud network from here, check mark the boxes of all players and apply the setup alternatively, clicking download template will download a microsoft excel file that contains columns for serial number, device name, setup file, application url, and description the excel sheet can be used to help expedite the process by adding multiple serial numbers simultaneously and automatically assigning them setup files and application urls when everything is entered correctly, the player should automatically query the device provisioning servers when connected to the internet and powered on the device provisioning servers will then assign the players the corresponding setup files and point to any application urls entered, and the player will automatically configure itself and play any presentation files contained in the autorun zip re provisioning vs factory resetting a player cloud connected players should be re provisioned rather than factory reset, if they must be refreshed if the player to be re provisioned is currently configured on a network which requires a specification configuration (security, certificates, etc ) or is a wi fi player, choose use current device settings in device setup > network configuration on the bottom left to maintain your player's current network configuration factory reset should only be used if you have local access to the player since it deletes all registry sections and clears network interfaces the factory reset may leave a remote player in an inaccessible state (it would only be possible to factory reset a player and reconnect to bsn cloud if the user has a "device provisioning" entry in brightauthor\ connected, and their network allows a rogue device to retrieve an active ip address for a b deploy connection) diagnostic web server for internet connected players, bsn control offers remote access to the diagnostic web server (dws) the dws provides the ability to view key info about players, access to diagnostic tools for troubleshooting, the ability to modify player settings and apply os updates, and much more to access the dws, open brightauthor\ connected (either the desktop app or the web app at control bsn cloud) the network tab provides a list of all registered players on the network enter the player's dws by clicking the gear icon to the right of the desired player for complete details about the dws, see diagnostic web server (dws) docid\ qxt4yhey7iej m9dh73wm