Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
COURSE of the MONTH
9 days, 3 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Build DC VM without network or Internal network and then redeploy and place onto a teamed fabric
Posted on 2016-08-25
Hey All,
Trying to get ahead of the game build a virtual environment as I am upgrading from physical to a HyperV Host for all roles.
Servers not here yet, so was going to start building the DC VMs on another server and either use NOT CONNECTED or create an internal Virtual Switch and use this while I build the DC, DNS, DHCP .. VM.
Then when servers are here, move onto the server and after using Converged Fabric for teaming and setting up an External VSwitch on this.
Sound all good, or will I come into problems when building the DC or after I move it.
Trying to get things ahead as I only have the weekend to build.. Which option would you choose?
Many thanks in advance
R
Trying to get ahead of the game build a virtual environment as I am upgrading from physical to a HyperV Host for all roles.
Servers not here yet, so was going to start building the DC VMs on another server and either use NOT CONNECTED or create an internal Virtual Switch and use this while I build the DC, DNS, DHCP .. VM.
Then when servers are here, move onto the server and after using Converged Fabric for teaming and setting up an External VSwitch on this.
Sound all good, or will I come into problems when building the DC or after I move it.
Trying to get things ahead as I only have the weekend to build.. Which option would you choose?
Many thanks in advance
R
[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
5 Comments
Active today
As long as you have network connectivity between servers and services, in virtual world or physical, there will be no issues.
the VMs will need to have network communication between them, so virtual switch required.
the VMs will need to have network communication between them, so virtual switch required.
Active 7 days ago
But a Private one could suffice for the build and then change it when I move onto the actual Host?
Thanks
R
Thanks
R
Active today
Yes, as long as you have some networking communication between ALL servers, however you implement it does not matter.
Active today
To be clear, when you create an internal switch and create the VM, the VM will get its own virtual NIC. The details of which will differ depending on whether the VM is gen1, gen2, or if a legacy adapter is added to the VM properties...all are independent of the switch.
Then if/when you change over to an external switch and bind that switch to a team, the *VM's* virtual NIC is remaining unchanged. This is equivalent to taking a physical server and plugging it into a new unmanaged switch. The VM won't know or really care. It has the same NIC so no binding or IPv4/6 properties change.
This is true for a VM that is a DC as well as any other VMs you create. They can be "plugged into" the same virtual switch or different virtual switches. Hyper-V definitely makes a separation between the virtual NICs that VMs use and virtual switches that run within the hypervisor itself. This increases reliability and portability, and addresses exactly concerns such as yours.
Then if/when you change over to an external switch and bind that switch to a team, the *VM's* virtual NIC is remaining unchanged. This is equivalent to taking a physical server and plugging it into a new unmanaged switch. The VM won't know or really care. It has the same NIC so no binding or IPv4/6 properties change.
This is true for a VM that is a DC as well as any other VMs you create. They can be "plugged into" the same virtual switch or different virtual switches. Hyper-V definitely makes a separation between the virtual NICs that VMs use and virtual switches that run within the hypervisor itself. This increases reliability and portability, and addresses exactly concerns such as yours.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
When we have a dead host and we lose all connections to the ESXi, and we need to find a way to move all VMs from that dead ESXi host.
In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
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…
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…
Suggested Courses
Course of the Month9 days, 3 hours left to enroll
764 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.