I have a 3 node, 2016 Datacenter cluster. Multiple VMs. Right now, all VMs are on hosts 1 and host 2. If I try to live migrate to host 3, I get event id 1069 and 21502. I can migrate between hosts 1 and 2 at will with no problem. Even when I try a quick migrate, the VM appears to move to host 3, but when I start it, it fails immediately.
The thing I've noticed is that I can access the Cluster Shared Volume from windows explorer on host 1 and host 2. If I try to access it on host 3 I get:
C:\clusterstorage\volume1 is not accessible. The referenced account is currently locked out and may not be logged on to.
The 1069 error reads:
Cluster resource 'Virtual Machine X' of type 'Virtual Machine' in clustered role 'X' failed. The error code was '0x775' ('The referenced account is currently locked out and may not be logged on to.').
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover
Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
The 21502 error mentions:
'Virtual Machine X' failed to start.'X' failed to start. (Virtual machine ID blah_blah)
'X' failed to start worker process: The referenced account is currently locked out and may not be logged on to. (0x80070775). (Virtual machine ID blah_blah)
'Virtual Machine Name Unavailable' could not initialize. (Virtual machine ID blah_blah)
'Virtual Machine Name Unavailable' could not read or update virtual machine configuration: The referenced account is currently locked out and may not be logged on to. (0x80070775). (Virtual machine ID blah_blah)
What account is it referring to? Shouldn't this be happening across all hosts instead of host 3?
Any help is much appreciated.