Differences between Update-Recipient cmdlet in Exchange 2007 and 2010
Those of you that do a lot of Exchange provisioning based on ILM/FIM or other solutions should find this piece of information useful.
Unlike the Update-Recipient cmdlet in Exchange 2007, the one included with Exchange 2010 has more strict requirements before it can change an Active Directory user object to an Exchange 2010 mailbox-enabled object.
In order to convert an Active Directory user to a Mailbox-enabled user, the Exchange 2007 version of the Update-Recipient cmdlet only required the following attributes set on the object:
- Either msExchHomeServerName, homeMDB, ord homeMTA
Now with Exchange 2010, the cmdlet requires the following three attributes:
Good to know if/when you run into issues provisioning Exchange 2010 objects 🙂
Thanks to Ian Liu (Program Manager in the Exchange Product group) for helping me out with issues that were related to these missing attributes.
MCM: Exchange 2007 | MVP: Exchange Architecture