• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1529
  • Last Modified:

Hyper-V Replication without domain


I'm trying to get replication VM-replication working between two Hyper-V hosts that are not in a domain (without success until now).

What is the FQDN nam of a  host that ist not in a domain?
The workgroup name ist WORKGROUP and the primary DNS-Suffix is empty (ipconfig /all).

I created certificates with just the hostname in it (SERVER1/SERVER2) and get error

"the certificate with the fingerprint .... could not be verified by SERVER1
The CN-name of the certificate does not correspond with the correct value (0x800b010f)"

I tried it also with SERVER1. and SERVER2. as FQDN but that does not work also.

which FQDN do I have to  use for the certificates?

  • 2
  • 2
1 Solution
Cliff GaliherCommented:
The FQDN can be whatever you want within reason. You just need to have a DNS record with the FQDN pointing to the appropriate IP address and you need to configure certificate-based authentication for Hyper-V replica and use a certificate where the common name or subject alternate name has that same FQDN. Neither the name of the server nor workgroup matters.
lenn0xAuthor Commented:
so the FQDN are just SERVER1 / SERVER2 ?

I create certificates for SERVER1 and SERVER2 ?
Cliff GaliherCommented:
Using a single-label name is not a good idea.

You can, for example, have a server named SERVER1 in a workgroup called WORKGROUP.

You can create an A record called Hyper-V in a DNS zone domain.com on your domain server and point it to the IP address of SERVER1. Your FQDN is then hyper-v.domain.com and you'd want that in the certificate as well. Notice how neither the certificate nor the DNS record reference SERVER1 or WORKGROUP. Those are strictly internal identifiers.
lenn0xAuthor Commented:
okay, thank you!
I will do as you proposed.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now