Inherited Players

if you have inherited an existing brightsign player, here are some tips to help you understand and use the players the most important things to know are which content management system (cms) app was used? this could be brightsign author , , or a partner cms which publishing mode docid\ resciigy djrpuzgwaa4e did that app use to publish content to the player? these apps support multiple content publishing modes brightsign author was called brightauthor\ connected prior to august 2026 determine cms & publishing mode to determine how content was published to the player, you can search the computer that was used for setup (if you have access to it), check the contents of the player's microsd card, or access the player through the local diagnostic web server these methods are described below computer access if you can access the computer that was used to create the presentations, search for a brightsign author, brightauthor classic, or partner cms app if brightsign author is installed on your computer, open it you may need the login credentials of the previous user or may need to create your own account go to the network docid\ uba8sfkmsajsibrbv4a6n tab to see the players' publishing mode (standalone, local network, web folder, etc ) if brightauthor classic is installed on your computer, open it you may need the login credentials of the previous user or may need to create your own account go to the manage docid\ zazqgxtu6iu8ogeteuget tab to see more about your setup if neither brightsign author or brightauthor classic are visible on the computer, search for one of our partner apps the brightsign partner network | brightsign® https //www brightsign biz/partners/?tab=cms if you find their app on the player, check their website for more information card method copy the microsd card information from the player to your computer using a card reader to see if brightsign author ( brightauthor\ connected), brightauthor classic, or cms partner files are on the card if you see xml files on the card, the brightauthor classic cms was used to determine the content publishing mode if you see a local sync xml file, your player was not set up for the cloud and uses either local file networking or standalone the contents of the setup xml file will help you determine which publishing mode was used to publish content to the player if you see a current sync xml file , your player is set up for the cloud and uses either bsnee or brightsignnetwork com http //brightsignnetwork com simple file networking if the current sync xml file is pointing to a custom url (the customer’s simple file networking server), then it is set up for simple file networking if you see json files on the card, brightsign author was used to determine the content publishing mode if you see a local sync json file, your player is not set up for the cloud and was using either local network or standalone if you see a current sync json file, your player is set up for the cloud and is using bsn cloud web folder (formerly simply file networking) if the current sync json file is pointing to a custom url (the customer’s web folder server) then it is set up for web folder here are examples of microsd card contents from some brightsign cms partners ip access method you can also enter the ip address of the player into a browser to access the local diagnostic web server (local dws or ldws) local access (i e , access over the local network) of the diagnostic web server (dws) is disabled by default as of brightsignos 9 0 218 (on the 9 0 branch) and brightsignos 9 1 75 (on the 9 1 branch) in brightsignos versions prior to these, local access to the dws was enabled by default to enable local access to the dws, see dws local access docid\ iafcherljfjdjtwttkpk5 note that some specially configured players have the external microsd card port and usb storage disabled at the factory (sku svc internal storage only) for these players, local access to the dws remains enabled by default remote access (i e , access over the internet) of the dws remains available for all internet connected players registered with brightsign cloud to enable the local dws, see this page docid\ iafcherljfjdjtwttkpk5 once enabled, the local dws follow these steps to access it open a web browser enter the player ip address in the address bar you should now have access to all the features of the local dws (see dws remote access docid\ xue20rjxhft lq0rdmjbw for more information) which will help you understand the publishing mode of the player other if you can’t access the microsd card but do have the player's serial number, you can send that info to the brightsign support team for further assistance brightsign author/brightauthor classic recovery ask your it team to give you access to the admin email account that was used to register the players and then reset the network account password after which you can add a new admin email to transfer ownership (try to use a generic email account rather than your personal email) you can also c lear the provisioning record on the player to reconfigure it with a new network or setup file next steps once you have determined the cms and setup type of the player, see the following resources to add a new player to your deployment, or to better understand how the existing players are set up, see ⭐ player setup docid\ rcuhsqujj1ethbhvt46xi to create a new presentation through brightsign author, see publishing quickstart docid\ czguhz omw1rsbpfddpah to create a new presentation through brightauthor classic, see create presentations docid\ gft1eg7a u950gji4cabf if you are publishing content to a player through a partner cms, see the brightsign partner network | brightsign® https //www brightsign biz/partners/?tab=cms or their website for more information to upgrade to series 5 players, see brightsign series 5 digital signage players https //www brightsign biz/brightsign players/series 5/ to upgrade to series 6 players, see brightsign series 6 digital signage players https //www brightsign biz/brightsign players/series 6/