Add existing servers to HyperV

In an attempt to save space, two servers need to be run on one machine.
The best way seems to use HyperV.
I have two possibillities as far as I see:
1. Install HyperV 2012 R2 core on the machine, and move the two physical servers as VHDs onto it.
2. Install Server 2012 R2 with HyperV role on the machine, and add the VHDs.
The second requires an additional license, as far as I can find out, so i choose the first possibility.
The installation of the core hyperv server is simple.
The conversion of physical to VHD as well. (By the way: must something be done to add drivers to be able to run virtually?)
Moving those images to the hyperv server is done.
But then...
I need a short guide for what steps have to be done to connect these vhds to memory, cpu and network. and may be
other required things. Using powershell, because nothing else is available.

It looks as if there must be some preparation for the network before any machine can be created,
with attributes of memory, and attachment of the provided vhd.
ebrinkAsked:
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 MVE^2)VMware and Virtualization ConsultantCommented:
Microsoft Server 2012 Standard comes with 2 virtual licenses for servers.

 Microsoft now has some new free software called.. Microsoft Virtual Machine Converter 3.1, which you can use to convert your physicals to virtual e.g. P2V

see my EE Articles

HOW TO:  P2V, V2V for FREE to Hyper-V -  Microsoft Virtual Machine Converter 3.1

HOW TO: Convert a physical server or virtual server (P2V/V2V) to Microsoft Hyper-V using Microsoft Virtual Machine Converter 3.1
0
Cliff GaliherCommented:
"1. Install HyperV 2012 R2 core on the machine, and move the two physical servers as VHDs onto it.
 2. Install Server 2012 R2 with HyperV role on the machine, and add the VHDs.
 The second requires an additional license, as far as I can find out, so i choose the first possibility."

The two scenarios above have the *exact* same licensing requirements.  So your best path forward is to use #1 and install with a GUI. Much easier to manage unless you are already an expert.  As far as converting physical to VM, Microsoft has a tool to do so, but like all P2V, it depends on workload. Some servers P2V better than others, and particularly hacked-together boxes that have seen many programs and roles installed and uninstalled or on custom hardware don't P2V well. In those situations it is often better to install the OS clean and just migrate the data and workloads separately.
0

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
ebrinkAuthor Commented:
As response to Cliff Galiher:
If scenario 1 and 2 have same license requirements (So 2 licences for the VHDs and NONE for the Hyperv)
I prefer to install server 2012 R2 at the bottom of the machine (without any license), and add the VHDs
(btw one is server 2012 R2 and the other server 2008 R2, both using the same open license).
So why do you choose for option 1?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Cliff GaliherCommented:
First, some terminology clarification:

VHD does not mean VM, and VM does not mean VHD.  You can have VHDs on a physical OS (iSCSI uses VHDs, win7 supports VHDs in a physical OS, and a VM can have many VHDs for managing data.)  Don't use them interchangeably.  VHDs don't require licenses, VMs do.

"I prefer to install server 2012 R2 at the bottom of the machine (without any license)"  I have no idea what "bottom of the machine" means.  Can you clarify?

You need a license to install 2012 R2, period.  But 2012 R2 comes with special virtualization rights.  So if you install 2012 (or 2012 R2, they have the same rights) *with* a GUI and enable Hyper-V, you also have the rights to run two Windows VMs on Hyper-V without needing another license.  So your physical install *does* need a license. But two of your VMs will not.  This is commonly referred to as 1+2.  1 Physical + 2 Virtual, all covered under the same license.  So when you say "without any license"   that is technically inaccurate.

Now, your second scenario has two VMs.  Those would still need to be licensed.  If you installed the "free" Hyper-V core product, you still have to license the VMs.  Once license *still* covers 2 VMs. You just aren't taking advantage of the "1+" in the "1+2" scenario. So I stand by my previous statement that the licensing requirements for both of your scenarios are the same.

Now, of course, there are still other things to consider.  You can't run workloads on the physical OS in 1+2.  Only Hyper-V.  And you have to meet the processor requirements (4 processors requires 2 licenses), but that'd be true in the free version as well. Free Hyper-V can't run other workloads, and your VMs are running on a server with 4 processors, so it'd still require two licenses, and so forth.  So even if you change the actual license count, HOW it is licensed is the same for both scenarios.

Which means I stand by my previous statement.  I recommend option #1 because it is easier to manage.  You have access to a GUI at any time to perform tasks that are much more difficult via command-line or powershell. For example, want to make some changes to the NIC settings via command-line.  Many settings aren't even exposed in powershell. You get to fire up netsh and manually walk through dozens of commands.  Or you can run the GUI and right-click and adjust.  

Free Hyper-V is a good idea for *very* large datacenters that remotely manage all of their servers anyways (think SCVMM or bigger.)  People aren't managing Hyper-V purely through powershell there either. They still have a GUI. It just isn't running on the box.  And most have experts in Hyper-V or SCVMM on staff full time to manage such environments.  For the average IT Pro, there is still too much that can't be done or is difficult to do via PowerShell to justify hamstringing yourself with the free Hyper-V product. And, in fact, even finding it in 2012 R2 is more difficult. They've buried it in the eval center instead of making it front and center. That should be a good sign of where Microsoft sees the product fitting in the current ecosystem. It just isn't an infrastructure I'd consider supportable for smaller shops.
0
ebrinkAuthor Commented:
Ok.
Your explanation changes the implementation.
Having a gui will simplify maintenance.
The networkstructure, which made me posing the question,  is still not clear.
However, I pause this topic until I have seen, what support comes from the gui to implement that.
The result must be, that every VM and the HyperV machine are remote reachable on their own ipadress,
as if it were separate physical machines, so 3 adresses. The physical machine has only two networkports.
May be it is best, to use only one. If it is defect at some point, the other one can replace it.
0
Cliff GaliherCommented:
Hyper-V runs a virtual switch. So You can have many VMs with only a few NICs. Entire chapters have been written on Hyper-V networking, so understanding how it works does take some research. It isn't going to be a simple answer here.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Use at least two nics, with teaming for resilience. Use teaming in the OS.
0
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.