This page will ultimately be published in the FAQs section of our external docs. |
Windows 11 IoT LTSC (Long-Term Servicing Channel).
Security updates will be applied via the standard Windows Update feature. Importantly, however, Windows Update will not update the Windows version.
The following interfaces are supported:
Audio and video across all HDMI outputs. Required drivers are installed.
USB Audio and multi output. Required drivers are installed.
USB-A
The following items will only function while the bootloader is loading and have no function once Windows has booted up:
Buttons (e.g., SVC, reset)
3.5mm serial port
The following interfaces are not supported:
USB-C
GPIO
HDMI-CEC
IR
What storage devices are supported?
microSD card
USB-A connected storage (e.g., USB-A thumb sticks, USB-A drives)
SSDs (M.2 form factor)
For more info about compatible storage devices, please visit https://brightsign.biz/storage. |
No. BrightScript requires BrightSignOS. The OS on this player is Windows.
No. Functionally, this is a Windows PC.
No. Functionally, this is a Windows PC.
Yes. Functionally, this is a Windows PC so you can install Chromium or any other Windows-compatible browser.
The player’s serial number can be found on the label on the bottom of the player. The serial number cannot be determined from within Windows.
The Windows registry can be accessed just as with any Windows PC. Refer to Microsoft’s registry documentation.
No. If you need CEC control, please consider our standard players based on BrightSignOS.
No.
For Windows related issues, please contact your reseller or Microsoft.
For hardware related issues, please visit support.brightsign.biz.
The notes below are from Ben’s original document. They are being left here temporarily for reference only and will be eventually deleted. The above section is what will be published publicly. |
How to update to BrightSign provided UEFI bootloader?
nb: currently not supported
at scale?s
How to update from a BrightSign provided UEFI bootloader to a newer BrightSign provided UEFI Bootloader?
nb: currently dont support
at scale?
How to determine the version of the player?
BrightSign Version?
There is not a 'brightsign version'
UEFI Version?
Same as normal Windows process
BrightSign UEFI Bootloader Version?
Remove the SSD and check the splash screen
BrightSign Windows Agent (Windows Installer App) Version?
Communication with Brightsign
Windows Version?
Same as normal Windows process
How does a end user apply a Recovery Image?
Greg Herlein Jonathan Dye Andrew Saul - if a user needs to recover the Windows system with a Recovery Image, will they leverage the existing image or do they require a recovery image? (Aaron Rollins Matthew Neutra ) need to determine whether this is an image distributed by the Support Team or publicly accessible.
Notes (very rough - WIP will be formalizing these 10/30):
(Eng / Product) do we have a hardening guide
Refer Customer to Windows Support
(Nick ) create generic macro to point to windows support
(Product / Sales) publicizing or providing details on "how powerful the player is". How does a customer determine performance between XC5 vs other PCs.
(Product) guide to specs on Windows relative to XC5 and how to answer sales and suports questions
potential recommended security software to install that we have confirmed works fine
is there a different bootloader screen or indicator displayed? UEFI Bootloader..
(Product / Matt) Sticker on the XC5 player case: "Powered by Windows" (Matt / Ben)
(Product) there is an shipping guide explaining where / how to place the sticker on the XC5 Windows unit
can someone remove the SSD and duplicate the image to another SSD? from a support perspective? from a product perspective?
technically yes
malicious user: the unit should be physically locked down if this is a concern
genuine user: No. End users cannot duplicate SSDs. It's the case N number of registration keys are required for N units.
does the unit support random mac address? booting into recovery?
share edit access to the document with Support?
can we re-flash an SSD with a windows image?
to test:
try all-partition update to revert back to BOS Bootloader