Auteur de questions
We use MIIS for galsync and password sync.
I found we currently collect legacyEchangeDN value of contacts of all ExchangeOrgs to metaverse person object legacyEchangeDN(multi-value) .
Collected legacyExchangeDN values are all exported as X500 address of proxyaddresses of contacts and distributed to all ExchangeOrgs.
It looks for me very strange because X500 addresses of other ExchangeOrgs are all exported to contact objects and I think they does not need other ExchangeOrg's X500 address as proxyaddresses.
Is it standard way of galsync ?
dimanche 24 mars 2013 03:29
- Type modifié Markus VilcinskasMicrosoft employee, Owner vendredi 24 mai 2013 23:16
Toutes les réponses
The LegacyExchangeDN from the GalSync provisioned contacts needs to be added to the proxyaddresses of the source object so that mail routing between forest occurs correctly. this is the standard configuration
David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html
I understand writing collected legacyExchangeDN of contacts object to source object proxyadresses is default.
And we also are adding all collected legacyExchangeDN values to contacts object proxyaddresses in each ExchOrgs.
I thought also that we do not need to add X500addresses to all contact objects.
How do you think about that ?
- Modifié blackjack08 mardi 9 avril 2013 20:43