?
Solved

Outlook 2010 an encrypted connection to your mail server is not available. during migration to office 365

Posted on 2016-09-16
11
Medium Priority
?
82 Views
Last Modified: 2016-09-22
I'm having a major issue to migrate to Office 365, at fist I was trying to use Outlook 2007 and got the same problem now I've installed Outlook 2010 and still having the same issue. Can someone try to help me.
0
Comment
Question by:jdff
  • 5
  • 3
  • 2
  • +1
11 Comments
 
LVL 18

Expert Comment

by:Todd Nelson
ID: 41802579
What are you migrating from ... Exchange, Hosted Exchange, other?  What method/tool are you using to migrate the mailboxes?

FYI... Office 2010 and older are not supported with Office 365.  They may work but are not supported.

Previous versions of Office, such as Office 2010 and Office 2007, may work with Office 365 with reduced functionality. Get more details about which Office versions are supported.

    - https://products.office.com/en-us/office-system-requirements/#Office365forBEG
0
 
LVL 1

Author Comment

by:jdff
ID: 41802582
From a local exchange 2003 server.
0
 
LVL 18

Expert Comment

by:Todd Nelson
ID: 41802585
How did you migrate the mailboxes from Exchange 2003 to Exchange Online?

Can you access the Exchange Online mailboxes from http://outlook.office365.com?
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
LVL 18

Expert Comment

by:Ivan
ID: 41802929
Hi,

have you already managed to migrate mailboxes? If so, have you reconfigured DNS records?
Do you have problem connecting from inside your LAN and Outside as well?

Can you download trial of Office 2016 and try with it?
As Todd said, Outlook 2007 is not supported, and Outlook 2010 needs to have SP2 with hotfix KB2965295 and KB2956191.

Regards,
Ivan.
0
 
LVL 1

Author Comment

by:jdff
ID: 41803047
Yes, office365 is configured and working fine, I can ping the autodiscover record without a problem from my lan. I have 3 computers that migrated just fine to office 365 some with Outlook 2007 and some with Outlook 2010, now I have 4 more computers that gives me the encryption message. I have download the assistant tool from Office 365 and it did not find anything. I'm sure this is not an autodiscover issue, this is something with the Outlook itself. It has to be, why the 3 computers connected just fine and others are not connecting.
0
 
LVL 18

Expert Comment

by:Ivan
ID: 41803122
That is very strange, since Outlook 2007 is not supported. I have no idea why is it working in the first place..
As said, see if you have SP2 with those KB installed first.

Regards,
Ivan.
0
 
LVL 1

Author Comment

by:jdff
ID: 41803174
Just installed SP2 on Office 2010 and still same message. Ive attached the crazy message, have no idea on what to do next.
Desctop-screenshot.png
0
 
LVL 18

Expert Comment

by:Ivan
ID: 41803283
Do you have a license for Outlook 2013 or 2016?
0
 
LVL 1

Accepted Solution

by:
jdff earned 0 total points
ID: 41803285
Problem solved guys, the Kaspersky antivirus was the culprit, as soon I've disabled it, it worked perfectly.
0
 
LVL 15

Expert Comment

by:Edwin Hoffer
ID: 41804304
Hello user,
The connectivity error is very general. The error occur for different reasons. It is typically occurred because of following conditions:
1. Due to incorrect user name, password.
2. Correct Exchange online information for the user account s prevented.
3. Due to Network connectivity issues.

If these are correct then please check you Antivirus it must be restricting your Outlook to migrate.
0
 
LVL 1

Author Closing Comment

by:jdff
ID: 41810372
Problem Solved
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The Exchange database may sometimes fail to mount owing to various technical reasons. A dismounted EDB file can be the source of many Exchange errors including mailbox inaccessibility for users. Resolving the root cause of mounting problems becomes …
Let us take a look at the scenario, you have a database that is corrupt and you run the ESEUTIL command only to find you are unable to repair it. How do you now get the data back?
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
The video provides a quick and easy steps to migrate MBOX file to well known Outlook PST and Office 365. Besides this, it also supports and migrates more than 20 email clients of MBOX which include AppleMail, Opera, Thunderbird and SeaMonkey effortl…
Suggested Courses

601 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question