In my environment, I have a number of servers for an electronic medical records package, so I will leave those member servers out of the discussion. I am left with a VMWare esxi server running three virtual machines at the moment. I have no additional licenses of Windows Server to work with. VM1 is a Windows Server 2012R2 domain controller. VM2 is a Windows Server 2008R2 member server running Exchange 2010. This box will be removed after it is migrated to Exchange 2013. I only really installed it because I had to do a swing migration from Exchange 2003 to 2013. VM3 is a Windows Server 2012R2 member server that has nothing on it right now but will be getting Exchange 2013 in the near future and will definitely be providing OWA to external and internal clients.
I want to install Sharepoint 2013 Foundation on VM3 and use the option of installing as a standalone development environment because it is very easy to configure that way and Sharepoint for me is just a simple document repository for PDF files containing company policies, handbooks and other things. I did this on VM1 when it was a member server but it stopped working when I promoted it to a domain controller. I was unaware at the time that this type of install of Foundation would not work on a dc.
My question is, is it ok to run Sharepoint 2013 Foundation on the same server as Exchange 2013? I have plenty of power to do so as the VMware host server is brand new and the specs are very nice. I didn't know if there would be any downside at all. Incoming https traffic will be directed to this virtual machine for owa access going to https://mail.mycompany.com/owa
. I only plan on allowing access to Sharepoint content from the inside network.
Any pitfalls? I really don't want to spin up any more VMs because I am out of Windows server licenses and I have limited options. I can't touch any other member servers in my environment because the software vendors running on them will not allow it and I don't blame them.