I should acknowledge up-front that my network is now a mess. I will state my problem but will also clarify a large variety of things that are in various stages of broken.
I have installed Hyper-V 2016 on a standalone workstation (eventually I hope to get a virtualized instance of Windows Server 2016 Essentials running there as well). I have installed the RSAT tools on a Windows 10 Professional laptop. Things go wrong for me at Step 13 when I expect to see the Hyper-V server in the management console ready to be managed but instead I see "kerberos authentication error". I disabled the firewall on the Hyper-V server hoping that would help (it did enable me to ping the server), but there was no change in behavior.
At this point the broken-ness of my network becomes relevant...
I had been running with Windows Server 2012 Essentials for several years. I attempted to migrate from 2012E to 2016E but ended up with two servers that see each other but don't cooperate. I finally gave up fixing this and decided to start with a clean installation with the old server turned off. But my other WIn10 machines, from which I have uninstalled the client connector, still remember the (now serverless) domain. I have created local accounts on my laptop and attempted to use them to connect to the Hyper-V server, but to no avail. Every attempt results in a complaint about kerberos.
So I don't know if my problems are related to vestiges of the old domain or some other configuration issue, but I sure would appreciate help figuring out how to start making progress again.
If you get the "kerberos authentication error" this is caused in most cases by not following step 8,9 and 10. Did you complete all steps?
I attempted to migrate from 2012E to 2016E but ended up with two servers that see each other but don't cooperate.
Did you have network problems? Migrating from 2012 to 2016 should be really easy. Did you follow my guide? If so, why did you not ask for assistance?
To the first point, I did follow all steps. I did more experimenting this morning and believe the issue is with the vestiges of domain membership on the client machine. I have one laptop that was more thoroughly removed from the domain (removed client connector software AND switched from Domain to Workgroup in System window) and I was able to make the connection from that machine using local credentials, as per the tutorial.
To the second point, I did not follow your guide. I attempted to do it using Microsoft's useless^H^H^H^H^H^H^Hincorrect online instructions. I joined this site after the wasted hours and the damage was done (a false economy, to be sure) when I decided to just start over.
Yes, the tutorial is part of a series that explain how you build a virtualized network the cheap way for SMB's. That means you start from scratch installing Hyper-V core and connecting to that server with a non joined client. All the relevant guides can be found here https://server-essentials.com/support/cid/34?category=virtualization. Sorry to see you had such difficulties!
My guides are tailored to the scenario, which is in the title of each guide and leads to success.