locked
Hyper-v 2016 Core configuration for replica RRS feed

  • Question

  • I have a situation here.

    HOST01 - Windows 2016 Hyper-v GUI mode, joined to the domain and has 2 VM's - existing

    HOST02 - Windows 2016 Hyper-v Core mode- new to replicate the VM's from HOST01

    When i join the HOST02 to the domain, i cannot even manage the server from my laptop using Hyper-v manager. So its standalone.

    If its standalone, i can connect from my laptop and also from HOST01 Hyper-v manager. Now the problem is when i try to configure replication from HOST01 to HOST02 its not connecting to HOST02 with kerberos error.

    Error comes as.

    Hyper-v failed to enable replication

    hyper-v failed to authentocate using kerberos authentication

    the specified target is unknown or unreachable (0x80090303)


    • Edited by BN04 Saturday, February 1, 2020 5:10 PM license
    Saturday, February 1, 2020 12:35 PM

Answers

  • Hi BN04,

    Thanks for your post!

    1. Firstly, agree with Tim, please check if the replica server is licensed, this is the Prerequisite of the following troubleshooting steps.

    2. If the replica server is licensed, the issue still exists, please try the following things:

    a. Please check if the replica Server join the domain correctly, check the secure channel between the replica server and the DC. We may also try the rejoin the replica server to the domain.

    b. Please check if the replica server's FQDN recorded in the DNS server correctly, if not, we may add the A record manually.

    c. Please check if the firewall port for replication and Kerberos authentication is opened, we may try to turn off the firewall on the Servers for test.

    Thanks for your time! If you have any concerns or questions, please feel free to let me know.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by BN04 Monday, February 3, 2020 5:26 PM
    Monday, February 3, 2020 8:26 AM
  • While I certainly appreciate you citing my articles in a response to my response, I must point out that the exact one that you linked only covers 2012 R2. None of the articles that you cited include a discussion on replica. I have a much newer one that does a more applicable job than that one

    Bottom line: If your host contains a replica of even one Windows Server VM, then you must treat it as a normal VM running a full, active copy of Windows Server. The host must be licensed for that. Using Hyper-V Server does not absolve you of your licensing responsibilities. If you have not paid for a license on that host, then you are out of licensing compliance and subject to software piracy fines up to $150,000 per incident. And, they pay bounties to people that report violations. That qualifies as a "real problem" in my book, much more than any temporary technical problem.

    If you want your lawyers to vet what I'm saying, this is the only document that matters: https://www.microsoft.com/en-us/licensing/product-licensing/products. The use of replica without a license is specifically covered as a Software Assurance benefit ONLY (page 92 in the English edition).


    Eric Siron
    Altaro Hyper-V Blog
    I am an independent contributor, not an Altaro employee. I accept all responsibility for the content of my posts. You accept all responsibility for any actions that you take based on the content of my posts.


    • Edited by Eric SironMVP Monday, February 3, 2020 6:39 PM
    • Marked as answer by BN04 Monday, February 3, 2020 9:07 PM
    Monday, February 3, 2020 6:37 PM

All replies

  • "Windows 2016 Hyper-v Core mode(to save license) "

    This is not a legal forum set up to address licensing issues.  But it looks like you should check with a trained Microsoft licensing specialist about your assumption on licensing.  Running Hyper-V Server (I think that is what you mean by 'Hyper-V Core') does not change any licensing requirements for running VMs.  Microsoft licenses at the physical host level, not at the VM level, in order to have consistent licensing no matter what hypervisor is running.


    tim

    Saturday, February 1, 2020 3:06 PM
  • I am not asking for a license help. I wrote about license just to avoid the question why i am using the core version. Please ignore the license part or i will edit it from my question.
    Saturday, February 1, 2020 5:08 PM
  • Thank you Leon. i will try this.
    Saturday, February 1, 2020 5:09 PM
  • I am not asking for a license help. I wrote about license just to avoid the question why i am using the core version. Please ignore the license part or i will edit it from my question.

    If you run even a single Windows Server instance on the system, even if it's just a replica, then the host must be licensed to run Windows Server anyway. Tim is telling you that you might be able to use the full Windows Server product for the same cost. If you want to use Hyper-V Server, use Hyper-V Server (there is no such thing as "Hyper-V Core"). We don't tend to grill people about their reasons here unless we see a potentially superior alternative and want to make certain that we're not missing some vital piece of information. But, if you're not properly licensing the system, then you're risking thousands of dollars in piracy fines just to avoid an ~$800 license cost. Tim is trying to help you, not interrogate you.

    If you disjoined from the domain, then you can't use Kerberos.


    Eric Siron
    Altaro Hyper-V Blog
    I am an independent contributor, not an Altaro employee. I accept all responsibility for the content of my posts. You accept all responsibility for any actions that you take based on the content of my posts.

    Saturday, February 1, 2020 6:26 PM
  • Hi BN04,

    Thanks for your post!

    1. Firstly, agree with Tim, please check if the replica server is licensed, this is the Prerequisite of the following troubleshooting steps.

    2. If the replica server is licensed, the issue still exists, please try the following things:

    a. Please check if the replica Server join the domain correctly, check the secure channel between the replica server and the DC. We may also try the rejoin the replica server to the domain.

    b. Please check if the replica server's FQDN recorded in the DNS server correctly, if not, we may add the A record manually.

    c. Please check if the firewall port for replication and Kerberos authentication is opened, we may try to turn off the firewall on the Servers for test.

    Thanks for your time! If you have any concerns or questions, please feel free to let me know.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by BN04 Monday, February 3, 2020 5:26 PM
    Monday, February 3, 2020 8:26 AM
  • To all who replied to the post talking about Hyper-V licenses and Hyper-V core. See below the links that explains everything about the licenses.

    https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2019

    https://www.nakivo.com/blog/understanding-hyper-v-vm-licensing-on-windows-server-2016-and-hyper-v-server-2016/

    https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-server-2016

    https://www.altaro.com/hyper-v/how-to-install-hyper-v-r2/free-server-core/

    My requirement for this new install was it to make it as a replica server and not trying to make this as a Hyper-v running on windows server and running VM on it. Instead of discussion with the real problem everyone was talking about licenses. Anyway thanks for all the replies and help.

    Monday, February 3, 2020 5:59 PM
  • While I certainly appreciate you citing my articles in a response to my response, I must point out that the exact one that you linked only covers 2012 R2. None of the articles that you cited include a discussion on replica. I have a much newer one that does a more applicable job than that one

    Bottom line: If your host contains a replica of even one Windows Server VM, then you must treat it as a normal VM running a full, active copy of Windows Server. The host must be licensed for that. Using Hyper-V Server does not absolve you of your licensing responsibilities. If you have not paid for a license on that host, then you are out of licensing compliance and subject to software piracy fines up to $150,000 per incident. And, they pay bounties to people that report violations. That qualifies as a "real problem" in my book, much more than any temporary technical problem.

    If you want your lawyers to vet what I'm saying, this is the only document that matters: https://www.microsoft.com/en-us/licensing/product-licensing/products. The use of replica without a license is specifically covered as a Software Assurance benefit ONLY (page 92 in the English edition).


    Eric Siron
    Altaro Hyper-V Blog
    I am an independent contributor, not an Altaro employee. I accept all responsibility for the content of my posts. You accept all responsibility for any actions that you take based on the content of my posts.


    • Edited by Eric SironMVP Monday, February 3, 2020 6:39 PM
    • Marked as answer by BN04 Monday, February 3, 2020 9:07 PM
    Monday, February 3, 2020 6:37 PM
  • Eric you are the best. Thanks for the support.

    I tried Hyper-v server for replica in my test environment and found its not easy to configure and maintain. So i have to go with Windows Server standard and license all the cores.

    Monday, February 3, 2020 8:51 PM
  • I understand that licensing is not fun. I've supported companies as they underwent a software audit, and that's significantly less fun. Just trying to do my part to keep as many people as possible from unintentionally suffering through one.

    With time and practice, Hyper-V Server is not nearly so bad as it seems at first blush. Once you have some experience, it's really nice when you have to work with a bulk of hosts. But, if you're not there yet, you're not there yet. I almost always recommend that smaller installations stick to Windows Server. It usually fits their comfort level better and they have to pay for the license anyway. I'm pretty sure that's what Tim was trying to say in his response as well.


    Eric Siron
    Altaro Hyper-V Blog
    I am an independent contributor, not an Altaro employee. I accept all responsibility for the content of my posts. You accept all responsibility for any actions that you take based on the content of my posts.

    Monday, February 3, 2020 9:04 PM
  • yes, thank you again.
    Monday, February 3, 2020 9:07 PM
  • thank you for your support.
    Monday, February 3, 2020 9:08 PM
  • Hi Eric,

    Do you have any blog that explains setting up use certificate based authentication (HTTPS) in replication process, if i have to create another question here i can ask that too.

    Monday, February 3, 2020 9:19 PM
  • " if i have to create another question here i can ask that too."

    You have marked this post as having answered your initial question.  Forum etiquette says that you should open a new post when you have a new question.  It helps people in the future who are looking for answers.  Having a descriptive title to a post which defines or hints at the issue also helps people to find answers.


    tim

    Tuesday, February 4, 2020 5:46 PM
  • thank you
    Wednesday, February 5, 2020 3:53 PM