Before anybody says it, I had the money for 1 Server, so yes, I know it's not advised to install Exchange on the Domain Controller but it's what I have to do.  Thanks to Microsoft doing away with the Small Business Server, this is my only option if we don't want to spend 75 dollars a month for a service that was free on SBS 2003. 

        So, what I have done is setup Server 2012 Essentials, I did an in-place upgrade to Server 2012, getting ready to install Exchange 2013.  What do I need to be aware of when it comes to Exchange 2013 co-existing with Anywhere Access.  Can they co-exist?  I am going to build my SSL certificate off of the certificate wizard during the setup of Anywhere access (bought it from Godaddy, a multi-name certificate).  I plan on adding autodiscover and mail to the certificate. 

       Any help would be great.  Is there a good guide on Exchange 2013 setup?  I have found various things on the internet including TechNet but seem to get varying advice on how to install it 

Before anybody says it, I had the money for 1 Server, so yes, I know it's not advised to install Exchange on the Domain Controller but it's what I have to do.  Thanks to Microsoft doing away with the Small Business Server, this is my only option if we don't want to spend 75 dollars a month for a service that was free on SBS 2003. 

        So, what I have done is setup Server 2012 Essentials, I did an in-place upgrade to Server 2012, getting ready to install Exchange 2013.  What do I need to be aware of when it comes to Exchange 2013 co-existing with Anywhere Access.  Can they co-exist?  I am going to build my SSL certificate off of the certificate wizard during the setup of Anywhere access (bought it from Godaddy, a multi-name certificate).  I plan on adding autodiscover and mail to the certificate. 

       Any help would be great.  Is there a good guide on Exchange 2013 setup?  I have found various things on the internet including TechNet but seem to get varying advice on how to install it.

Hi

Exchange 2013 is not supported co-existing with Exchange Server 2003 and earlier versions.

Upgrade from Exchange 2010 to Exchange 2013:

http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx

The following a blog from a MVP for your reference.

How to Install Exchange Server 2013:

http://exchangeserverpro.com/how-to-install-exchange-server-2013/

More information:

Checklist: Perform a New Installation of Exchange 2013:

http://technet.microsoft.com/en-us/library/ff805042(v=exchg.150).aspx

Install Exchange 2013 Using the Setup Wizard:
http://technet.microsoft.com/en-us/library/bb124778(v=exchg.150).aspx

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

Thank you Wendy for answering, SBS 2003 is not on the same network, nor will it ever be.  I am not doing a migration.  What I need to know is if Exchange can co-exist with Anywhere Access.  The articles you sent me I have seen but none speak specifically  to what I am doing.

Your only option is to install both roles (CAS and MBX) together, so in the setup there is not much you can do. Regarding Anywhere access, just make sure that you have separate IP for Exchange services (as they are also using HTTPS) and proper certificate. In the certificate for Exchange, you should have your local Exchange name, public Exchange name and autodiscover name.

Thank you for the response, I did a run through of the install to see what would happen, in IIS it gave exchange ports 81 and 444.  I assumed because anywhere access is using 80 and 443.  Would that setup  work?  Or could I reverse it and have anywhere access use 81 and 444?  I only have one static, I could order another one but that will take time and was hoping to finish the job this coming weekend.  Also, I am going to assume that Comcast will charge more a month for that.

Exchange 2003 and 2013 can't coexist in the same AD forest. Exchange 2003 would need to be migrated to 2010 before it could be migrated to 2013. You will have to install 2010 cas, ht and Mbx. You can install on one server. Even if this is going to be a separate forest you would need to install 2010 and migrate to 2013 unless you go for quest or other tool. Feel free to check my blogs at MSExchangeGuru.com for migration and 2013 install. I am replying from phone so unable to add any link.

I appreciate that but that isn't the problem, I am not going to have the exchange 2003 sbs server on the same network and is going away as soon as the new server is online.  My problem is having a Server 2012 that was a Server 2012 Essentials run exchange and anywhere access (RWW + SSTP) all co-exist and be happy on the same server.  I am not doing any migration at all.  I am backing up exchange mailboxes to PST and will import into the new profiles once the new server is online. Thank you everybody for the help

This will not work. You will have to remove sbs server before installing 2013.

I don't think you understand what I am asking.  Let's forget I said anything about the SBS 2003. That is not the problem. 

    I need to know if Anywhere Access and Exchange 2013 can co-exist on the same server.  I did an in-place upgrade from Server 2012 Essentials to Server 2012 Standard.  I am going to install Exchange 2013.  I need Anywhere Access, RWW, and Exchange 2013 to work together.  Is that possible?

Thanks for the help