Otdfbt

What should I be aware of in buying second-hand sinks and toilets?

Idiom for 'person who gets violent when drunk"

Why not make one big CPU core?

Approach sick days in feedback meeting

Nth term of Van Eck Sequence

What things do I only get a limited opportunity to take photos of?

My parents claim they cannot pay for my college education; what are my options?

How can religions without a hell discourage evil-doing?

Bullying by school - Submitted PhD thesis but not allowed to proceed to viva until change to new supervisor

Are athletes' college degrees discounted by employers and graduate school admissions?

Leveraging cash for buying car

Is it possible to install Firefox on Ubuntu with no desktop enviroment?

Can a 40amp breaker be used safely and without issue with a 40amp device on 6AWG wire?

Manager wants to hire me; HR does not. How to proceed?

Can I give my friend the sour dough "throw away" as a starter to their sourdough starter?

Sakkāya-Ditthi and Self-View

Do legislators hold the right of legislative initiative?

100-doors puzzle

Reflecting Telescope Blind Spot?

How to search for Android apps without ads?

Looking for an iPhone app for working out chess problems

Is fission/fusion to iron the most efficient way to convert mass to energy?

How to avoid offending original culture when making conculture inspired from original

How to address players struggling with simple controls?

Hyper-V setup before & after domain creation?

Advantages/disadvantages of moving from a workgroup to domainDNS Configurations for Microsoft VDI on Hyper-V Server 2012How to create new domain w/ Hyper-V 2012 hosting the DC server?How to configre 4-port NIC for standalone Hyper-V server?Connect Hyper-v Manager on domain PC to a workgroup Hyper-V ServerHyper-V 2012R2 in workgroup: can't access via Hyper-V Manager after joining client to domainHyper-v replication assistanceHow do I remotely manage Hyper-V 2016 standalone via Windows 10?Remote Hyper-v VMs not being listedWindows server 2019 fails after hyper-v role install

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

1

I am planning to create a Windows Domain through a Windows Server 2016 or 2019, however the Windows server will be installed as a virtual machine in Hyper-V.
Since Hyper-V requires selecting membership of a Workgroup or a Domain, right after the setup, what steps should I follow as the Domain will exist only after installing the Windows server.
Therefore, should I initially join Hyper-V to a fake workgroup and then, once the domain creation has completed, join the Domain?

domain hyper-v workgroup

share|improve this question

edited May 30 at 16:20

Riccardo

asked May 30 at 16:00

RiccardoRiccardo

16129

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks Todd, I would need just one server to keep management easier, the Windows Server is just for a few users (4) hence I was tempted to avoid VMs and go physical! So we can afford having the unique DC down, should ever happen
  
  – Riccardo
  May 30 at 16:27
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  They need a machine with MS SQL Server. I am aware this is deprecated (DC + SQL server on the same machine) however they don't want to spend more than the cost for one server....
  
  – Riccardo
  May 30 at 16:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Riccardo To be exact, if you buy a standard server version, you can have two VM with the same licence inside one physical's server, you are allowed to do that, but the hyper-v must be used only for the hyper-v (no other windows's roles)
  
  – yagmoth555♦
  May 30 at 17:28
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks @yagmoth555
  
  – Riccardo
  May 30 at 17:44
  

  
  
  
  

add a comment | 

1

I am planning to create a Windows Domain through a Windows Server 2016 or 2019, however the Windows server will be installed as a virtual machine in Hyper-V.
Since Hyper-V requires selecting membership of a Workgroup or a Domain, right after the setup, what steps should I follow as the Domain will exist only after installing the Windows server.
Therefore, should I initially join Hyper-V to a fake workgroup and then, once the domain creation has completed, join the Domain?

domain hyper-v workgroup

share|improve this question

edited May 30 at 16:20

Riccardo

asked May 30 at 16:00

RiccardoRiccardo

16129

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks Todd, I would need just one server to keep management easier, the Windows Server is just for a few users (4) hence I was tempted to avoid VMs and go physical! So we can afford having the unique DC down, should ever happen
  
  – Riccardo
  May 30 at 16:27
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  They need a machine with MS SQL Server. I am aware this is deprecated (DC + SQL server on the same machine) however they don't want to spend more than the cost for one server....
  
  – Riccardo
  May 30 at 16:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Riccardo To be exact, if you buy a standard server version, you can have two VM with the same licence inside one physical's server, you are allowed to do that, but the hyper-v must be used only for the hyper-v (no other windows's roles)
  
  – yagmoth555♦
  May 30 at 17:28
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks @yagmoth555
  
  – Riccardo
  May 30 at 17:44
  

  
  
  
  

add a comment | 

I am planning to create a Windows Domain through a Windows Server 2016 or 2019, however the Windows server will be installed as a virtual machine in Hyper-V.
Since Hyper-V requires selecting membership of a Workgroup or a Domain, right after the setup, what steps should I follow as the Domain will exist only after installing the Windows server.
Therefore, should I initially join Hyper-V to a fake workgroup and then, once the domain creation has completed, join the Domain?

domain hyper-v workgroup

share|improve this question

edited May 30 at 16:20

Riccardo

asked May 30 at 16:00

RiccardoRiccardo

16129

share|improve this question

edited May 30 at 16:20

Riccardo

asked May 30 at 16:00

RiccardoRiccardo

16129

share|improve this question

edited May 30 at 16:20

Riccardo

asked May 30 at 16:00

RiccardoRiccardo

16129

asked May 30 at 16:00

RiccardoRiccardo

16129

asked May 30 at 16:00

RiccardoRiccardo

16129

1 Answer
1

active

oldest

votes

2

Microsoft recommends joining the Hyper-V host to a domain. You certainly can join it to the domain of the guest DC.

Hyper-V itself does not need the DC for any Hyper-V related functions. Hyper-V will happily run and start any and all VM's without having access to the DC, so there is no chicken or egg scenario.

The domain join process is completed before the computer joining the domain reboots. The domain join process does not complete during the reboot. When you reboot the server, the server itself is reconfigured for domain membership. It does not at that point need any connectivity to the domain, so, again, there is no chicken or egg scenario.

When the server reboots, you can simply log on with the local Administrator user account. If you want to cache the domain user account credentials on the Hyper-V host then simply log onto it remotely (RDP) with your domain credentials after the host and guest are up and running. Once the domain credentials are cached you can log onto the server locally with those credentials... whether the DC is running or not.

share|improve this answer

answered May 30 at 16:45

joeqwertyjoeqwerty

97.6k466149

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969521%2fhyper-v-setup-before-after-domain-creation%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

2

Microsoft recommends joining the Hyper-V host to a domain. You certainly can join it to the domain of the guest DC.

Hyper-V itself does not need the DC for any Hyper-V related functions. Hyper-V will happily run and start any and all VM's without having access to the DC, so there is no chicken or egg scenario.

The domain join process is completed before the computer joining the domain reboots. The domain join process does not complete during the reboot. When you reboot the server, the server itself is reconfigured for domain membership. It does not at that point need any connectivity to the domain, so, again, there is no chicken or egg scenario.

When the server reboots, you can simply log on with the local Administrator user account. If you want to cache the domain user account credentials on the Hyper-V host then simply log onto it remotely (RDP) with your domain credentials after the host and guest are up and running. Once the domain credentials are cached you can log onto the server locally with those credentials... whether the DC is running or not.

share|improve this answer

answered May 30 at 16:45

joeqwertyjoeqwerty

97.6k466149

add a comment | 

2

Microsoft recommends joining the Hyper-V host to a domain. You certainly can join it to the domain of the guest DC.

Hyper-V itself does not need the DC for any Hyper-V related functions. Hyper-V will happily run and start any and all VM's without having access to the DC, so there is no chicken or egg scenario.

The domain join process is completed before the computer joining the domain reboots. The domain join process does not complete during the reboot. When you reboot the server, the server itself is reconfigured for domain membership. It does not at that point need any connectivity to the domain, so, again, there is no chicken or egg scenario.

When the server reboots, you can simply log on with the local Administrator user account. If you want to cache the domain user account credentials on the Hyper-V host then simply log onto it remotely (RDP) with your domain credentials after the host and guest are up and running. Once the domain credentials are cached you can log onto the server locally with those credentials... whether the DC is running or not.

share|improve this answer

answered May 30 at 16:45

joeqwertyjoeqwerty

97.6k466149

add a comment | 

Microsoft recommends joining the Hyper-V host to a domain. You certainly can join it to the domain of the guest DC.

Hyper-V itself does not need the DC for any Hyper-V related functions. Hyper-V will happily run and start any and all VM's without having access to the DC, so there is no chicken or egg scenario.

The domain join process is completed before the computer joining the domain reboots. The domain join process does not complete during the reboot. When you reboot the server, the server itself is reconfigured for domain membership. It does not at that point need any connectivity to the domain, so, again, there is no chicken or egg scenario.

When the server reboots, you can simply log on with the local Administrator user account. If you want to cache the domain user account credentials on the Hyper-V host then simply log onto it remotely (RDP) with your domain credentials after the host and guest are up and running. Once the domain credentials are cached you can log onto the server locally with those credentials... whether the DC is running or not.

share|improve this answer

answered May 30 at 16:45

joeqwertyjoeqwerty

97.6k466149

share|improve this answer

answered May 30 at 16:45

joeqwertyjoeqwerty

97.6k466149

answered May 30 at 16:45

joeqwertyjoeqwerty

97.6k466149

answered May 30 at 16:45

joeqwertyjoeqwerty

97.6k466149