MatthewDK
asked on
msExchServerSite Value Not Updating
In AD Sites & Services, we have four sites set up...
Site A = 192.168.1.0/24
Site B = 192.168.0.0/24
Site C = 192.168.4.0/24
Default-First-Site-Name, not assigned any subnets.
Sites A & B have two DCs a piece. All DCs are GCs. Site C has one DC which is a GC.
Sites A & B have one Exchange 2013 server a piece. Both servers have the Mailbox and Client Access roles. The Exchange servers were brought into AD before Sites & Services was set up. So their Site and AutoDiscoverSiteScope were originally set to Default-First-Site-Name.
Once we established our sites, we assumed the msExchServerSite value would update automatically based on site affinity. It has not. We have dealt with the issues that result from both servers being assigned to the Default-First-Site-Name for long enough and wish to get this corrected.
How do we get the site affinity to update, and once it does, will we still have to run the command, Set-ClientAccessServer <server name> –AutoDiscoverSiteScope <name of AD Site>, to correct the AutoDiscoverSiteScope?
Some Shell commands below for reference...
[PS] C:\>get-exchangeserver | ft name,site -autosize
Name Site
---- ----
MAIL1 domain.local/Configuration /Sites/Def ault-First -Site-Name
MAIL2 domain.local/Configuration /Sites/Def ault-First -Site-Name
[PS] C:\>get-clientaccessserver | ft name,autodiscoversitescope -autosize
Name AutoDiscoverSiteScope
---- ---------------------
MAIL1 {Default-First-Site-Name}
MAIL2 {Default-First-Site-Name}
[PS] C:\>get-adsite
Name HubSiteEnabled
---- --------------
Default-First-Site-Name False
Site A True
Site B False
Site C False
[PS] C:\>nltest /dsgetsite
Default-First-Site-Name
Site A = 192.168.1.0/24
Site B = 192.168.0.0/24
Site C = 192.168.4.0/24
Default-First-Site-Name, not assigned any subnets.
Sites A & B have two DCs a piece. All DCs are GCs. Site C has one DC which is a GC.
Sites A & B have one Exchange 2013 server a piece. Both servers have the Mailbox and Client Access roles. The Exchange servers were brought into AD before Sites & Services was set up. So their Site and AutoDiscoverSiteScope were originally set to Default-First-Site-Name.
Once we established our sites, we assumed the msExchServerSite value would update automatically based on site affinity. It has not. We have dealt with the issues that result from both servers being assigned to the Default-First-Site-Name for long enough and wish to get this corrected.
How do we get the site affinity to update, and once it does, will we still have to run the command, Set-ClientAccessServer <server name> –AutoDiscoverSiteScope <name of AD Site>, to correct the AutoDiscoverSiteScope?
Some Shell commands below for reference...
[PS] C:\>get-exchangeserver | ft name,site -autosize
Name Site
---- ----
MAIL1 domain.local/Configuration
MAIL2 domain.local/Configuration
[PS] C:\>get-clientaccessserver
Name AutoDiscoverSiteScope
---- ---------------------
MAIL1 {Default-First-Site-Name}
MAIL2 {Default-First-Site-Name}
[PS] C:\>get-adsite
Name HubSiteEnabled
---- --------------
Default-First-Site-Name False
Site A True
Site B False
Site C False
[PS] C:\>nltest /dsgetsite
Default-First-Site-Name
ASKER
Thank you, but I don't understand how cloning the Autodiscover service connection point (SCP), Outlook Anywhere FQDNs, and all Exchange virtual directory internal/external URLs to our already in-production server will help with this issue. Our issue is with the server not associating itself with the correct site.
can you post the result of the below, without the <>, for each of the exchange servers
such as
nltest /DSADDRESSTOSITE:<ip address of exchange server>
such as
nltest /DSADDRESSTOSITE:192.168.0.100
ASKER
Here are the results...
nltest /dsaddresstosite:192.168.1 .2
Get the site-subnet mapping for '192.168.1.2' from '\\SiteA_DC.wbd.local'.
192.168.1.2 Site A 192.168.1.0/24
nltest /dsaddresstosite:192.168.0 .4
Get the site-subnet mapping for '192.168.0.4' from '\\SiteA_DC.wbd.local'.
192.168.0.4 Site B 192.168.0.0/24
This command has the IP addresses of our two Exchange servers in the correct sites.
nltest /dsaddresstosite:192.168.1
Get the site-subnet mapping for '192.168.1.2' from '\\SiteA_DC.wbd.local'.
192.168.1.2 Site A 192.168.1.0/24
nltest /dsaddresstosite:192.168.0
Get the site-subnet mapping for '192.168.0.4' from '\\SiteA_DC.wbd.local'.
192.168.0.4 Site B 192.168.0.0/24
This command has the IP addresses of our two Exchange servers in the correct sites.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We did indeed have HKEY_LOCAL_MACHINE\System\ CurrentCon trolSet\Se rvices\Net logon\Para meters\Sit eName registry entry present, and it was hard-coded to Default-First-Site-Name.
Deleting the entry from both mail servers and restarting them has addressed part of the issue. Running the command, get-exchangeserver | ft name,site -autosize, provides the following output...
Name Site
---- ----
MAIL1 domain.local/Configuration /Sites/Sit e A
MAIL2 domain.local/Configuration /Sites/Sit e B
So that is perfect. However, running the command, get-clientaccessserver | ft name,autodiscoversitescope -autosize, still references the Default-First-Site-Name...
Name AutoDiscoverSiteScope
---- ---------------------
MAIL1 {Default-First-Site-Name}
MAIL2 {Default-First-Site-Name}
What is the best course of action to get that to accurately reflect our AD sites?
Deleting the entry from both mail servers and restarting them has addressed part of the issue. Running the command, get-exchangeserver | ft name,site -autosize, provides the following output...
Name Site
---- ----
MAIL1 domain.local/Configuration
MAIL2 domain.local/Configuration
So that is perfect. However, running the command, get-clientaccessserver | ft name,autodiscoversitescope
Name AutoDiscoverSiteScope
---- ---------------------
MAIL1 {Default-First-Site-Name}
MAIL2 {Default-First-Site-Name}
What is the best course of action to get that to accurately reflect our AD sites?
I would suggest the script that I suggested in my first comment.
For further reading you may find this useful https://blogs.msdn.microsoft.com/brad_hughes/2007/09/11/autodiscoversitescope-and-client-only-sites/
For further reading you may find this useful https://blogs.msdn.microsoft.com/brad_hughes/2007/09/11/autodiscoversitescope-and-client-only-sites/
https://gallery.technet.microsoft.com/scriptcenter/Sets-the-Autodiscover-SCP-5a642f32