Solved

Hyper-V Replication without domain

Posted on 2014-02-14
4
1,300 Views
Last Modified: 2014-11-12
Hi,

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?


Lennox
0
Comment
Question by:lenn0x
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 39858800
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.
0
 
LVL 1

Author Comment

by:lenn0x
ID: 39858941
so the FQDN are just SERVER1 / SERVER2 ?

I create certificates for SERVER1 and SERVER2 ?
0
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 39859130
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.
0
 
LVL 1

Author Closing Comment

by:lenn0x
ID: 39865185
okay, thank you!
I will do as you proposed.
0

Featured Post

MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
OfficeMate Freezes on login or does not load after login credentials are input.
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question