Hello. Regarding the article.
https://na4.salesforce.com/articles/Case_Summary/Probe-license-update-is-not-working?popup=true
I am sorry that you have headache.
You are right what you mentioned.
Redeploy probe from distsrv (which has new license info) to robot will update expire.cfg with probe's new license expiration date.
This would be actionable if there are few probes to remedy.
Move expire.* from robot directory, then restart controller will force robot to retrieve new lincese from distsrv and re-generate expire.cfg with the latest license info.
It is expected to work because controller restart is involved in the step. However, the article mentioned, controller restart is necessary.
Thanks
Yu Ishitani