none
Exchange 2010 provisioning via FIM 2010 RRS feed

  • Question

  • Experts,

    We are using FIM 2010 R2 for AD provisioning in our environment which is running completely fine. All provisioning is codeless and through outbound synch rule to AD.

    Now we want to enable exchange provisioning. I have been going through couple of links and getting one doubt.

    do I have to necessarily select 'Enable Metaverse Rule Extension' and select file 'Exch2010Extenstion.dll' although I am having codeless provisioning so far?

    Thanks,

    Mann

    Wednesday, February 4, 2015 3:15 PM

All replies

  • Hello,

    no MV Rules Extension in the wrong way.

    You have to enable Exchange provisioning on the last Management Agent tab.
    Enter the path to the remote powershell of Exchange: http://exchangeserver/PowerShell

    then at least let flow the following attributes:

    mailNickname

    msexchHomeserverName

    homeMDB

    (and mDBUseDefaults could be good also)

    You can of course add additional attributes for Exchange depending on your Needs.


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    • Proposed as answer by UNIFYBobMVP Monday, January 25, 2016 1:36 AM
    Wednesday, February 4, 2015 4:13 PM
  • I'd do it with this: http://blog.goverco.com/p/psmadownloads.html, way more controllable.

    • Proposed as answer by UNIFYBobMVP Monday, January 25, 2016 1:36 AM
    Thursday, February 5, 2015 4:53 AM
  • Did you get this sorted?

    Thursday, January 21, 2016 4:26 AM
  • Hello,

    no MV Rules Extension in the wrong way.

    You have to enable Exchange provisioning on the last Management Agent tab.
    Enter the path to the remote powershell of Exchange: http://exchangeserver/PowerShell

    then at least let flow the following attributes:

    mailNickname

    msexchHomeserverName

    homeMDB

    (and mDBUseDefaults could be good also)

    You can of course add additional attributes for Exchange depending on your Needs.


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    And it's possible in the rules to have a "roundrobin" balance of homeserver or database if you have multiple. 
    Thursday, January 21, 2016 10:08 AM
  • I too would avoid using the Exchange Provisioning tab of the AD MA ... it tends not to be flexible enough in a variety of real-world scenarios.  Far better to use PowerShell,

    This way it's no longer necessary to write your own "round robin" allocation model like we used to do in the early MIIS/ILM days.  These days far better to leave msexchHomeserverName and homeMDB blank and let Exchange allocate one randomly for you (it will do a better job).  The minimum the Exchange PowerShell commandlets require of you is to define the unique value for the -Alias parameter, and of course for you to specify the name of the CAS in the URI ... i.e. http://$ExchangeCAS/PowerShell/.

    If you don't want to use the PowerShell MA, then use a PowerShell script that can be run post-export to AD instead ... searching for user accounts which SHOULD have mailboxes but do not, and setting them ... e.g. with an LDAP filter like this:

    (&(objectCategory=user)(objectClass=user)(!msExchHomeServerName=*))


    Bob Bradley (FIMBob @ TheFIMTeam.com) ... now using FIM Event Broker for just-in-time delivery of FIM 2010 policy via the sync engine, and continuous compliance for FIM

    • Proposed as answer by UNIFYBobMVP Monday, January 25, 2016 1:35 AM
    Monday, January 25, 2016 1:35 AM