The hyper-v virtual machine management service encountered an unexpected error logon failure 0x80070569

Question

I dont understand why Microsoft people can't make things simpler
They are LITERALLY MOTHER F%^%RS
Bill Gate and his team need to learn hot to F^&&IN make things.

Answer 1

I agree, the use of profanity is completely unnecessary, we've all been in the stressful situation before, it still doesn't call for it.
The network you're receiving an APIPA IP on, is it the virtual switch you setup when adding the Hyper-V role?  If so you can get the warnings to go away and subsequently hide the adapter by unchecking the 'Allow host to manage this adapter' setting
in the virtual network manager of Hyper-V manager on each node.
Tim is also right, while disk resources are only owned by one node, you'll see the mount points for CSVs located under C:\ClusterStorage.
More importantly, you're logon issue sounds directly related to group policy.  I had the same problem moving to Server 2012.  Yes, it's an annoying process but in the end you will have a working cluster.  I did the following steps:
1. Install 'Group Policy Manager' on one of the nodes in your Hyper-V cluster
2. Log on to the node you installed it on with a Domain Admin or appropriately endowed account that can edit the GPO relating to 'Logon as a service right'
3. Edit the GPO where you specify who can logon as a server, OR if you don't have one, make a new one and link it to the OU with the Hyper-V nodes
4. Add permission to that right for 'NT Virtual Machine\Virtual Machine Group', save and exit
5. As an optional step I would reboot the nodes so you make sure they get it
The problem here is that security group ONLY exists on servers that have Hyper-V installed on them.  If you add the group on a machine that has it to the GPO, the SID for the group is saved and each Hyper-V host will know what group that is.  The
problem you're having right now is most likely related to a GPO changing 'Logon as a service right' to your needs and setup in Group Policy.  When a Hyper-V node starts up, it automatically adds the right for that group to the local security policy, however,
group policy's auto refresh will remove it after a certain amount of time.