Came across an interesting issue today at a customer site where they have 2 Hyper-V host that are not domain joined but are in VMM. They had noticed that VMM could no longer talk to them.
When you add a Host to VMM that is not domain joined, VMM creates a Run As Account and adds this to be a local admin on the Hyper-V host. What it doesn’t do is set the account up in such a way as the password does not expire… Yes you guessed it, the local account was sitting there at “user must change password on next login” as it had expired.
Set a new password on the host, update the Run As Account in VMM, refresh and all is well once more 🙂