none
About a user's Compatibility RRS feed

  • Question

  • User ID is synchronized from SQLServer to AD using the following sites. 
    http://technet.microsoft.com/en-us/library/cc720671(v=ws.10).aspx

    When it processes according to the following procedures 
    It will become impossible to take the compatibility of user information. 

    <Process>
     1.FIMServer backup
     2.userA add to SQLServer. 
     3.Synchronous processing is performed. 
     4.userA is added to AD. 
     5.FIMServer restore

    <This timing>
      SQLServer :userA exist
      SQLCS     :userA nothing
      MV        :userA nothing
      ADMA      :userA nothing
      AD        :userA exist


    profile is performed in order of the following. 
     1.SQLMA(Full Import)
     2.ADMA(Full Import)
     3.SQLMA(Full Synchronization)
     4.ADMA(Export)

    But An error occurs.-> 3.SQLMA(Full Synchronization)

    Since a user already exists on AD, an error occurs. 
    If there is a point which should be improved, please let me know.

    It will be saved if the advice 
    Please help me. 

    Wednesday, November 7, 2012 10:09 AM

Answers

  • See this, if you haven't already http://social.technet.microsoft.com/wiki/contents/articles/2253.aspx

    It seems you have incomplete joins, so follow the steps provided

    "To fix an incomplete join problem in your environment, you should:
    1. Disable provisioning.
    2. Run synchronization on the Fabrikam FIMMA to bring Britta Simon into the metaverse.
    3. Run synchronization on the Fabrikam ADDSMA to join Britta Simon with the related object in the metaverse.
    4. Enable provisioning. "

    • Marked as answer by 梅崎 Wednesday, January 23, 2013 11:29 AM
    Thursday, November 8, 2012 3:00 PM

All replies

  • See this, if you haven't already http://social.technet.microsoft.com/wiki/contents/articles/2253.aspx

    It seems you have incomplete joins, so follow the steps provided

    "To fix an incomplete join problem in your environment, you should:
    1. Disable provisioning.
    2. Run synchronization on the Fabrikam FIMMA to bring Britta Simon into the metaverse.
    3. Run synchronization on the Fabrikam ADDSMA to join Britta Simon with the related object in the metaverse.
    4. Enable provisioning. "

    • Marked as answer by 梅崎 Wednesday, January 23, 2013 11:29 AM
    Thursday, November 8, 2012 3:00 PM
  • Thank you very much Gaston!!
    The following procedures were tried. 

    1.ADMA Modify
    ADMA>Configure Join and Projection Rules>user
     mapping group:samaccounname
     action:Direct
     Metaverse Object Type:samaccountname

    2.Identity Manager>Tools>Options>Enable Provisioning Rules Extension 
     The check box was turned OFF. 

    3.SQLMA-FullImport run
    4.ADMA-FullImport run
    5.SQLMA-FullSync run
    6.ADMA-FullSync run

    7.Identity Manager>Tools>Options>Enable Provisioning Rules Extension 
     The check box was turned ON.

    8.SQLMA-FullImport run
    9.ADMA-FullImport run
    10.SQLMA-FullSync run
    11.ADMA-Export run

    It operated normally. 


    But I cannot understand why a [Join] setup must be performed. 
    I am very glad if it teaches. 

    Thank you verymuch!!
    Saturday, November 10, 2012 2:16 PM