Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This page outlines how to set up a provisioning system that uses DHCP Option 43.

...

Note

The 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.

Overview

Recovery/Bootstraping

When a BrightSign player boots (and at periodic intervals while running), it will direct an HTTP GET request at the provisioning/recovery URL stored in the player registry, which is blank as a factory default. The header of the HTTP GET request includes the following parameters:

Parameter

Example Value

Description

Account

bsaccount

The a registry value

User

bsuser

The u registry value

Group

bsgroup

The g registry value

Password

bspassword

The p registry value

DeviceModel

XD1230

The model designation of the BrightSign player

DeviceFamily

cheetah

The family designation of the BrightSign player

DeviceId

X2F2CU0000065

The serial number of the player

DeviceFwVersion

4.7.146

The version of firmware currently installed on the player

DeviceUpTime*

240

The amount of time (in seconds) since the player booted up

RecoveryMode*

override

The mode of the current URL request:

  • override: The initial HTTP GET request of a player with a valid autorun script

  • periodic: Subsequent HTTP GET requests of a player with a valid autorun script

  • last-resort:  The HTTP GET request of a player without a valid autorun script

CrashDump*

yes

A flag indicating that the current boot was initiated by a forced reboot due to a crash (this header is only present if true)

StorageStatus

usb1=none;sd=autorun;

sd2=storage;ssd=none;

The current autorun and file-system status of each storage device.

If the HTTP GET request is successful, the player will attempt to utilize whatever content was downloaded as an autorun script. Note that the player does not make any checks to determine if the content is actually a .brs autorun file before attempting to run it.

...

The provisioning script should, in turn, overwrite the recovery URL in the registry and download the provisioning package from a separate URL.

...

Note

...

By 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.

The provisingScript.brs file included with this document provides a template provisioning script for downloading a presentation package and/or firmware file. To use this script, you will need to replace the following values in the script with values that are specific to your application:

...