One of the areas we know can be costly for our customers is the cost of having a large helpdesk staff to investigate and resolve issues reported by users. We've done an extensive scrub of MSIT's he...
Updated Jul 01, 2019
Version 2.0
Blog Post
A "Last Updated" and an easier to find "Update GAL" would be awesome in the UI!
Here is another issue. I don't have the exact metrics on it, but in the last couple months I would easily guess we've had close to a dozen tickets have come it. Bear with me here, it takes a bit to explain.
We have a rather large AD environment, 14 domains, 135 DCs (way too many, need to streamline), >100 AD sites. All of Exchange 2003 is centralzied in one AD domain, one AD site, and we have about 30,000 mailboxes at present time.
The Exchange topology generator only returns a list of 10 GCs which can be used by clients. Given my supergalactic mathematical abilities, I believe "14 domains > 10 GCs" to be true. This leaves at any given time 4 domains who's users cannot self-edit DLs, Delegates, and other items because Outlook is using a non-home domain GC for its operations. This also means we are overloading GCs by directing thousands upon thousands of users to single GCs within certain domains because the topology generator only discovered and published one GC in some domains.
I've been through all of the KBs, all of the EHLO blog entries, read all the workarounds, done all of the best practices with AD site links, worshipped the mail gods, made offers of exquisite tequilas, etc...
Unfortunately all of the present workarounds can fix one thing, but break another feature in the process. Our users are getting quite testy and seem to get awfully bothered by having to ask the IT employees to edit their DLs for them.
Help! :) I've been told before on this blog that even 2007 SP1 doesn't change this behavior, is it true? Our environment needs more than 10 GCs to be returned, and further more the ability for the topology generator to discover GCs beyond one AD site-link hop away from the Exchagne centralized site. Our site structure is very hub and spoke so we have many clients 2 hops away from Exchange from an AD site structure perspective. Sometimes we have Exchange AD Site --> Main AD Hub Site --> Regional AD Hub Site --> Client AD Site
Thank you!
Here is another issue. I don't have the exact metrics on it, but in the last couple months I would easily guess we've had close to a dozen tickets have come it. Bear with me here, it takes a bit to explain.
We have a rather large AD environment, 14 domains, 135 DCs (way too many, need to streamline), >100 AD sites. All of Exchange 2003 is centralzied in one AD domain, one AD site, and we have about 30,000 mailboxes at present time.
The Exchange topology generator only returns a list of 10 GCs which can be used by clients. Given my supergalactic mathematical abilities, I believe "14 domains > 10 GCs" to be true. This leaves at any given time 4 domains who's users cannot self-edit DLs, Delegates, and other items because Outlook is using a non-home domain GC for its operations. This also means we are overloading GCs by directing thousands upon thousands of users to single GCs within certain domains because the topology generator only discovered and published one GC in some domains.
I've been through all of the KBs, all of the EHLO blog entries, read all the workarounds, done all of the best practices with AD site links, worshipped the mail gods, made offers of exquisite tequilas, etc...
Unfortunately all of the present workarounds can fix one thing, but break another feature in the process. Our users are getting quite testy and seem to get awfully bothered by having to ask the IT employees to edit their DLs for them.
Help! :) I've been told before on this blog that even 2007 SP1 doesn't change this behavior, is it true? Our environment needs more than 10 GCs to be returned, and further more the ability for the topology generator to discover GCs beyond one AD site-link hop away from the Exchagne centralized site. Our site structure is very hub and spoke so we have many clients 2 hops away from Exchange from an AD site structure perspective. Sometimes we have Exchange AD Site --> Main AD Hub Site --> Regional AD Hub Site --> Client AD Site
Thank you!