Hate to bring up an old thread as well but I've run into this issue a few times now. We are running ESXi 5.5 U2 and this problem seems to have appeared after applying some security patches (or at least I didn't notice it until then). The process mentioned in the VMware KB works however I've been afraid to disable the service all together as I'm not sure why it's running in the first place. We also do NOT use VSAN. Does anyone know why this is enabled?
↧
