Great explanation. This really came in handy for t… Unknown - Jul 2, 2013Great explanation. This really came in handy for troubleshooting. I am so glad it was of use I am using MV extension to create users in AD from FIM. Need to flow password to AD which is any Random number say “$random123” This attribute flows to AD but can be viewed in account preview etc or the attribute value can be seen.
Many FIMsters wonder about the Metaverse and how works, how the data is stored. In this series I will reveal the secrets of the Metaverse. Parts 1-5 (links live but post yet to come) What is the Metaverse? How is the Metaverse data stored? Is there a limit to how many Metaverse attributes I can have? Has access to the metaverse gotten faster with recent releases? How do I safely query the metaverse?
Here is an update on the impact of the newly deprecated features: The big change is that XMA has caught up to Multi-Mastery and is tied for first. http://feeds.feedburner.com/IdentityLifecycleManagerilmBestPractices
Watch the presentation that James Booth (who worked with us on the project) and Joe Gasowski (DPDHL) gave at the Redmond Identity Summit 2013 about our project at DHL to replace the DPDHL Sun One Directory and deploy FIM to replace both CriticalPath and a home-grown admin portal. http://feeds.feedburner.com/IdentityLifecycleManagerilmBestPractices
Looks like ECMA1 deprecation has caught up to the … Ross - Feb 4, 2013Looks like ECMA1 deprecation has caught up to the equal precedence issue since you posted this. I think I’ll start offering some ECMA1->ECMA2 upgrade services. I suppose not everybody has an xMA developer in their back pocket!
I conducted a linkedIn poll to find out what others thought of the features that are deprecated starting in FIM 2010 R2 SP1. For the poll I only listed the ones I put in my top 5 list. With 15 votes and 1 abstention I thought it would be worthwhile to publish the results: Here we can see the winner: Multi-mastery/equal precedence (I had this 2nd) ECMA1 (XMA) (I had this third)
Remember that these features are still here but will be removed in a future version (probably the next major release or the one after) Feature Impact Unselect “allow nulls” for exported values You need to be more careful to ensure that you aren’t deleting values Web Service configuration interface You will no longer be able to send a request to the web service to update the mv-data or ma-data objects in order to configure the sync engine.
I have heard that investments in FIM CM are contin… David Lundell - Jan 2, 2013I have heard that investments in FIM CM are continuing. So don’t worry about FIM CM disappearing.
Yesterday Microsoft published a list of features that have been deprecated in FIM and will be removed from the product at some point in the future. In other words these don’t require immediate action but when the next major release of * Identity Manager (* because we don’t know what the new name will be – see my tweet from last week at the Redmond Identity Summit) emerges those features will likely be gone.
Hello, Is Fim r2 sp1 support sql server 2012 sp1 Unknown - Mar 2, 2015Hello, Is Fim r2 sp1 support sql server 2012 sp1
