I have a customer that is currently running MIIS 2003. I am trying to scope the effort I need to migrate from MIIS 2003 to FIM 2010. One of their directories is OpenLDAP Directoy. The MA used to communicate with the openLDAP is an extensible MA downloaded from http://sourceforge.net/projects/openldap-xma/ I am not sure what I need to do to replace/upgrade their OpenLDAP xma. Any help to explain what is needed to use OpenLDAP XMA in FIM 2010 is greatly appreciated. Is there is any plan to add OpenLDAP MA to FIM in the future? Issam Andoni

The Exensible MA architecture really hasn't changed. So there is unlikely to be any problems there although I've not tested it specifically. The only tick I notieced on doing test upgrades was that you will need to rename the existing MicrosoftIdeneityIntegrationServer database to FIMSynchronizationService when you upgrade/restore the database. Eric

I try to install OpenLDAP that is referenced above but the MSI provided with it simply did not run because it did not detect MIIS. It seems the installation is looking for MIIS in specific. Based on that it seems I need to open the source code and adjust it by removing any reference to MIIS and replace it with FIM before I re-build. I am not sure if that all what I need to do. Issam

Likely the install isn't doing much. There should be a DLL in the extensions directory that the current OpenLDAP MA is pointing at and that should be it unless there are other client components that I'm not aware of. There are a couple of ways to trap what the MSI is doing if it is more than that. As always, test.. :-)Eric

In the techNet Webcast: Forefront Identity Manager 2010: Deploying FIM Brjann Brekkan (the presenter) said that all MAs configuration and code is included in the SQL database and thus after you point the installation to use existing database you should be done and the most you need to do is copy needed DLLs to the right place. Yours Eihab Isaac

there are two scenarios here: 1. OpenLDAP XMA is installed on ILM, then ILM gets upgraded to FIM In this scenario the upgrade process should result in an OpenLDAP XMA that runs on FIM. 2. Installing the OpenLDAP XMA from scratch on FIM probably has the following issues: a. The install program fails when it can't find ILM, needs to look for FIM b. The XMA won't build because it references Microsoft.MetadirectoryServices.DLL, needs to reference Microsoft.MetadirectoryServicesEx.DLL CraigMartin Edgile, Inc. http://identitytrench.com

Craig, My inquiry is related to the first scenarios where I have openLDAP XMA already installed on MIIS 2003. I am going to replace MIIS 2003 with FIM 2010. My replacement method is to copy the database to the new server (the FIM 2010 server) then point to it during FIM 2010 sync engine installation. My question is to make sure that such action will result with FIM server that has OpenLDAP XMA and if I need to do anything beyond that such as copying any dll to the new server Issam

Yup, that should work thanks to the upgrade process during the FIM installation. If you encounter problems feel free to take this offline with me then we can report back to this thread.CraigMartin Edgile, Inc. http://identitytrench.com

Hello everyone, Issam and Craig, I am facing the same issue and it is a new FIM installation (no upgrade): I have FIM installed, and the openLDAP XAM installer does not run. I'll try to find a solution and look at the code. Any update on this issue? Thanks Jérémie

I am preparing for an FIM 2010 implementation that includes syncronization of openldap to AD, and if this doesn't work properly, I'll need to use ILM. Is there a known, TESTED and Microsoft approved fix (with steps for those of us like me who don't know how to code)?Or should I use ILM 2007 because it works now, and FIM 2010 doesn't?

OpenLDAP MA is an open source project that I believe was sponsored by Microsoft in 2005/2006 but they don't have any responsibility to support, test or approve it. Currently this project is maintained by amongst others MVP Craig Martin and since it's open source he has no responsibility to do it either.I would love someone to make this project available to FIM implementers since there's still a demand for it. The question is if the demand is enough and is anyone willing to spend the time (or the money) to make it FIM ready?Henrik Nilsson, ILM/FIM MVP Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

I think we need to go a little further with this thread.1. What version of MIIS ? SP1, SP2?2. There could possibly be 2 different versions... .Net 1.1 or .Net 2.0 a. If it's .Net 1.1, I couldn't upgrade the old code, I would download the newer version and Upgrade it using Visual Studio 2008 Should be pretty painless. The old .Net 1.1 LDAP Api made calls to unmanaged code and I really would stay away from upgrading this.. Not worth the effort and the headaches it could cause. The newer .Net 2.0 version uses System.DirectoryServices.Protocols namespace which is now native calls and not unmanaged. b. Run the code under Visual Studio 2008 and it will ask you to automatically upgrade it... There could be a couple issues as I haven't done this.. I have my own ma's that i use. But shouldn't be too bad. Good Luck.Joe Stepongzi - Identity Management Consultant - ILM MVP - www.microsoftIdM.com,ilmXframework.codeplex.com