Build DC VM without network or Internal network and then redeploy and place onto a teamed fabric

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
LVL 7
RomoloIT Pro, Projects, Mentor, TrainerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
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.
RomoloIT Pro, Projects, Mentor, TrainerAuthor Commented:
But a Private one could suffice for the build and then change it when I move onto the actual Host?

Thanks

R
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
Yes, as long as you have some networking communication between ALL servers, however you implement it does not matter.
Cliff GaliherCommented:
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RomoloIT Pro, Projects, Mentor, TrainerAuthor Commented:
Thanks guys.

Wanted to ensure as I virtualising an entire estate this weekend, so wanted to ensure no issues with servers and roles such as DC etc..

Thanks for the confirmation and reassurance.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.