I ran into an issue when I introduced a second Hyper-V host to a non-domain environment, and to make things play nice I decided to create a Server 2012 VM and set up a domain. Everything went fine and I'm now using SMB3 shares for storage and able to use live migration.
I forgot to think about time sync before joining, though (I went through this months ago when I tried out a Samba4 DC). After I joined the 2 Hyper-V servers, everything pretty much started fighting over where to sync from....
Hyper-V Virtualized Domain Controllers & Time Sync![]()
I forgot to think about time sync before joining, though (I went through this months ago when I tried out a Samba4 DC). After I joined the 2 Hyper-V servers, everything pretty much started fighting over where to sync from....
Hyper-V Virtualized Domain Controllers & Time Sync