EDIT: This post has been updated on 5/20/2008 to include a link to an Outlook 2007 hotfix for this behavior.
If you have been struggling with Delegate errors in multi-domain environments where you co...
Updated Jul 01, 2019
Version 2.0
Blog Post
4 MIN READ
Understanding multi-domain DL update and delegate issues after application of Exchange 2003 SP2 - Part 2
I'm laughing at ..."SOB Error" ... because it certainly is one. :)
Will the reg key be automatically created with the necessary value, or does this just make Outlook check for it and it is still up to us to actually enable a value for the key?
We've got 14 domains and 30,000 + users. It will be a bit of a hassel to get the hotfix installed everywhere (although I'm thankful it now exists!). Is there any chance of making Exchange topology discoverer & DSAccess discover/use more than 10 GCs so we can get GCs from all of our domains involved? Right now only about 7 of our domains work properly because numerous GCs from Exchange's domain in its site are first used, then another few from the other domains. We can never get all 14 domains working correctly at any one time because of this. All of the previous workarounds, like you mentioned, typically break something else or cause unacceptable penalties.
Our TAM is in the middle of working on a design change request for us for exactly this issue. Thanks for any insite.
Will the reg key be automatically created with the necessary value, or does this just make Outlook check for it and it is still up to us to actually enable a value for the key?
We've got 14 domains and 30,000 + users. It will be a bit of a hassel to get the hotfix installed everywhere (although I'm thankful it now exists!). Is there any chance of making Exchange topology discoverer & DSAccess discover/use more than 10 GCs so we can get GCs from all of our domains involved? Right now only about 7 of our domains work properly because numerous GCs from Exchange's domain in its site are first used, then another few from the other domains. We can never get all 14 domains working correctly at any one time because of this. All of the previous workarounds, like you mentioned, typically break something else or cause unacceptable penalties.
Our TAM is in the middle of working on a design change request for us for exactly this issue. Thanks for any insite.