Back in 1.8.2 you guys implemented an excellent feature that prevented a display from duplicating in the CMS if Xibo was run under two or more user accounts(thank you very much for that, by the way). Would it it be at all possible to do the same thing when Xibo is reinstalled on a player?
I just had to re-image one of our players, and while the hardware is all the same, it’s pulled a whole new hardware ID and there are now two identical players in the CMS. It’s going to take a bit of time to redo all of this player’s scheduling, so if there’s any way this could be prevented I’m sure all users would appreciate it!
You probably could copy the hardware key from the ‘old’ entry to the new one - or rather to be clear change the hardware key in the player’s options to match the ‘old’ hardware key you can get from CMS.
and then remove the ‘new’ record from CMS.
Just a thought, but it might be easier/faster than re-creating schedule etc.
Now regarding the hardware key itself, when you just reinstall the player then it will preserve the hardware key, but if you re-image whole system then it will generate new hardware key, we could try to implement some additional checks for that, but it might not be so straightforward to ensure that it won’t cause different issues.
