In case someone struggles with this in the future, this turned out to be related to replication. I can't recall if it was a patch to ESX or an update to vSphere Replication, but one (or both) of those fixed the problem.
↧
In case someone struggles with this in the future, this turned out to be related to replication. I can't recall if it was a patch to ESX or an update to vSphere Replication, but one (or both) of those fixed the problem.