Few days back i installed a new exchange server 2013 as a multi role i-e Mailbox-CAS role. This server was placed in another AD site so all users were not effected but some users in the same site were effected and getting the warning as mentioned in bellow screen shot.
Even that this warning was not critical, but i have to resolve.
To resolve this issue i came to know with the help of bellow command that the auto discover entry was not reset in this new server and was still set as default with the server name as (HYBRID01 https://hybrid01.domain.com/Autodiscover/Autodiscover.xml)
[PS] C:\Windows\system32>Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 15*") -And ($_.ServerRole -L
ike "*ClientAccess*")} | Get-ClientAccessServer | Format-Table Name, AutoDiscoverServiceInternalUri -Auto
Name AutoDiscoverServiceInternalUri
---- ------------------------------
MBX-CAS https://autodiscover.domain.com/autodiscover/autodiscover.xml
MBX-CAS https://autodiscover.domain.com/autodiscover/autodiscover.xml
MBX-CASDR https://autodiscover.domain.com/autodiscover/autodiscover.xml
HYBRID01 https://hybrid01.domain.com/Autodiscover/Autodiscover.xml
Now i have to reset the auto discover enter on this new server as the other servers so i ran the following command.
[PS] C:\Windows\system32>Set-ClientAccessServer -Identity hybrid01 -AutoDiscoverServiceInternalURI https://autodiscove
r.domain.com/autodiscover/autodiscover.xml
Now to verify the updated setting i again ran the following command and got the desired result all servers have the same autodiscover entry.
[PS] C:\Windows\system32>Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 15*") -And ($_.ServerRole -L
ike "*ClientAccess*")} | Get-ClientAccessServer | Format-Table Name, AutoDiscoverServiceInternalUri -Auto
Name AutoDiscoverServiceInternalUri
---- ------------------------------
MBX-CAS https://autodiscover.domain.com/autodiscover/autodiscover.xml
MBX-CAS https://autodiscover.domain.com/autodiscover/autodiscover.xml
MBX-CASDR https://autodiscover.domain.com/autodiscover/autodiscover.xml
HYBRID01 https://autodiscover.domain.com/autodiscover/autodiscover.xml
and the issue reslvoed.
Even that this warning was not critical, but i have to resolve.
To resolve this issue i came to know with the help of bellow command that the auto discover entry was not reset in this new server and was still set as default with the server name as (HYBRID01 https://hybrid01.domain.com/Autodiscover/Autodiscover.xml)
[PS] C:\Windows\system32>Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 15*") -And ($_.ServerRole -L
ike "*ClientAccess*")} | Get-ClientAccessServer | Format-Table Name, AutoDiscoverServiceInternalUri -Auto
Name AutoDiscoverServiceInternalUri
---- ------------------------------
MBX-CAS https://autodiscover.domain.com/autodiscover/autodiscover.xml
MBX-CAS https://autodiscover.domain.com/autodiscover/autodiscover.xml
MBX-CASDR https://autodiscover.domain.com/autodiscover/autodiscover.xml
HYBRID01 https://hybrid01.domain.com/Autodiscover/Autodiscover.xml
Now i have to reset the auto discover enter on this new server as the other servers so i ran the following command.
[PS] C:\Windows\system32>Set-ClientAccessServer -Identity hybrid01 -AutoDiscoverServiceInternalURI https://autodiscove
r.domain.com/autodiscover/autodiscover.xml
Now to verify the updated setting i again ran the following command and got the desired result all servers have the same autodiscover entry.
[PS] C:\Windows\system32>Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 15*") -And ($_.ServerRole -L
ike "*ClientAccess*")} | Get-ClientAccessServer | Format-Table Name, AutoDiscoverServiceInternalUri -Auto
Name AutoDiscoverServiceInternalUri
---- ------------------------------
MBX-CAS https://autodiscover.domain.com/autodiscover/autodiscover.xml
MBX-CAS https://autodiscover.domain.com/autodiscover/autodiscover.xml
MBX-CASDR https://autodiscover.domain.com/autodiscover/autodiscover.xml
HYBRID01 https://autodiscover.domain.com/autodiscover/autodiscover.xml
and the issue reslvoed.
No comments:
Post a Comment