"The reboot meant every client of ours was uninsured for the eight minutes it took to reboot the server."
By the sounds of it, the design of the policy update process means that, even in the absence of any unexpected server reboots, all of their clients would regularly suffer periods of being "uninsured" (as in, *appearing* to be uninsured due to their policy not showing up on MID, though not *actually* uninsured through not having a policy in the first place) for however long it took to upload the new data having first wiped the old data each time the update process was run.
Biting the hand that feeds IT
