Pre-Exchange Server 2003 Service Pack 2 Behavior
Prior to Exchange Server 2003 Service Pack 2, Outlook MAPI clients would receive either a referral to a global catalog server or use the Excha...
Updated Jul 01, 2019
Version 2.0
Blog Post
If I'm understanding this right, does that mean there is no way to force a user to use a GC in their own site? For example:
Lets say we centralized Exchange and consolidated to a couple of Exchange servers in Site A (Chicago). The users are in Site A of course, Site B (NY), Site C (Miami), Site D (L.A.), and site E (Denver). All sites have a GC, and all the users and servers are in the same domain (although not a single domain organization due to an empty root domain, for all intents and purposes it acts as a single domain. )
Obviously we would like a user in Miami to normally hit the GC in Miami, but it sounds like they will instead always hit Chicago. I understand that since the user has no IP address it would be hard to determine their site... :) but is there no way around this?
In any case thanks for the article, this blog really is great for learning stuff I'd probably never know otherwise...
Lets say we centralized Exchange and consolidated to a couple of Exchange servers in Site A (Chicago). The users are in Site A of course, Site B (NY), Site C (Miami), Site D (L.A.), and site E (Denver). All sites have a GC, and all the users and servers are in the same domain (although not a single domain organization due to an empty root domain, for all intents and purposes it acts as a single domain. )
Obviously we would like a user in Miami to normally hit the GC in Miami, but it sounds like they will instead always hit Chicago. I understand that since the user has no IP address it would be hard to determine their site... :) but is there no way around this?
In any case thanks for the article, this blog really is great for learning stuff I'd probably never know otherwise...