Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
A BrightSign player can download its autorun script and other presentation assets from a URL value stored in its registry. This feature can be used to provision a player in the field. It also allows a player to automatically recover from run-time or load errors associated with the autorun script.
...
This page outlines how to set up a provisioning system that uses DHCP Option 43.
Note |
---|
NoteThe /wiki/spaces/DOC/pages/6543661 B-Deploy Appliance may also use DHCP Option 43. The solution outlined on this page makes use of a third-party provisioning server (i.e. one you set up yourself) rather than the B-Deploy Appliance. |
...
Parameter | Example Value | Description |
|
| The |
|
| The |
|
| The |
|
| The |
|
| The model designation of the BrightSign player |
|
| The family designation of the BrightSign player |
|
| The serial number of the player |
|
| The version of firmware currently installed on the player |
|
| The amount of time (in seconds) since the player booted up |
|
| The mode of the current URL request:
|
|
| A flag indicating that the current boot was initiated by a forced reboot due to a crash (this header is only present if true) |
|
| The current autorun and file-system status of each storage device. |
...
The provisioning script should, in turn, overwrite the recovery URL in the registry and download the provisioning package from a separate URL.
Note |
---|
NoteBy default, IIS servers do not allow .brs files because they are not a registered MIME type. If you're using an IIS server to distribute the .brs provisioning script, make sure to register .brs as a "text/plain" MIME type. |
...