[ms office - 2016] Outlook 2016 profile setup crashes with proxy

[timbo343]

We are rolling out Office2016 and enabling admin users to use Outlook2016 however after testing we have found that outlook crashes when a proxy is enabled. Disabling the proxy allows outlook to set their profile up. Once the profile has been setup, the proxy server can be turned back on. The trouble is turning off the proxy server whilst we set thsi up is not an option and was wondering if anyone knows how to get round this.

 

Thanks

[Edu-IT]

So is it crashing before you even set the profile up?

[Edu-IT]

Tried any of this?

 

https://support.microsoft.com/en-gb/kb/3119083

[timbo343]

Yup, its the olmapi32.dll error. see attached. The image that shows the crash is with proxy enabled, and the one which completes is with proxy removed.

 

Ive tried those settings, they dont make any difference.

Edited August 11, 2016 by timbo343

[timbo343]

Change the value of ProxySettingsPerUser to 0 completely disables the proxy on the machine.

 

Might have just tried something else.. which has just worked for domain admin, just need to try it for a user now - its the automatic settings, unticking it made it work however when i tried earlier it failed.

[timbo343]

GOT IT! Its the automatic configuration setting, disabling this makes the outlook profile creation work. I guess i dont need this enabled as i dont have a WPAD configuration on the network. Edited August 11, 2016 by timbo343

[Edu-IT]

GOT IT! Its the automatic configuration setting, disabling this makes the outlook profile creation work. I guess i dont need this enabled as i dont have a WPAD configuration on the network.

Good to hear. That's described in the article above, should anyone else come across the issue.

[timbo343]

Just to come back to this, ive wanted to know what the automatically detect settings actually does and here is MS's explanation https://technet.microsoft.com/en-us/library/cc713344.aspx along with a 3rd party http://ask-leo.com/do_i_want_to_let_my_browser_automatically_detect_settings.html

 

I guess usually it can be turned off as these days i guess most of us are using registry imports to specify the proxy server on site.

 

Edit... just found out what it does! If you run various web servers and you connect to them like http://computername then this wont work anymore with automatically detect settings disabled. You would need to connect to them using http://computername.domain so it looks like we will have to have a little script that we can use that disables automatically detect settings whilst we configure outlook or we only allow this setting to be altered in internet explorer settings.

Edited August 12, 2016 by timbo343

[timbo343]

So last nights testing was a waste of time, tried to replicate the tests but they didnt work so ive reverted back to leaving automatically detect settings on with the proxy.

 

Machines are in an impero group called OUTLOOK - TEMP STORE with Microsoft Outlook blocked from running, this way staff (16 of them) will contact us to complain about outlook or we will leave a note on their desk.

 

Once we are contacted, we will remove the machine from the temp group and have a VBS file that we can run on staff sessions that will import a registry entry to disable the proxy whilst we configure outlook for users.

 

Once outlook has been setup we will run the enable proxy VBS which puts the registry back to how it was.

[timbo343]

One last time to update this. the problem that was causing the http://computername pages not to load was down to my error in the group policy registry entry ProxyOverride. I missed a ; between *.domain and .

 

Now i have automatically detect settings disabled and things are working great .

[Simcfc73]

Having the exact same issue, I migrated to Exchange 2016 from 2013 which I thought would be an easy job but its been a right pain.

 

I thought it was my autodiscover messed up with the migration but unticking the box fixed it.

 

Only issue is the teachers that have come in over the holidays who tried to run outlook have a corrupt profile but I'll just wipe those out.

[timbo343]

Yup thats happened today.

We ended up taking out the proxy and leaving automatically detect settings unticked. We also have settings and control panel open for now until we get all 16 users on outlook. The rest use web outlook. Some staff struggled to find outlook as they were looking for the orange 2010 outlook symbol rather than the 2016 blue one.

[Simcfc73]

I'm also migrating to Windows 10 so its all over the shop here...

[timbo343]

I'm also migrating to Windows 10 so its all over the shop here...

 

Hope its going ok for you. We've finished barring 4 machines but we are finding little problems with ltsb 2015. For example, eclipse and identikit (finger print reader). It kinda works with administrator but not domain admin.

 

The majority of staff will be fine at ours, we just need to sort out admin.

 

On top of this a new phone system to learn. Obe of the busiest years for us.