Windows device identity and cloned images
Every signageOS device has a device UID. On Windows the Core App generates it on first start from the hardware and stores it on the machine, so the device keeps its identity across restarts, upgrades and reinstalls. If you deploy Windows machines from a disk image, read this guide before you capture the image.
How the device UID is stored
The Core App resolves the UID in this order on every start and uses the first value it finds:
- The file
C:\signageOS\fileSystem\root\.cache\device-uid - The registry value
HKLM\SOFTWARE\signageOS\DeviceUid - A fresh value generated from the hardware (Core App 3.2.1-rc.5 and newer): the SMBIOS UUID, then the serial number of the system disk, then a value derived from the BIOS serial number
Both stores survive an application upgrade and an uninstall, so a device that is reinstalled keeps its registration.
Core App versions 3.1.1 to 3.2.1-rc.4 generated the UID from values that Windows copies with the installation (ProductId or MachineGuid). On those versions every clone of an image shares the UID even when the stores are empty. Use Core App 3.3.0 or newer on any image you intend to clone.
Prepare an image for cloning
An image captured from a machine where the Core App has already started carries that machine's UID in both stores. Every clone then connects as the same device. sysprep /generalize does not remove the signageOS registry key, so clear it yourself.
On the master machine, after the Core App is installed and before you capture the image, run in an administrator PowerShell:
Stop-Service signageosserver.exe
Remove-Item C:\signageOS\fileSystem\root\.cache\device-uid* -Force -ErrorAction SilentlyContinue
Remove-ItemProperty HKLM:\SOFTWARE\signageOS -Name DeviceUid,DeviceUidFingerprint -ErrorAction SilentlyContinue
C:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe /shutdown
Each clone then generates its own UID on first boot and shows a verification hash for pairing.
Symptoms of a shared identity
- A newly installed machine reports that the device is already registered instead of showing a verification hash.
- One device in Box keeps going online and offline, or its serial number and screenshots alternate between two machines.
- Content or settings assigned in Box appear on a different machine than expected.
Check which UID a machine uses
In an administrator PowerShell on the machine:
Get-Content C:\signageOS\fileSystem\root\.cache\device-uid -ErrorAction SilentlyContinue
(Get-ItemProperty HKLM:\SOFTWARE\signageOS -ErrorAction SilentlyContinue).DeviceUid
(Get-CimInstance Win32_ComputerSystemProduct).UUID
(Get-CimInstance Win32_BIOS).SerialNumber
The first two lines are the stored UID. If two machines print the same stored UID but different BIOS serial numbers, they share an identity. The third line is the SMBIOS UUID the Core App would generate from on this hardware. Some boards report the placeholder 03000200-0400-0500-0006-000700080009 instead of a real UUID; the Core App rejects it and falls back to the disk serial number.
Repair a machine that shares an identity
Repair only the machines that should get a new identity. Leave the machine that already owns the device record in Box untouched, otherwise it loses its registration too.
The machine comes back as a new device and has to be paired in Box again. Its applet, settings and policies are assigned to the device record, not to the machine, so reassign them after pairing.
Core App 3.3.0 or newer. In an administrator PowerShell:
Stop-Service signageosserver.exe -Force
Stop-Process -Name SignageOS.KioskApp -Force -ErrorAction SilentlyContinue
Remove-Item C:\signageOS\fileSystem\root\.cache\device-uid* -Force -ErrorAction SilentlyContinue
Remove-ItemProperty HKLM:\SOFTWARE\signageOS -Name DeviceUid,DeviceUidFingerprint -ErrorAction SilentlyContinue
Get-ChildItem C:\signageos\frontend, C:\Users\*\AppData\Local -Filter SignageOS.KioskApp.exe.WebView2 -Directory -ErrorAction SilentlyContinue | Remove-Item -Recurse -Force
Start-Service signageosserver.exe
The Core App generates a new UID from the hardware on this start. The kiosk browser profile is removed as well, because it keeps the previous device's state and would show the old pairing screen otherwise. Downloaded content stays on the machine.
Core App older than 3.3.0. Upgrade the machine to the latest Core App first, from Box or by reinstalling. The upgrade keeps the current UID, so the device stays reachable. Then run the commands above.
Machine without the Core App installed. If the Core App was uninstalled, or the clone has not been installed yet, only the registry value is left. Remove it before installing:
Remove-ItemProperty HKLM:\SOFTWARE\signageOS -Name DeviceUid,DeviceUidFingerprint -ErrorAction SilentlyContinue
Installing the Core App over a leftover registry value makes the fresh installation connect as the old device again.
PowerShell must run as administrator for every command on this page. Without elevation the registry commands fail silently and the machine keeps the shared UID.
After the repair, the machine shows a verification hash. Pair it as described in How to add a new device via Box.