So between this bug
Yes I feel it's fair to consider this a defect, it worked this way for years and now it does not. I feel it was both reasonable and responsible for us to build firewall rules around this legacy behavior
and this bug:
I am posed to have some headaches when my licenses expire here shortly. I would like to get ahead of this by triggering the probes that have expiration dates to go update the epoch timestamp in the expire.cfg file BEFORE my expiration date hits, without having to either corrupt the expire.cfg checksum (thus forcing the robot to recreate this file with the updated epoch time) or redeploy the probe.
Does anyone know how to get the probes to update this timestamp outside of the two ways I listed above? I am guessing not but thought I would ask.