Far-Flung DC
We have a domain in Japan called JAPAN (clever, huh) in Forest PACIFIC.
We have a local domain in Chicago called LOCAL (even better) in forest USA.
People in Japan are complaining that an application on the Chicago Citrix server is very slow. When users in Japan log into LOCAL.USA accounts the app is quick, but we want to eliminate all non-domestic based LOCAL accounts. It has been determined that the app in question is very chatty and continually authenticates to JAPAN.PACIFIC domain controllers.
I response, we are going to place a domain controller for the JAPAN.PACIFIC domain in Chicago so that the app server and the domain controller are physically close.
Question: assuming we have no firewall issues, should we make an AD site between the JAPAN.PACIFC DC in Chicago and the DCs in Japan?
Or maybe make a site between the JAPAN.PACIFIC DC and the Chicago based Citrix server? That seems more to the point of making AD sites and I wouldnt think latency between the JAPAN.PACIFIC DCs in Japan and Chicago would be an issue.
Any thoughts? Thanks.
May 8th, 2008 12:46am