Skip to main content

How to configure MS Outlook 2010 for Office365 Exchange Server 2013

This procedure is for you if you are using the following online services provided by Microsoft.
  • Office365
  • Recently upgraded from Exchange Server 2010 to Exchange Server 2013.
  • MS Outlook 2007 or 2010
Microsoft sent out an email on how to manage MS Outlook using the new Exchange Server 2013 environment. The new environment provides many features that admin and users will be able to appreciate after your successful transition. I agree with you, the process provided by Microsoft (and even their customer service still using the old procedure when I called them as of 5/15/2013) is NOT detailed but I have a simple solution to fix it. The procedure that help me re-configure all MS Outlook to connect using Offic365 Exchange Server 2013.

I login to the Outlook Web Apps using the user workstation email address and password, click on PC tab to run the Setup. It will download a program for Office365 Desktop, and restart is needed.

If you have any users, having a connection problem using their MS Outlook. Here's what you need to do. 
  • Close MS Outlook
  • Go to Control Panel, Email, Email Accounts 
  • In Email Account, select click on the Name e.g. yourname@whaddya.com (this is user email address), then click Repair. This will automatically update the user mailbox connection setting via autodiscover for the domain name. The user need to enter their email password for authentication. 
  • Click on Close to update your setting. 
  • Open MS Outlook program, MS Outlook will ask you to restart to accept the new settings. 
  • Re-open MS Outlook, and make sure it is not connected Offline (lower right corner of the screen). 
If everything is configured correctly, you will see the current emails.

Let's figure out what changed:
In the Server Settings, the server changed from the fully qualified domain name e.g. BLU12345.outlook.com to 580ead4a-429c-4fdf-a29e-f6ad2a7101e5@whaddya.com (where whaddya.com is equivalent of your Office365 domain name for your company). The random number is unique to every Office365 user, so don't try to copy this from userA to userB or userC. It will not work.

And in Exchange Proxy Settings:
Connection settings, changed from BLU12345.mailbox.outlook.com to outlook.office365.com

Only connect to proxy servers that have this principal name in their ceritificate:
msstd:outlook.com (remain the same)

Good luck with your Office365 transition using Exchange Server 2013.

Please don't hesitate to post your reply if you have additional information to share.
Thank you.

If this helped you, please take the time to share this post by sharing using Google+, Facebook, Twitter, or LinkedIn

Popular posts from this blog

Alternative Social Networks

If you are planning to create your social network e.g. similar to Facebook. Here's a short list of alternative software's:

Open Source and Free​
http://buddypress.org/ - Wordpress (Open Source and Free)http://elgg.org/ - (Open Source and Free)Commercial Social Networks software
http://www.socialengine.com/ ($299 Stand Alone, $29/mo Cloud)http://www.jomsocial.com/ (run with Joomla, need to know CMS)http://www.boonex.com/ (very expensive, $399 for Standard)http://www.anahitapolis.com/http://www.oxwall.org/http://sharetronix.com/http://www.moosocial.com/http://www.jcow.net/http://phpdolphin.comhttp://www.grou.ps (from free to Commercial, I left my networks and they are selling it http://www.phpfox.com/ (I used this before, it's hard to maintain. I moved to NING but left too after it was sold to another company)http://www.ning.com (I don't recommend using this service, it's hard to export your data when it's time to move)Something to check when selecting your next soc…

Example of Out of Office Reply for Terminated Employee

This is a sample message that I used for terminated employees, unless HR staff specified a different message.
=== Example for KING.NET Employee === John Doe (employee or consultant) is no longer with KING.NET effective June 1, 2008 (termination date). For matters relating to "Project Name here" please direct your concerns to John Smith at johnsmith@king.net (Manager or Supervisor). For all other matters, please direct your email to Mary Smith HR at marysmith@king.net.
Please call our main office 703-345-6789 if you have other concerns.
Thank you.
=== end of message ===

Frequent Account Lockout in Active Directory

I have a user in Windows Pro 7, and Windows Server 2003 environment that is frequently account locked out. I tried many different scenarios to resolve this account lockout issue, from resetting his password, changing a new password, remove and re-join the domain, rebooting the workstation and active directory servers.

I tried to use the command prompt utility to run "rundll32.exe keymgrdll, KRShowKeyMgr" (case sensitive) to delete the account in Windows 7 password cache, and still no luck.

Still searching for answer ... Let me know if you encounter a similar issue in Windows Pro 7 and Windows Server 2003.

Continue reading updated post here:
http://www.whaddya.com/2011/09/windows-needs-your-credentials.html