Link to home
Start Free TrialLog in
Avatar of redworks

asked on

Exchange 2013 on Windows 2012 with RDS


I know officially the installation should be on 2 seperate servers, but for unimportant (at least for this discussion) reasons we want them combined on 1 server.

I have installed Windows 2012 with terminal services, and now Exchange 2013 fails: operating system not supported.

There are several other apps that fail to install on Win2012, such as Dynamics CRM 2011. However, after a few hacks, it did manage to install.
Perhaps there is a hack here too? Hope to hear from you soon.
Avatar of Stelian Stan
Stelian Stan
Flag of Canada image

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


redworks said:
I know officially the installation should be on 2 seperate servers, but for unimportant (at least for this discussion) reasons we want them combined on 1 server.
WHY would you do this when you have TWO licenses for 2012?  Install Server 2012 to the hardware, load Hyper-V role.  Install TWO VMs with 2012, make one your RDS server and one your Exchange server.

Keep in mind, you're asking how to do something that few if any professional person who knows the products would even think of doing.  Doing it right is easy and costs you nothing.
Remove the Remote Desktop Feature to get the Exchange 2013 installed on Windows Server 2012. If you want to combine both the TS and Exchange 2013 on Windows 2012, then deploy TS and Exchange 2013 on different servers.
I am interested in the Hyper-V solution.
I have already installed Win2012, with RDS and many other things.
When I try to install the Hyper-V role, it says that a some virtualizer is already installed?...

please paste the exact error message to understand the background.
Hyper-V can not be installed: A hypervisor is already running.
Understand - In order to use the two virtual licenses, the host cannot run ANYTHING - EXCEPT Hyper-V.  For this reason, it's best to start clean - reload the server and ONLY install the Hyper-V role.  Then create TWO VMs and load the roles you want in them.

You MIGHT be able to use Disk2VHD (free util from Microsoft/SysInternals) to essentially convert the existing physical install to a VM - But if you try this, uninstall the Hyper-V role first, and keep in mind, this too is unsupported but FAR more commonly done than what you were initially trying to do.
I did what is listed on those pages, even the CPU fixes.
Still I now get "the processor does not have required virtualization capabilities".

I added to the VMX:
mce.enable = "TRUE"
hypervisor.cpuid.v0 = "FALSE"
vhv.allow = "TRUE"

What to do?
What Brand / Model Server and CPU are you using?
Intel Xeon E5530, gave it 2x2 cores
Also tried on Xeon X5570. Intel VT-d enabled in BIOS.
I have found that my CPU does not support EPT. So what does this mean, not possible?