Outlook 2010 RPC Over HTTP
-
Tuesday, January 08, 2013 4:13 PMI have my old domain that holds {Myserver}.{mydomain}.org. This is an SBS 2003 server that holds my exchange. I now have {Myserver}.{MynewDomain}.local which is running an sbs 2011 essentials server. The essentials did not include exchange so i have to use the old server for exchange and the new server for everything else. I need to know how to connect clients outlook to the old server even though they are joined to the new domain. When i tried on my client everythingjoined, but i could not send or recieve email. I fixed all my dns records to allow the emails and now my outlook has no connectivity to exchange. None of the other client outlooks will connect. They wont even complete the check name stage of the manual setup. Please help as this has made me very close to throwing all the computers away and going back to a pen and pad of paper.
All Replies
-
Tuesday, January 08, 2013 4:18 PM
So let me get this straight, you now have two domains, and you want to keep your old SBS2003 box running on the old domain but have the new SBS Essentials box running with a new domain??????? Any reason why you bought Essentials instead of Standard, knowing that you wanted to continue using Exchange?
I suspect what you will need to do is change the accounts in Outlook to request credentials (e.g. Basic authentication) and all your users will have to enter credentials on the OLD domain when they want to connect to Outlook.
Remember that OWA will probably also be affected, you can only have one DHCP server, and probably countless other problems going forward.....
If I were in the mess that you are now in, I would suggest the only long term headache-free solutions are to either buy SBS 2011 Standard and migrate, ditching Essentials along the way, or move your Exchange database to the cloud on Office 365 (which Essentials will happily talk to).
I assume you "upgraded" due to the SBS2003 hardware (and software) being ancient, but unless you deal with Exchange you're not really solving that problem.
Jim
- Edited by Jim WillsherMicrosoft Community Contributor Tuesday, January 08, 2013 4:22 PM
-
Tuesday, January 08, 2013 7:15 PM
Hi,
First of all I totally agree with Jim, the situation you have put your self in is a real mess. ;lBest option now you own SBS 2011 Essentials move email to the cloud. Essentials has a wizard to connect to office 365 so this would be the best option.
If you want to rpc over https you need to configure you exchange server for using this, maybe these guides might help: http://support.microsoft.com/kb/833401 and http://www.petri.co.il/how-can-i-configure-rpc-over-https-on-exchange-2003-single-server-scenario.htm
But again the best option would be to get rid of the SBS 2003 server and move your email to another configuration.
Regards Ronny
-------------
Visit my Blog or follow me on Twitter -
Wednesday, January 09, 2013 4:20 PMThe setup is as you discussed. I bought the essentials server, knowing i wanted exchange, because i thought exchange was built in like it was on the old sbs. The site i bought it from sells products at a drastic disount to nonprofits like mine. On thier site, they discuss essentials, and its exchange capabilities. I think they used the standard info to explain essentials. I have contacted them to correct this. The issue now is i am stuck with essentials, as even at a discounted rate, it ate most of my it budget. We actually moved to essentials because we were replacing the server that 2003 is on. I am in a huge mess now, as you have all stated, and need a solution. My nonprofit cannot afford to go with a cloud based monthly fee. For some reason last night after moving everyone but my client pc back to the old server so they could use exchange without issue, my client pc outlook decided to start working and is accessing the old server exchange on the new domain. But it is "hinky" and disconnects from the exchange server frequently. Are there any other suggestions than cloud based? Thanks for your time.
-
Wednesday, January 09, 2013 4:29 PM
If you really do need Exchange rather than cloud (and I would be 100% in agreement with you; I don't want Exchange in the cloud either) then I'm afraid you really do only have two choices: Stick with SBS 2003 or get SBS 2011 Standard.
I don't know which country you are in, but here in the UK I am a trustee for a charity (not for profit) and we get our software from CTExchange. Software there costs peanuts - Exchange 2013 is just £26; Windows Server 2012 is £33 etc. They don't list SBS2011 unfortunately due to Microsoft pulling the plug (don't start me on that one....); but it might be that you can get SBS2011 locally from an equivalent reseller.
Jim
- Marked As Answer by Aiden_CaoMicrosoft Contingent Staff, Moderator Monday, January 21, 2013 3:05 AM

