[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Hyper-V Replication without domain

Posted on 2014-02-14
4
Medium Priority
?
1,429 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 59

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 59

Accepted Solution

by:
Cliff Galiher earned 2000 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

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.

Question has a verified solution.

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

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
Previously, on our Nano Server Deployment series, we've created a new nano server image and deployed it on a physical server in part 2. Now we will go through configuration.
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

649 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