We're still running MIIS 2003 SP2 with multiple Exchange environments (some 2003, some pure 2007, some mixed).One of the pure Exchange 2007 environments runs the set-mailcontact ps script after MIIS syncs in new contacts. I see the update-recipient cmdlet was written specifically with MIIS/ILM in mind.But what is the actual difference (if any) between running set-mailcontact (with no options) versus running update-recipient?Is there any reason to recommend switching from set-mailcontact to update-recipient? Or do they do the same thing?Thanks for any insights into this!

For exchange 2007, ILM synchronization management agent creates the mail contacts. After that, agent needs Update-Recipient cmdlet to add the attributes required by Exchange 2007 to complete the provisioning of these contacts Set-MailContact cmdlet is used to modify the parameters of the existing mail-enabled contact

Thanks for yourreply James. I agree the documentation clearly indicates that set-mailcontact is used to modify existing mail-enabled contacts. It also appears that when set-mailcontact is used with no options against an object just created (not fully mail-enabled) by MIIS 2003it will mail-enable that objectjust as the Update-Recipient cmdlet does. From what I can tell, update-recipient is functionally equivalent to set-mailcontact with no options. So I'm not sure if there's any reason to use one over the other. Updated: One thing I do notice is that set-MailContact updates the msExchRecipientDisplayType attribute, where Update-Recipient doesn't. But both populate legacyExchangeDN and ShowInAddressBook.