Thanks JoeK.
I was simply going to say to OP, try it and find out on your own, maybe it will
work for you. If not, take my original post and sit down and say he told me so.
Exchange has pathetically bad documentation so you can't point at much and say,
see it says it here other than where it tells you setting your own values in AD
isn't supported unless using CDOEXM to do it. Instead they try to rely on the
GUI admin tools enforcing rules. This obviously doesn't work as well as it used
to because now instead of Exchange admins who only know the GUI, you now have a
bunch of AD admins who know how to script LDAP.
My "real job" involves working on very large enterprise Exchange deployments and
Active Directories. I am talking 100,000 users and up. I have been doing this
now for a year and prior to that I helped design and implement and support an
AD/Exchange environment for a Fortune 5 company with about 250,000 users which,
right now, is running at 5 nines W/O clustering.
Duplicates in the proxyaddresses attribute of any type are BAD. Period. Actually
any garbage in the Exchange attributes in AD is BAD. I have seen huge company
email systems grind to a halt to do seemingly stupid little data issues. This is
why, again, the only supported programmatic mechanism for updating the Exchange
values is CDOEXM and even that doesn't catch everything.
When in doubt, a quick check is to try and do something in the GUI and see if it
will let you. If it won't, you need to actually understand what is happening
prior to overriding it and just jamming shit in the directory.
joe
