Veeam Cloud Connect RevocationStatusUnknown: the CRL cache, not the intermediates
How a misleading RevocationStatusUnknown error turned out to be Veeam reading the Windows CRL cache without populating it, and why my first fix only looked like it worked.