Link to home
Start Free TrialLog in
Avatar of Member_2_4384294
Member_2_4384294Flag for United Kingdom of Great Britain and Northern Ireland

asked on

VM topology - How many VMs do I need?

To what level is it best to separate servers between different VMs? Our physical environment was a single Windows server, but now that we have migrataed it to VMWare we going to begin using Sharepoint server. Should everything be split between differnet VMs (ie. Domain Controller, SQL, Sharepoint, Exchange) or should we still keep some services on the same (virtual) server?

Thanks.
SOLUTION
Avatar of WotanAU
WotanAU
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Member_2_4384294

ASKER

We chose Server Datacentre to avoid licensing limitations in the future. I'm thinking:

Domain Controller (DHCP, DNS, AD etc)
SQL
Exchange
Project Server
Sharepoint Server

Any reaon not to go with this? Are there perfomance issues if roles are on different hosts (albeit virtual)?
Avatar of Tony J
I always try to follow the one server one role (or at least associated roles) approach.

When you virtualise, if you buy a Windows Server Enterprise license and it's a supported hypervisor (which VMware is) then you can actually use that single license for four virtual instances. Just Google Microsoft virtualisation licensing.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
By the way - be careful with licensing SQL in a virtual environment. You have to license it for every potential CPU (or core - can't remember off-hand) that it could possibly be hosted on and that rapidly makes it expensive in a multi-host virtual environment.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I most certainly agree with all what has been said by the above experts.

I would like to add the reasons behind not adding roles other than DNS and DHCP to a domain controller:

Domain controllers, by default, have security configurations higher than other member servers. In many cases this wouldn't be ideal for other roles like terminal services; and unless these security configurations are relaxed would cause an endless amount of errors that would take you 'ages' to troubleshoot. Moreover, it is strongly recommended not to tamper with security configurations on your DCs as they host all your critical domain components. Needless to say, hosting other roles where clients connect to with interactive sessions like terminal set vices or Sharepoint would raise security concerns.

Therefore, the factors to determine the number of VMs and how to split your roles should be availability of resources, licensing, performance, resilience and fault tolerance, security. Taking all of these into consideration should eventually help you in determining the number of VMs in your environment.
And then of course there is supportability - in the event you ever have to raise a call with Microsoft, the moment you tell them your Exchange server is on a DC they won't help until the roles are split and at that point it could impossible to do this.
Of course!! :)