EVOSTS Not found

Moonlight 176 Reputation points
2021-01-14T16:37:35.117+00:00

Hello

I went through all HMA steps but i have the below issues shown when i run the below shell

Set-AuthServer EvoSTS -IsDefaultAuthorizationEndpoint $true

56682-evo2.jpg

but i can see the EVOSTS create on domain controller from adsiedit and it has been created in the same time when i ran the Exchange 2016 hybrid wizard

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,995 questions
Microsoft Exchange Online Management
Microsoft Exchange Online Management
Microsoft Exchange Online: A Microsoft email and calendaring hosted service.Management: The act or process of organizing, handling, directing or controlling something.
4,253 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,918 questions
{count} votes

6 answers

Sort by: Most helpful
  1. Joyce Shen - MSFT 16,646 Reputation points
    2021-01-15T02:16:29.307+00:00

    Hi @Moonlight

    As you mentioned in the previous thread, you can run the Get-AuthServer command successfully

    Please run the Get-AuthServer | FL to check the detailed information, pay attention to the OriginatingServer

    56934-qa-2021-01-15-10-06-56.png

    Check if the value returned same as the error information above.

    Then run the command below to get EvoSts again

    Get-AuthServer -DomainController "FQDN" -Identity EvoSts   
    

    If an Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
     


  2. Anonymous
    2021-03-05T14:59:05.25+00:00

    We have the same issue, Get-AuthServer returns EvoSts and using FL returns FQDN of DC, yet running Get-AuthServer -DomainController "FQDN" -Identity EvoSts returns object not found.

    When running Get-AuthServer | where {$_.Name -like "Evo"}, it also returns EvoSts

    Anyone have a solution to this?

    0 comments No comments

  3. Thomas Coleman 1 Reputation point
    2021-04-01T04:22:42.61+00:00

    we have the same issue on Exchange 2019 CU8

    Exactly the same as above can run the powershells and does not come up with any thing also errors on the DC powershell, so far we can not move forward with enabling HMA.

    anyone got a solution to this?

    0 comments No comments

  4. Anonymous
    2021-04-01T10:36:54.107+00:00

    Thomas,

    In our case we had setup in AADConnect (ADSync) to sync with Azure a few years ago. I found a couple of entries located here in ADSIEdit:

    " CN=Auth Servers,CN=Auth Configuration,CN="ExchanheDomain",CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com"

    I deleted both those entries and re-ran the Azure AD Connect wizard selecting Hybrid (as this is a new hybrid install for us).

    I then was able Get-AuthServer -DomainController "FQDN" -Identity EvoSts and then set it to $True.

    0 comments No comments

  5. Константин Быков 1 Reputation point
    2021-05-19T10:16:45.727+00:00

    Hello, try
    Set-AuthServer -Identity "EvoSTS - {GUID}" -Domain "Tenant Domain" -IsDefaultAuthorizationEndpoint $true
    Set-OrganizationConfig -OAuth2ClientProfileEnabled $true

    0 comments No comments