Outlook 2010 Office 365 Direct Access Forced Tunnell Disconnected

Scenario
Windows 7 / Outlook 2010 SP2 + Patches Clients using Direct Access and configured for Forced Tunneling. Clients connect via a webproxy via DA Policy. User mailbox is migrated to Office 365 / Exchange online.  

Problem
When on WAN / LAN normal Wi-Fi, there are no issues. But when client connects over Direct Access, Outlook will not connect to Office 365 and says disconnected.  Windows 7 / Outlook 2010 is fully patched.  (this may be where the problem lies). Access to webmail, normal internet is fine.

Solution / Workaround
At the time of writing there is no official word on Microsoft on this issue. (Although we have a pending case, in which I will update accordingly).

But after trial and error, I stumbled across this KB.  (Not directly related but started the cogs turning.)
So I reversed this setting to Disable MAPI/HTTP (MS new way of connecting to Exchange) by adding the below Key.

Key: HKEY_CURRENT_USER\Software\Microsoft\Exchange
DWORD: MapiHttpDisabled
Value: 1

Note: The setting takes a few minutes to kick in, after it updates via AutoDiscover.

So how do you know when this is kicked in ?

 OK,  so where you would normally see the “connection” tab in account settings, when MAPI/HTTP is enabled,  This disappears..:) Once this is disabled.  It reappears..,

 

Once this became active. Outlook connected Via Direct Access !!!!   Thanks MS. Await the Official KB / Hotfix.... 

Office 365 Hybrid oauth issue - Event ID 3002 - IIS 401

Issue
Free busy requests fail from Office 365 users to on-premise users after oauth is enabled on an Exchange 2013 Hybrid server. 

you may see in the Event log:

event ID 3002
Protocol /EWS failed to process request from identity NT AUTHORITY\SYSTEM. Exception: Microsoft.Exchange.Security.OAuth.InvalidOAuthTokenException: The user specified by the user-context in the token does not exist.

You also may see in the exchange hybrid IIS logs something similar to the below. (where 401 is an authentication fail)

443 - 192.168.1.110 ASProxy/CrossForest/EmailDomain//15.01.0427.019 - 401 0 0 15

Resolution
If after applying the latest Exchange 2013 CU Updates this issue still persists, you can disable the oAuth connector in Exchange online to resolve this issue.

1. Open Exchange online Powershell and connect to your tenant.
2. Get-IntraOrganizationConnector MyHybridConnector | Set-IntraOrganizationConnector -Enabled $false

The change may take 30 minutes to fully update within Office 365, so please be patient.

This issue relates to KB https://support.microsoft.com/en-us/kb/3001281 but its is not clear on what the issue is or how it should be fixed other than disabling the connector. Assume CU would correct, but my lab was Running SP1 CU 11 and I had this issue.

Office 365 / Exchange Online - Outlook 2010 / 2013 /2016 Hangs on entering credentials.... (Not Responding)

Problem

Upon moving to Exchange online. You attempt to open Outlook (Either as en existing Profile (Mailbox Move) or new Profile.) When you are prompted to enter your credentials you are unable to do so and get "Not responding" and are unable to continue.

Cause

This issue is caused by "HP Client Security" Hi-Jacking the logon screen.

Resolution.

• Option 1
• Uninstall HP Client Security

Option 2

• Follow the steps below to disable the Logon Screen interaction.

.

ERROR:Updating hybrid configuration failed with error 'Subtask ValidateConfiguration execution failed: Configure Mail Flow

Scenario
You need to add a new domain to the Hybrid Configuration Wizard. You complete the following correct steps.

• Add Domain to O365 and Verify
• Add Domain to On-Premise Exchange as Authoritative
• Run the HCW and Complete Domain Verification etc...
• At the end the HCW Completes with error:

ERROR:Updating hybrid configuration failed with error 'Subtask ValidateConfiguration execution failed: Configure Mail Flow

A Closer look at the HCW logs may include an error something like:

ERROR:System.Management.Automation.RemoteException: This operation is not required. Organization is already enabled for customization.

Resolution
In my case, there was no rhyme or reason for the HCW to error. So after trawling many Office 365 Blogs and community forums, also having a go at removing connectors as per one MS KB  made no difference (Which is just bad advice anway in my opinion,) here just for ref:

 The following simple steps worked for me.

 1. Connect to your Exchange On-Line via Power shell
     (So a key point here is that you need internet access to Office 365 from the EMC/EMS)

•  $UserCredential = Get-Credential
• $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
• Import-PSSession $Session 

2. Run the following Command against one of your SMTP Domains (Ensure it completes ok)

• Get-FederationInformation -domain mysmtpdomain.com

3. Re-Run HCW. 
                               
                             

All good !!!!  Bizarre, but it works. Hope this helps