question

DCSKW avatar image
0 Votes"
DCSKW asked Gil-2211 answered

EVOSTS Not found

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

windows-active-directoryoffice-exchange-online-itprooffice-exchange-hybrid-itpro
evo2.jpg (38.6 KiB)
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @DCSKW

Any progress about this issue?

0 Votes 0 ·

Hi @DCSKW

Any update about your issue?

0 Votes 0 ·
joyceshen-MSFT avatar image
0 Votes"
joyceshen-MSFT answered HendriPieterse-3421 commented

Hi @DCSKW

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.
 


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for the above. We do get success resultson both sites (on prem and online)

when we run Get-AuthServer | where {$.Name -eq “EvoSts”}. it dispays nothing. If we run Get-AuthServer | FL it shows the evosts server as well as domaincontroller as the originating server
so we ran the HWB again as per microsoft instructions but still do not get results with Get-AuthServer | where {$
.Name -eq “EvoSts”}

And if we run Set-AuthServer -Identity EvoSTS -IsDefaultAuthorizationEndpoint $true it cannot find the object on the domain controller. We have checked in the setup logs that the service was setup and no 8064 errors were given. is there anything we have missed?

0 Votes 0 ·
ScotJohnson-8253 avatar image
0 Votes"
ScotJohnson-8253 answered

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?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ThomasColeman-0246 avatar image
0 Votes"
ThomasColeman-0246 answered ThomasColeman-0246 published

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?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ScotJohnson-8253 avatar image
0 Votes"
ScotJohnson-8253 answered

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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

06296771 avatar image
0 Votes"
06296771 answered 06296771 edited

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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Gil-2211 avatar image
0 Votes"
Gil-2211 answered

Same issue here - Set-AuthServer -Identity "EvoSTS - {GUID}" -DomainController "FQDN" -IsDefaultAuthorizationEndpoint $true returns the same results that the domain controller:

The operation couldn't be performed because object 'EvoSTS - {GUID}' couldn't be found on '*'.

In my case, I'm running fresh install of Exchange 2019 CU9 with latest patch from May 2021 and separate Windows Server 2019 and ran the latest Exchange Hybrid Wizard like 100 times.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.