I'm pretty skilled with SBS and am now needing to replace a bunch of SBS machines with Standard/Exchange combos. Local Exchange is a must and I'm trying to find a way to knock these systems out so the new high cost is as low as possible. It's already about $2500 to $3000 more just in licenses and clearly setting up 4 Windows installs is not very easy. I'm building a test bed trying to figure out the best way to do this. Details follow.
I have a number of clients with SBS 2008 systems reaching the end of their supported, warranted life. The question is whether I've made a fatal mistake in my test machine or if it's just configuration mistakes which can be fixed. The goal is to come up with a process to deliver and install a Server Standard 2012r2/Exchange 2013/Hyper-V setup where the entire switchover is done over a weekend with everything working on Tuesday morning. I bought a test server, two copies of Standard 2012 R2 on the plan that the old server will become a BDC and the source of a third guest OS in addition to the two that come with Standard. The three VMs will be on their own partitions on the theory that the disk fragmentation difference is worth the hassle. I don't have clear guidance here but it seems to make sense. I'm open to being told I'm wrong. The next thing is that I am using three guest OSes with the host doing nothing but host. There will be a BDC on the old box currently running SBS so the host could also be the file server but the file server is also an app server and I've been advised not to have the host do anything but host.
So, Host, and thee guest OSes, Domain controller, Exchange 2013 and file/print/app server.
Issue 1: can the same instance of IIS run both Remote Web App and OWA if Essentials is not installed on the Exchange VM. I thought that Essentials should be installed on the DC as it's a pseudo domain enabling remote access, desktop backup and the like. I need to have a single external IP address and a single certificate for both RWA and OWA. Can the IIS on Exchange VM also run RWA on the default web site as it does on SBS if Essentials is on the DC? Or does Essentials need to be on the Exchange server? And if it needs to be on the Exchange server, is it too late and I need to start over?
Second question is that I don't understand disjoint namespace or something else which has resulted in my Exchange server sending as subdomain.domainname.com instead of domainname.com. There are two receive connectors, one for subdomain.domainname.com and the other just as domainname.com but I don't see a way to make the send connector send to the internet as domainname.com.
The DC is setup by defaults I could not figure out how to change as "INTERNAL".domainnname.com with no obvious way to prevent the subdomaining nor a way to change the NetBIOS name as INTERNAL. INTERNAL is the NetBIOS name and users are at internal<username>. I tried to eliminate it for DNS so that Exchange would be at domainnane.com but I fumble-fingered something so that DNS name is "int" not INTERNAL. So the Exchange server is trying to send as int.domainname.com.
I tried to name sense of disjoint namespace but thought that if the domainname after the NetBIOS subdomain was the DNS name, I was OK and it was not disjoint. Is the Exchange problem the "int" or that I have not figured out how to make the Internet send connector send as "domainname.com"? SBS had a "connect to the Internet Wizard" which let you define the Internet domain that Exchange was authoritative for.
I'm combining these questions because the underlying question is whether I can change some settings or need to do the DC and then Exchange over. I understand that little can be changed on the DC at this point.
Thanks for any help. I'm stumped.