SCOM + Exchange 2010 SP2 test-outlookconnectivity

We have SCOM + Exchange 2010 SP2 and we receive;

Alert: TCP connectivity with Autodiscover - Autodiscover failure

We see the SCOM exchange MP running the the command:

Test-OutlookConnectivity -Protocol:Tcp -TrustAnySSLCert:$true -MonitoringContext:$true

This command gives a failure see below

ClientAccessServer   ServiceEndpoint                               Scenario                            Result  Latency
                                                                                                                  (MS)
------------------   ---------------                               --------                            ------  -------
Exchange2010...                                               Autodiscover: Web service request.  Failure   -1.00

RunspaceId          : c8bfb227-abb7-4ac4-9aac-7fea236c500b
Events              : {Source: MSExchange Monitoring OutlookConnectivity
                      Id: 2003
                      Type: Error
Message: The test step Autodiscover running over protocol 'ncacn_ip_tcp' issued from test user '/
                      o=domain/ou=Exchange Administrative Group (FYDIBOHG34DQFAY)/cn=Recipients/cn=extest_n9v7763gg815
                      4552' failed with error: '-2146233088'. The detailed information of the running instance context:
                       'Mailbox = 'domain.local\extest_n9v7763gg8154', ClientAccessServer = 'domain-Exchange2010.domain.loc
                      al''. The exception: 'Microsoft.Exchange.Monitoring.AutodiscoverTaskException: The Autodiscover r
                      esponse isn't valid. Field = 'AutoDiscoverResponseXML', autodiscoverData = '<Null>'.
                         at Microsoft.Exchange.Monitoring.AutodiscoverTask.ValidateAutoDiscoverResponse(AutoDiscoverRes
                      ponseXML autoDiscoverResponseXML)
                         at Microsoft.Exchange.Monitoring.AutodiscoverTask.AutodiscoverEnd(IAsyncResult asyncResult)'
                      Verbose: Target Site = 'domain.local/Configuration/Sites/domain'
                      Verbose: Target Domain = 'domain.local'
                      Verbose: Target User ='extest_n9v7763gg8154@domain.local'
                      Verbose: Mailbox = 'domain.local\extest_n9v7763gg8154', Owner = '/o=domain/ou=Exchange Administ
                      rative Group (FYDIBOHG34DQFAY)/cn=Recipients/cn=extest_n9v7763gg8154552'
                      Verbose: SMTP address for Autodiscover request ='extest_n9v7763gg8154@domain.com'
                      Verbose: When contactinghttps://autodiscover.domain.com/autodiscover/autodiscover.xml received th
                      e error The remote server returned an error: (401) Unauthorized.
                      Verbose: <?xml version="1.0"?>
                      <Autodiscover xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/
                      2001/XMLSchema" xsi:nil="true" xmlns="http://schemas.microsoft.com/exchange/autodiscover/response
                      schema/2006" />
                      , Source: MSExchange Monitoring OutlookConnectivity
                      Id: 2006
                      Type: Error
                      Message: An exception occurred while the cmdlet was running. This often indicates the test enviro
                      nment isn't prepared correctly. The administrator needs to examine the configuration. Exception d
                      etails: Microsoft.Exchange.Monitoring.TopologyDiscoverException: The cmdlet fails to find all the
                       server information through pinging service providers or other topology discovery inside the doma
                      in. The cmdlet cannot continue. TopologyDiscoverMode = 'UseAutodiscover, UseAddressbook'.
                         at Microsoft.Exchange.Monitoring.OutlookConnectivityContext.get_RpcEndpointServer()
                         at Microsoft.Exchange.Monitoring.RfriClientWrapper.<.ctor>b__1()
                         at Microsoft.Exchange.Monitoring.OutlookConnectivityContext.RpcExceptionWrapper(Func`1 protect
                      edCall)
                         at Microsoft.Exchange.Monitoring.RfriClientWrapper.RfriCall(Func`1 rfriCall)
                         at Microsoft.Exchange.Monitoring.RfriClientWrapper..ctor(OutlookConnectivityContext context)
                         at Microsoft.Exchange.Monitoring.AddressbookTask.get_RfrWrapper()
                         at Microsoft.Exchange.Monitoring.AddressbookTask.GetReferral()
                         at Microsoft.Exchange.Monitoring.OutlookConnectivityBase.SingleCommandTransaction(OutlookConne
                      ctivityTask command, AsyncResult`1 result)
                         at Microsoft.Exchange.Monitoring.AddressbookTask.<BuildTransactions>d__c.MoveNext()
                         at Microsoft.Exchange.Monitoring.OutlookConnectivityBase.<BuildTransactionHelper>d__0.MoveNext
                      ()
                         at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.RunTasksWithTimeout(ExDateTime ex
                      pireTime, IEnumerable`1 task)
                         at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.InternalProcessRecord()}
PerformanceCounters : {Object: MSExchange Monitoring OutlookConnectivity
                      Counter: OutlookConnectivity Latency
                      Instance: domain.local\extest_n9v7763gg8154: RPC-over-HTTP: False, [/Basic], [/Negotiate]
                      Value: -1000}

When i run the same command above on the Exchange server, without the "MonitoringContext" parameter the command Succeeds without problems!

What we tried;

- create a new test user, same problem
- checking the  "Do not require Kerberos preauthentication" in AD user account, same problem
- un-hidde the test user in AD