Can a user account and its mailbox be disconnected from each other by setting homeMDB to Null? I am looking to achieve the same effect in FIM as running DISABLE-MAILBOX powershell cmd in E2K10. Anu

Setting the HomeMDB to null does disconnect the mailbox and starts the timer on the retention period after which it will be deleted. However, it does not remove all of the other exchange attributes. See here for a list of attributes that were removed in Exchange 2003 days (list is still similar) http://msexchangeteam.com/archive/2006/10/13/429192.aspx As to why it matters consider the following gentleman's issue: http://www.telnetport25.com/component/content/article/1-exchange-2007-gen/315-forcing-the-removal-of-exchange-attributes-on-a-directory-user-the-removeexchangeatributes-tool.html He had AD users with Exchange attributes populated (they had once had mailboxes) and he could not create mailboxes for them because they still had some of their exchange attributes populated. (I don't know which ones cause this problem).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

Thanks, David. It is interesting to see what kind of Exchange support the future releases of FIM will provide. There is so much more support in powershell for AD objects than in FIM for example changing states for a user to mailuser to usermailbox to contact etc. as well as providing the ability to modify AD attributes on user. As for mailbox disconnects you confirmed what I had suspected. When I tried using FIM for the purpose I ended up with users with missing homeMDB but still seen as usermailboxes and some with exchange attributes but no mailbox attached. Anu