Anyone got any ideas on what this error may have been triggered by? Totally at random on a Monday morning and obviously we weren’t changing anything over the weekend!
Could it be one of the issues resolved in the latest ESXi 6.7 patches (ESXi670-202008001), we have been slowly upgrading our hosts to this latest update but will get our skates on if neccessary! 🙂
View Reddit by k6kaysix – View Source