By your description a "quick contact" is an Outlook-local contact. It's failing for the reason you note and, more importantly, will _never_ look to the server to re-resolve this address. Outlook contacts are locally-managed only; no server-side fix. Since there are so few re-create them properly on the server and continue to have users delete them as the problem comes up.
> On Sep 15, 2014, at 14:11, "Orlebeck, Geoffrey" <[email protected]> > wrote: > > All: > > We performed a migration where we took a domain that was previously hosted on > our company’s Exchange server (Company1.com) and migrated them to their own > AD/Exchange environment (company2.com). > > We migrated the x500 addresses from when Company 2 was on our network so > company2.com so users could reply/forward internal email (or use quick > contacts) without issue. The problem is that users in our Org (company1.com) > have quick contacts pointing to the x500 address information from when > company2.com was still hosted on our (company1.com) Exchange servers. Now > that Company 2 is “external” these emails fail (which we would expect). We > sent out an advisory email and whenever a user calls, we’ve shown them how to > delete the quick contact and add user from Global Address List (we have FIM > 2010 running GALSync) and emails work. > > There are only ~20 addresses for company2.com, so if we can manually update > the proxyAddress attribute or something else, that’s fine. But we’re a little > unsure on how to allow company1.com to accept the old x500 address and still > forward it out to company2.com > > Here’s the network details in case it helps: > *Exchange 2010 SP3 on both sides > *Two-way Forest trust established > *FIM 2010 running GALSync w/ Cross-Forest Delegation to sync GAL and allow > delegation w/in Outlook > *Both Forests are housed in our datacenter, so while they are separated, they > can be hit via internal IPs w/o traversing WAN > > Thank you for your time. > > -Geoff > > Confidentiality Notice: This is a transmission from Community Hospital of the > Monterey Peninsula. This message and any attached documents may be > confidential and contain information protected by state and federal medical > privacy statutes. They are intended only for the use of the addressee. If you > are not the intended recipient, any disclosure, copying, or distribution of > this information is strictly prohibited. If you received this transmission in > error, please accept our apologies and notify the sender. Thank you.
