2nd instance of running into this issue. I will have to verify version number, but I believe the 4.x platform.. DW build.
Had several servers that were each licensed individually before merging via cloud/internet. Systems ran fine for a long period before one system dropped out of the hive with internet connection issues. After about 30 days the remaining merged servers decided to stop recording on cameras that should never have been impacted by the licensing... (Because I had activated the correct number of licenses on the servers before merging) The number of cameras that were Knocked offline and had their recording schedule turned off on the merged servers matched the number of cameras on the non-connectable server.
I remedied the situation by turning off the licenses related to the non-connected server and turning the recording back on for the cameras that took the hit with licensing.
I'm not sure what to expect if/when the offline server re-connects to this scenario.
So.. can it be clarified so I understand why the merged systems decided to stop recording due to license issues in this circumstance?
I had another group of servers behave this way today for a different customer. 2 systems that had been licensed prior to merging. One system dropped the connection to the cloud/internet, and the remaining system in the hive/group decided to deduct the licenses from the missing server from it's own remaining recording/functioning cameras. Customer lost a good amount of video unfortunately.
I'm guessing this is related to an approx 30 day grace period when a server with licenses referred to in a hive/merged group. This may be about defeating people trying to cheat on licensing or something similar, but it has caused some issues with our customers, and us when we aren't able to fix a missing server from the hive that can't connect.
Post is closed for comments.