Solved

HypverV Server Win2012

Posted on 2014-02-19
4
353 Views
Last Modified: 2014-02-22
So I have a Server PowerEdge 710 with 8 H.D
I install Win2012 R2 as O/S and installed the HyperV role.
It has 4 NIC's
I also installed the A/D Role and made it into a D/C

Here is what I want to do

.NIC #1 I want it to only be for the Server itself.
.NIC #2 I want it to only be for the HypverV D/C
.NIC #3 I want it to be for the VM machines as well as NIC#4

I'm stuck as to how to assign the NIC to the D/C

Can anyone please give me some insight as to how to do this?

Thanks
0
Comment
Question by:noad
  • 2
  • 2
4 Comments
 
LVL 38

Expert Comment

by:Philip Elder
ID: 39871686
If you are using the 1+2 licensing for the host (meaning host OS is Hyper-V only and that license gives you 2 guest VMs) then you cannot install any additional roles on the host.

DC and Hyper-V do not go together. This is not a recommended practice.

In standalone situations our preference is to leave the host in a workgroup and manage it via RSAT on a domain joined Windows 8 system.

To answer your question directly:
Use native teaming to do the following:
 Team Port 0 and 1 for Management
 Team Port 2 and 3 for vSwitch exclusively

In Hyper-V bind to the second team and leave the host OS unchecked.

Then go on to bind the new vSwitch to your VM's vNICs.

Philip
0
 
LVL 1

Author Comment

by:noad
ID: 39871812
Philip
this is my first time doing this...
Not following you.
can. U break not down?
Also this is not for production, just doing so testing and practicing.
0
 
LVL 38

Accepted Solution

by:
Philip Elder earned 500 total points
ID: 39872091
Okay, your first step is to install the OS fresh on the host.

Partition the host as follows:
 90GB = C:
 Balance = L:

Install your OS to the first partition. Download your ISOs to the second partition for your VM OS installs.

Leave the host in workgroup mode.

Set up teaming on the Host as mentioned above: Two Teams of two ports each. Leave the first team for management and network access and the second team for your virtual Switch (vSwitch). Make the vSwitch exclusive to Hyper-V only.

Set up your first VM using the vSwitch and some storage and use a Server 2012 R2 ISO.

Note the difference between Generation 1 & 2 VMs. Gen2 VMs are a lot more versatile.

Once your first VM is in, set it up, name it, give it an IP address (same subnet as host), and add the ADDS/DNS/DHCP roles. Configure those roles.

Go on to set up and install an OS on a second, third, and subsequent VM.

OPTION: Set up a vSwitch on one dedicated port (no host OS teaming) so you end up with two vSwitches. With Gen2 VMs you can then team those two vSwitches from within the guest OS (after binding both vNICs that is).

Does that help to clarify?

BTW, we do the split partition so we can flatten the host leaving VMs, settings, and ISOs behind. Much simpler that way. :)

Philip
0
 
LVL 1

Author Comment

by:noad
ID: 39872105
I see...
I'll try it.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

This article will review the basic installation and configuration for Windows Software Update Services (WSUS) in a Windows 2012 R2 environment.  WSUS is a Microsoft tool that allows administrators to manage and control updates to be approved and ins…
I don't know if many of you have made the great mistake of using the Cisco Thin Client model with the management software VXC. If you have then you are probably more then familiar with the incredibly clunky interface, the numerous work arounds, and …
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

770 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