Office 365 Manual Configuration
-
Hi All
I got this situation , after moving my email to office 365 . only few user succed to configure on outlook . i want to set manually to outlook 2010, 2013 . how do i know my mail server name , or how to check it
Thanks any help
-
@shybrsky said in Office 365 Manual Configuration:
Hi All
I got this situation , after moving my email to office 365 . only few user succed to configure on outlook . i want to set manually to outlook 2010, 2013 . how do i know my mail server name , or how to check it
Thanks any help
Office365's Echange Online does not work with Outlook 2010. I think 2013 is gone now too. Or will be soon.
-
@jaredbusch so .. no option but upgrade all version to 2016
-
@jaredbusch said in Office 365 Manual Configuration:
@shybrsky said in Office 365 Manual Configuration:
Hi All
I got this situation , after moving my email to office 365 . only few user succed to configure on outlook . i want to set manually to outlook 2010, 2013 . how do i know my mail server name , or how to check it
Thanks any help
Office365's Echange Online does not work with Outlook 2010. I think 2013 is gone now too. Or will be soon.
It works with outlook 2010, just need a few updates. I've about 15 computers with Outlook 2010 and Exchange 365.
-
One way to 'force it' is the Microsoft's SARA tool.
It will do a good bit of the work for you, and has been used by NTG to resolve a number of issues over the last year.
-
Even though O365 will work with Outlook 2010 with some help, you still want to strongly consider upgrading all of your desktops to Office 2016. Eventually, Exchange Online will drop support for Outlook 2010 and 2013.
Typically, your Exchange Online address will be <tenant>.mail.protection.outlook.com
-
@nerdydad said in Office 365 Manual Configuration:
Even though O365 will work with Outlook 2010 with some help, you still want to strongly consider upgrading all of your desktops to Office 2016. Eventually, Exchange Online will drop support for Outlook 2010 and 2013.
Typically, your Exchange Online address will be <tenant>.mail.protection.outlook.comI know, but it's a budget problem, while Office 2010 works with Exchange 365 and they don't let me upgrade the version.
-
@iroal said in Office 365 Manual Configuration:
@nerdydad said in Office 365 Manual Configuration:
Even though O365 will work with Outlook 2010 with some help, you still want to strongly consider upgrading all of your desktops to Office 2016. Eventually, Exchange Online will drop support for Outlook 2010 and 2013.
Typically, your Exchange Online address will be <tenant>.mail.protection.outlook.comI know, but it's a budget problem, while Office 2010 works with Exchange 365 and they don't let me upgrade the version.
ProPremium and up has Office 2016 built into the subscription price of O365. This isn't a budget problem, this is a management problem. Management being scared of change.
-
I as recently as this year had Outlook 2007 working with Office365.
It definitely takes finagling and can often break with O365 updates.
One thing you can try is manually pointing the autodiscover to a local file. That made a huge difference in our setup. (But we also had a hybrid setup (in-house MDaemon server as well) that extra complicated things.)
-
thanks for any respond ..
i did update on office 2010 , it works ..
issue solved -
@jaredbusch Works with 2007, 2010, and 2013.
-
@jackcpickup not sure with 2007 version ,,, but works with 2010 .
-
@shybrsky said in Office 365 Manual Configuration:
@jackcpickup not sure with 2007 version ,,, but works with 2010 .
It did, but was getting harder with each time.
2007 isn't supported anymore, anyway, so no one would recommend being on it.
-
@jackcpickup said in Office 365 Manual Configuration:
@jaredbusch Works with 2007, 2010, and 2013.
Lots of things work. Does not mean it is a supported configuration.
-
@jackcpickup : AFAIK, 2007 no longer works with O365 due to the removal of RPC over HTTP as of Oct 31 2017. They have since switched to MAPI over HTTP which is only supported by Outlook 2010 SP2 and later.
