be back to this page before long, selecting the attributes you want to appear in the Portal. See the Metaverse Designer tab in the Sync Service GUI for the configuration of the metaverse schema. We had to login to the server using the FIM Sync account (again FIM Sync, not FIM MA) and disable the proxy. On this page you map the Portal object type to an object type in the Metaverse. In fact, to learn about this interface the ILM and miis documentation will still be accurate. Filed under, fIM 2010, newbie. Note: this post was written for the RTM version of FIM 2010. This was pretty easy for me because everything was on the localhost. This turned out to be due to proxy settings. For some reason it was trying to connect to the fimservice database using the.
Again there should be nothing to configure on this page just click. On the Management Agent tab click. Create and then select the FIM Service Management Agent type from the dropdown. In this example I am blocking the two built-in Portal accounts. Im planning on managing users so I also select the Person object type here. Sync service account instead of the FIM MA service account. The error was Failed to retrieve the schema. We gave the Sync service account db_owner rights to the fimservice database and the problem went away. Otherwise the Server is the SQL server name, and the FIM Service base address should reference the sharepoint e service account is a regular domain account with no special permissions. Please check the specified database location, service host address, and acount information. Here you can block certain objects from being synchronized by the Sync Service.