Management agent configuration - selected containers
If you want to import users only from a specific container, you select only that container in the management agent configuration. But when a new container is created in AD (LDS), this container is automatically selected by FIM. Therefore, on the next import FIM will try to import objects from this new container, while only objects from the other container are desired in the metaverse. Is there an option to disable this default behavior?
June 28th, 2012 3:18am

I found out how FIM selects its containers. It depends on Include and Exclude rules. If the top container is selected as include, and you exclude specific containers, then new containers will automatically be selected, because the top container is included. You can check the list of rules when you configure containers and click the Advanced button. When you exclude the top container and include specific containers, new containers will only be selected if they are subcontainers of a selected container that had no sub containers before, or was included as a whole. In a nutshell: if you do not want that new containers are added automatically in the Management agent configuration, drill down to the lowest level of your hierarchy and only select on the lowest level the containers you want to include (all containers that contain sub-containers will be marked grey and are NOT checked). Only scenario remaining unsolved is a container that contains no sub-containers. If a sub-container is created and you do not want it to be selected, you have to change the management agent configuration by hand to exclude it. I see no way around this... Anyone else?
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2012 5:06am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics