![microsoft activesync outlook 2010 microsoft activesync outlook 2010](https://www.memotoo.com/img/screenshot/065.png)
![microsoft activesync outlook 2010 microsoft activesync outlook 2010](https://windows-cdn.softpedia.com/screenshots/Outlook-Sync-Db-2009-Light_9.png)
Result of this, my iPod touch can talk activesync to Exchange, but my freakin' desktop Outlook cannot. Case in point, where I work I have OWA and Activesync, but no Outlook Anywhere. This make them seem to be the same, but they are not. Where I think the confusion sets in, MOST of the time, admins seem to set up Outlook Anywhere(a proxy), Activesync, and OWA on the same public server. Outlook Anywhere is Outlook wrapping RPC in HTTPS(Why can't you just expose RPC to the world?)Īctivesync is how WM phones/Blackberry's/iPhones/etc talk to Exchange. OWA is IIS serving up a web version of Outlook. To do this, open a blank MMC by navigating to Start>Run then launching mmc.exe. RPC is how Outlook connects to Exchange on the LAN(or VPN), you always hide this behind the firewall. Both to request an enrolment certificate, and to request subsequent end-user certificates for ActiveSync authentication, we’ll need to use the Certificates Microsoft Management Console (MMC) snap-in, focused on the current user’s certificate store. It seems there's 4 ways to connect to exchange: RPC, RPC over HTTPS(eg. I wrote the question that you linked to in your edit, a question I still haven't found a good answer to. Obviously, it would be much nicer to add it as a second Exchange account.). (This doesn't have anything to do with the question, but I'm actually using this second corporate account in Outlook by POP3'ing to Gmail, and then IMAP4 from Gmail to Outlook. Is that correct? If so, it doesn't really semm quite right as absolute worst-case, one could (theoretically) resort to screen-scraping OWA.Įdit: this looks to be about the same as Activesync/OWA Desktop Client? I'm not very familiar with configuring Exchange servers, but in talking to those who are, it sounds like enabling Outlook Web Access is (slightly) different than allowing access from Outlook via HTTP(s).
![microsoft activesync outlook 2010 microsoft activesync outlook 2010](https://dyu7vpdere39o.cloudfront.net/10023:2063881:517639?fileName=Outlook%20Settings.png)
With this second account, the only supported access is through OWA while POP3 access is available, it is not actually suported.
![microsoft activesync outlook 2010 microsoft activesync outlook 2010](https://www.msoutlook.info/pictures/owa-settings-mobile-devices.png)
Specifially, in additional to my regular corporate (Exchange) account, I also use another corporate account through OWA. I'm wondering if there is any way to use this together with a (different) Outlook Web Access account to also get that email in Outlook. If everything authenticates properly, the Server and Username Fields will be underlined and you can now click Next, and complete the wizard.One of the new features of Outlook 2010 (beta) is the support for multiple Exchange accounts. Type in the Office 365 credentials here.ġ1. Select OK twice, and then Click Check Name at the Add New Account screen.ġ0. Once again, use the name of the server as noted in the Outlook Web App screen.ĩ. Navigate to the Connection tab, check the Connect to Microsoft Exchange using HTTP tick box and click on the Exchange Proxy Settings button.Ĩ. Instead, click on the More Settings button.ħ. Put in the user’s Office 365 email address in the User Name.ĭO NOT CLICK the Check Name button yet. The server name is the name of the Outlook Web App server, with an extra “ mailbox” added in. Select Microsoft Exchange or compatible service.Ħ. Select Manually configure server settings or additional server types.ĥ. Open up the Add New Account wizard (From the Mail settings in the Control Panel)Ĥ. Note down the address of the server – ie. Login to the Microsoft Online Services portal at and open up the Outlook Web App.Ģ. In this case, it may be necessary to manually configure Outlook 2010 to connect to the Office 365 servers.ġ. Sometimes, the domain hosting company is not able to properly configure autodiscover CNAME records to enable the domain to work properly with the Office 2010 auto configuration wizard.