Windows 10 Office 2016 Outlook Issue

[ITGURU]

Just clean installed the latest windows 10 update 1511 and installed office 2016.

Got the start menu customised nicely and deployed through an XML.

Thought i'd test the shortcuts - Outlook 2016 being one of them.

 

Created a new mailbox and on the first run - gets to the second step of the autodiscovery then crashes out with the error below...

Anyone else had this issue?

Autodiscover works fine for office 2010 and 2013.

 

[ITGURU]

Has anyone else found this issue yet?

 

I've tried with both 32 bit and 64 bit office on Windows 10 with same issue on both... or it comes up with Microsoft Outlook has stopped responding.

[chris_uk]

Just spun up a new VM for work avoidance. I've managed to get Office 2016 installed and Windows 10 education installed and I don't get that error message when I'm setting up a new email account. I've not done any updates, latest ISO from VL site and the latest version of office ISO from the VL site as well.

Exchange is Exchange 2013.

[ITGURU]

I'll have to crash and try another install - Only difference is I'm using enterprise of windows.

As well, I downloaded the latest windows 10 ISO 1511 build and latest version of Office 2016 from the VL site.

[ITGURU]

After several reinstalls and testing, it was simply an issue with the admin account but not sure why....

 

If I logged on as a standard user, and ran outlook the autodiscover worked fine and outlook opened!

However, on the admin user it crashes on outlook 2016, but on Outlook 2013 it works fine on Windows 10

 

Perhaps a bug?!

[john]

After several reinstalls and testing, it was simply an issue with the admin account but not sure why....

 

If I logged on as a standard user, and ran outlook the autodiscover worked fine and outlook opened!

However, on the admin user it crashes on outlook 2016, but on Outlook 2013 it works fine on Windows 10

 

Perhaps a bug?!

 

Domain Admin membership has broken various things for many years in Outlook / Exchange / Lync / Mobile Active Sync etc... that's nothing new, your regular account shouldn't be a Domain Admin it should be a standard use and then elevate as / when required with a separate one.

[ITGURU]

Domain Admin membership has broken various things for many years in Outlook / Exchange / Lync / Mobile Active Sync etc... that's nothing new, your regular account shouldn't be a Domain Admin it should be a standard use and then elevate as / when required with a separate one.

 

Never had any issues in the past. Whenever I've done exchange migrations I've always logged on as a domain admin to test with initially, before then testing as a standard user staff and student.

 

Wasn't my account I was using to test it, it was our cloned 'Administrator' account which we use for workstation admin purposes.