For sale: Want to own a business forum ? Submit your sealed bid to acquire businessforum.uk

By using Apprenticeforums services you agree to our Cookies Use and Data Transfer outside the EU.
We and our partners operate globally and use cookies, including for analytics, personalisation, ads and Newsletters.

  • Join our UK Small business Forum

    Helping business owners with every day advice, tips and discussions with likeminded business owners. Become apart of a community surrounded by level headed business folk from around the UK


    Join us!

2 Servers from 1 License in Server 2008

  • Thread starter Lanarkshire IT Services
  • Start date
L

Lanarkshire IT Services

New Member
Hi All

In my messing around with Server 2008 R2 64 bit STD and the Hyper V server role I have discovered that you are entitled to the same OS in VM form.

So in essence you can get 2 2008 R2 STD 64 bit servers - 1 host and 1 VM.

With today's environmental issues, the current trend towards virtualisation and the lost cost of server hardware I feel this is a real bonus with regards to hardware costs, server maintenance, testing etc.

Now server roles such as File / Print / DHCP / DNS / Windows Deployment Services can split and balanced between the host and the VM.

And the VMs are portable, you can export your 2008 VM to another server running Hyper V. Pretty useful if your VM is a Windows Deployment Server and you need to go to different company sites to deploy Windows operating systems.

Seems pretty cool stuff with a lot of possibilities.

Will keep you posted.

Regards
 
L

LumleyMedia

New Member
You shouldnt really run any services on the host machine except for the hyperv role.

The machine should really be concentrating on running the services for that role rather than being split.

A typical set up would be the host running a couple of VMs for example.

Host - HyperV only
VM1 - Domain Controller
VM2 - Exchange Server
VM3 - VOIP Server
 
L

Lanarkshire IT Services

New Member
You shouldnt really run any services on the host machine except for the hyperv role.

The machine should really be concentrating on running the services for that role rather than being split.

A typical set up would be the host running a couple of VMs for example.

Host - HyperV only
VM1 - Domain Controller
VM2 - Exchange Server
VM3 - VOIP Server

Hi Bud

I understand what you are saying but having your DC on a VM means you have to start the host then the DC VM.

Personally I wouldnt recommend that because if for any reason you cannot start the host with Hyper V then you have NO domain.


"The machine should really be concentrating on running the services for that role rather than being split."

I dont agree with that but its just a matter of whatever is best for your business I guess.

Bearing in mind that my original point was on purchase of ONE copy of Server 2008.

My setup:

Host: Server 2008 DC with Hyper V
Guest: Server 2008 Member Server configured with Windows Deployment Services (WDS) which I can turn off when I dont need!

Regards
 
L

LumleyMedia

New Member
I see your point but you are missing the whole point of having virtual servers.
Usually (i speak on behalf of larger organisations) the host machine is just a work group machine and the VMs are on the domain.

Only reason i can answer this is because I am still working as an IT Consultant while my business is in it first stages and i look after some large clients including computer games companies, Cancer research and architects.
 
L

Lanarkshire IT Services

New Member
I see your point but you are missing the whole point of having virtual servers.
Usually (i speak on behalf of larger organisations) the host machine is just a work group machine and the VMs are on the domain.

Only reason i can answer this is because I am still working as an IT Consultant while my business is in it first stages and i look after some large clients including computer games companies, Cancer research and architects.

M8 I was involved in the design and maintainence of a VM datacenter for one of the worlds biggest banks and having a domain on a "work group machine" is pretty silly!

Regards
 
L

LumleyMedia

New Member
Not neccassarily if you look at the benefits. But as you said it depends on the client.
Having the DC on a VM just made a disaster recovery job a lot quicker on a job i done last week as it was just case of moving the vhds to another virtual server.
 
L

Lanarkshire IT Services

New Member
Not neccassarily if you look at the benefits. But as you said it depends on the client.
Having the DC on a VM just made a disaster recovery job a lot quicker on a job i done last week as it was just case of moving the vhds to another virtual server.

Hi M8

Not wanting to get into an arguement here but that was not the original point I was making.

Yes you can move a VM around and import / export the VM to and from machines pretty simply as long as the Hyper V role / service is present.

One copy of Server 2008 = 2 licenses (1 host 1 VM)

1 Host machine as PDC with Hyper V
2 Any services / roles which drain or degrade the perfomance or that are otherwise bad practice on a DC such as Exchange can be on the VM

Regards
 
L

LumleyMedia

New Member
Ok i miss the whole point of it being about value for money with the 2 licenses.
Dont worry though this isnt an argument just a healthy debate.
The whole thing of VMs is prior planning obviously and you would know exactly what you were putting on the hosts. Would love to carry on this conversation another day though as im on my way out for meetings the now, do you use skype/msn?
 
L

Lanarkshire IT Services

New Member
No Worries

I love a good debate!

Have a great day!

Regards
 
L

Lanarkshire IT Services

New Member
Heres a wee quote from Virtualization Design:

Virtualizing a Domain Controller reintroduces possibilities to mess up the Domain Controller in ways most of the Directory Services Most Valuable Professionals (MVPs) and other Active Directory enthusiasts have been fixing since the dawn of Active Directory.

Regards
 
Top