I wonder if anyone can help?
I want setup an ESXi 5 server and run SBS2011 on it. I'll be buying VMware vSphere Essentials Kit for 3 hosts to do this (the cheap one). In conjunction to this I'll be using Veeam to replicate to another ESXi 5 server. I will also be getting it to perform a backup.
We're only a small company so I can't afford VMware vSphere Essentials Kit plus (£5000) on our budget and this Veeam setup seems to give me the same level of DR for £1500.
As we are on quite a tight budget I'm wondering if it is possible and what the legality is for the following:
If I buy an OEM SBS 2011 license and I need to DR to a different ESXi 5 host will it work i.e. normally in the physical as OEM is licensed for the life of the machine and validates against the CPU ID. If the machine changes the the SBS 2011 software detects this and requires the software to be reauthorised. I know that if you move a SBS 2003 OEM it will work but not 2011?
Could anyone point me in the direction of concrete proof that this can be done? For example some thing written by VMware? Does anyone know if this effects CAL's also? and has anyone come across what Microsoft's opinion is?
Many Thanks,
T.
the beauty in using virutalization technology is that it removes the underlying hardware from the actual virtual server itself.
So if you change hosts, the sbs doesnt even notice.
becasue the virutal machine hardware hasnt chagned, the sbs, which is the virutal machine, thinks it's the same machine, even if its recovered via replication in the dr site.
This is what I though and until recently I would not have questioned it, however I have been asked to have my virtualization proposal risk assessed by an external consultancy and now they have flagged this issue as a possible problem that need clarifying as this will have implications on what licensing model is required? I have rang VMware but I can't get passed call center level 1 unless I show an interest in Essential Plus and level one don't know. I though something might be written somewhere?
you could also try a prooff of concept to alleviate concerns?
Unfortunatly evaluation software tends to be the full version of a software not OEM therefore without buying a OEM copy I can test it?
Ok I believe I've found the legal stand point:
this is a short youtube vid explaining the licensing terms when licensing microsoft products on virtual machines.
In short you can virtulize OEM but you can't (when properly licensed) move it to other machines.
i.e. It will work but you shouldn't do it, supposedly
