asked on

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

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

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.

ROM

ASKER

But a Private one could suffice for the build and then change it when I move onto the actual Host?

Thanks

R

SOLUTION

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

Cliff Galiher

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ROM

ASKER

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.