Jump to content

Recommended Posts

Posted

Hi All,

 

Been trying to prepare for rolling out Windows 10 over the summer holidays to our PCs. Currently at the testing phase and having a problem getting Windows 10 to connect to our Exchange 2010 server (Server 2008) using Outlook 2016. We're currently using SCCM to deploy and the 3 installs that we did are having sporadic bursts between working and not (Two installed via SCCM, the other installed via disk). after doing a shift+f9 for sending and receiving it comes up with the error code 0x80040115, looked it up but this is a non admin account problem and can't do any of the suggestions.

 

PC1: can get onto outlook but doesn't receive any mails and comes up with the code. (installed via disk)

PC2: Gets onto outlook but randomly disconnects now and again (installed via SCCM)

PC3: Doesn't even open the application stating that it cannot connect and then closes the application.

 

Any suggestions?

Posted

Three things to check and ensure are in place...

 

On the proxy settings page in IE make sure that the "automatically detect settings" check box is NOT ticked

In your proxy exceptions, ensure that your exchange server is covered by an exception. Either by having a *.domain.com wildcard value in there or by manually specifying exchangeserver.domain.com

Ensure autodiscover is set up correctly in Exchange and DNS (should be in your case if it is allowing you to set up the mailbox profile in Outlook)

 

Both of these can be rolled out by GPO

Posted
We get pc3 a lot when we have a corrupt profile do you use roaming profiles Richard

 

We are currently using UEV for the profile that I have been using for testing (my own account)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...