Решено не проходит Test-OutlookConnectivity

[quake]

Добрый день, на одном из двух серверов exchange 2016 в кластере, не проходит синтетический тест Test-OutlookConnectivity
Посоветуйте что делать...

[PS] C:\Windows\system32>Get-ServerHealth mail2 | ?{$_.HealthSetName -eq "Outlook.Protocol"}
Выполняется создание нового сеанса для неявного удаленного взаимодействия команды "Get-ServerHealth"...

Server State Name TargetResource HealthSetName AlertValue ServerComp
onent
------ ----- ---- -------------- ------------- ---------- ----------
mail2 NotApplicable PrivateWorkingSet... msexchangemapimai... Outlook.Prot... Healthy None
mail2 NotApplicable ProcessProcessorT... msexchangerpcprox... Outlook.Prot... Healthy None
mail2 NotApplicable ProcessProcessorT... msexchangerpcprox... Outlook.Prot... Healthy None
mail2 NotApplicable CrashEvent.msexch... msexchangemapimai... Outlook.Prot... Healthy None
mail2 NotApplicable OutlookRpcSelfTes... Outlook.Prot... Unhealthy None
mail2 NotApplicable CrashEvent.M.E.rp... microsoft.exchang... Outlook.Prot... Healthy None
mail2 NotApplicable CrashEvent.msexch... msexchangerpcprox... Outlook.Prot... Healthy None
mail2 NotApplicable PrivateWorkingSet... microsoft.exchang... Outlook.Prot... Healthy None
mail2 NotApplicable ProcessProcessorT... microsoft.exchang... Outlook.Prot... Healthy None
mail2 NotApplicable ProcessProcessorT... msexchangemapimai... Outlook.Prot... Healthy None
mail2 NotApplicable PrivateWorkingSet... microsoft.exchang... Outlook.Prot... Healthy None
mail2 NotApplicable OutlookRpcDeepTes... Outlook.Prot... Unhealthy None
mail2 NotApplicable PrivateWorkingSet... msexchangemapimai... Outlook.Prot... Healthy None
mail2 NotApplicable PrivateWorkingSet... msexchangerpcprox... Outlook.Prot... Healthy None
mail2 NotApplicable ProcessProcessorT... microsoft.exchang... Outlook.Prot... Healthy None
mail2 NotApplicable PrivateWorkingSet... msexchangerpcprox... Outlook.Prot... Healthy None
mail2 NotApplicable RpcHttpEventlogMo... MAIL2 Outlook.Prot... Healthy None
mail2 NotApplicable ProcessProcessorT... msexchangemapimai... Outlook.Prot... Healthy None

 

[Surf_rider]

а еще есть какие либо ошибки..

 

[quake]

Exception: Microsoft.Exchange.Rpc.RpcException: Error 0x5 (Отказано в доступе) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName:
EEInfo: ProcessID: 23716
EEInfo: Generation Time: 26.06.2020 10:11:53
EEInfo: Generating component: 2
EEInfo: Status: 0x00000005
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long: 0 (0x00000000)
---------------------------------------------------------

MonitorIdentity StartTime EndTime Result Error Exception PoisonedCo
unt
--------------- --------- ------- ------ ----- --------- ----------
OutlookMapiHttp.Protocol\OutlookMapiH... 26.06.2020 1... 26.06.2020 1... Failed Error 0x5 (Отказа... Microsoft.Exchang... 0
---------------------------------------------------------

 

[Surf_rider]

Проверьте значение реестра , пишут что начинает работать если = 2, значение по умолчанию - 0
LmCompatibilityLevel

по пути HKLM\SYSTEM\CurrentControlSet\Control\Lsa



Specifies the mode of authentication and session security to be used for network logons.

TABLE 2

Value	Meaning
0	Clients use LM and NTLM authentication, but they never use NTLMv2 session security. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
1	Clients use LM and NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
2	Clients use only NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controller accepts LM, NTLM, and NTLMv2 authentication.
3	Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
4	Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controller refuses LM authentication responses, but it accepts NTLM and NTLMv2.
5	Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controller refuses LM and NTLM authentication responses, but it accepts NTLMv2.

 

[quake]

помогло но еще нужна была перезагрузка