none
MIM partitions and customization RRS feed

  • Question

  • Hello,

    I am using MIM 2016 SP1. My dev environment is a single partition while the production environment has two partitions. After migration from Dev to Prod some of the custom attributes bound to the User object show on one partition and not the other. I found the missing attributes by querying users by ID using powershell. The result of the query on one server showed the attributes while the other server didn't.

    The architecture

    MIM portal behind NLB and MIM Service is behind NLB with a sticky source configuration. Both partition connected to one DB. 

    Do I need to do anything special when migrating to multi-partition environment?


    Ahmed is an independent consultant in Ottawa, Canada specialized in .NET, Biztalk, WCF, WPF, TFS and other Microsoft technologies.

    Blog: http://lajak.wordpress.com

    Twitter: ahmedalasaad

    Monday, March 30, 2020 5:57 PM

Answers

  • Restart services

    Nosh Mernacaj, Identity Management Specialist

    Tuesday, March 31, 2020 1:11 AM
  • Hi,

    A restart of the services as Nosh said should refresh the schema Service wise.

    You don't state which PowerShell library you use, but if it's LithNet PowerShell, it caches the schema in memory. So -RefreshSchema would refresh the schema (or restarting the PowerShell console).

    Br,

    Leo


    Did my post help? Please use "Mark as answer" or "Propose as answer". Thank you!

    Wednesday, April 1, 2020 7:36 AM

All replies

  • Restart services

    Nosh Mernacaj, Identity Management Specialist

    Tuesday, March 31, 2020 1:11 AM
  • Restarting FIM service didn't help. Retrieving a user by Id returned the user object without the new attributes.

    I then called the service with -RefreshSchema option and that fixed the issue.

    Just curious, how MIM service caches the schema?


    Ahmed is an independent consultant in Ottawa, Canada specialized in .NET, Biztalk, WCF, WPF, TFS and other Microsoft technologies.

    Blog: http://lajak.wordpress.com

    Twitter: ahmedalasaad

    Tuesday, March 31, 2020 10:24 PM
  • Hi,

    A restart of the services as Nosh said should refresh the schema Service wise.

    You don't state which PowerShell library you use, but if it's LithNet PowerShell, it caches the schema in memory. So -RefreshSchema would refresh the schema (or restarting the PowerShell console).

    Br,

    Leo


    Did my post help? Please use "Mark as answer" or "Propose as answer". Thank you!

    Wednesday, April 1, 2020 7:36 AM
  • I was using Lithnet. Thanks both for your help

    Ahmed is an independent consultant in Ottawa, Canada specialized in .NET, Biztalk, WCF, WPF, TFS and other Microsoft technologies.

    Blog: http://lajak.wordpress.com

    Twitter: ahmedalasaad

    Thursday, April 2, 2020 5:04 PM