As mentioned by Ross Currie, you need a shortcut to this, as you keep losing this little gem…
Announcing the public availability of the MIMWAL project, now available as an Open Source Project on GitHub.
The MIMWAL is a Workflow Activity Library (WAL) for building complex workflows in the Microsoft Identity Manager (MIM) 2016 and Forefront Identity Manager (FIM) 2010 R2 solution.
The WAL is a powerful solution accelerator for MIM / FIM that provides foundational activities which can be combined to create complex workflows to implement business processes within a MIM / FIM solution simply by configuration instead of coding for days and months.
- Building-block Workflow Activities
- Conditional Execution Capability for Building-block Activities
- Support for Iteration Over a Collection of Values in Building-block Activities
- Deep Resolution Capability for FIM Lookup Grammar
- Rich Library of Workflow Functions
- UI Framework for Building Additional Custom Workflow Activities
- Support for ETW Event Tracing
- Optimization of Update Requests
- Combining multiple updates into a single request per resource per activity
- Issuing update request only when resource is actually modified.
Please visit the MIMWAL site at http://aka.ms/MIMWAL for information on project source code, releases and documentation, and discussion forums.
Please post any questions or discussions about the MIMWAL project on this forum, which can also be found at http://aka.ms/MIMWAL/Forum
Question: What’s the difference between Microsoft.MetadirectoryServices.dll and Microsoft.MetadirectoryServicesEx.dll?
MIIS/ILM code is using the Microsoft.MetadirectoryServices.dll, while FIM is using Microsoft.MetadirectoryServicesEx.dll.
Can the old DLL be removed from the FIM code extensions, when the new DLL is referenced in code?
You should use the Ex.dll when possible. The other DLL is only there in case you have a DLL from MIIS, has lost the sources, and cannot recompile it. The only difference between the two is that Ex is digitally signed and the other is not. When you have changed the references to Ex.dll you will not need the other.
[non-Dutch speaking audience, look the other way for a short moment… or skip to the last paragraph]
Voor de Nederlandstalige spelfanaten: de kinderen kregen voor afgelopen Kerst het spel Relic Runners cadeau.
Na enige navraag, blijkt dat hiervan de Nederlandse vertaling nog niet bestond.
Wat wel zonde is, want het is een erg leuk spel.
En er zitten een aantal leuke addertjes onder het gras in de spelregels van Relic Runners.
Dus om de pret te delen, heb ik dan maar zelf de spelregels vertaald.
Voor de Nederlandstalige fans van het Relic Runners bord spel. Je kan de integrale Nederlandse vertaling van de spelregels van Relic Runners vinden om m’n OneDrive: http://1drv.ms/1JTXrnL.
Gepubliceerd met toestemming van Days of Wonder
Days of Wonder, the days of Wonder logo en Relic Runners – het bordspel zijn allemaal handelsmerken of geregistreerde handelsmerken van Days Of Wonder, Inc. en copyrights © 2013 Days of Wonder, Inc. All Rights reserved. Symbols & Graphics Copyright © 2004-2016 Days of Wonder, Inc. Produced with permission of Days of Wonder, for non-commercial use only.
For the Dutch speaking fans of the Relic Runners board game, use the OneDrive link above to download the translated (into Dutch) version of the game rules of Relic Runners.
Published with the permission of Days of Wonder
Days of Wonder, the Days of Wonder logo and Relic Runners – the boardgame are all trademarks or registered trademarks of Days of Wonder, Inc. and copyrights
© 2013-2015 Days of Wonder, Inc. All Rights reserved. All Rights reserved. Symbols & Graphics Copyright © 2004-2016 Days of Wonder, Inc. Produced with permission of Days of Wonder, for non-commercial use only.
Please note that Andreas Kjellman published/updated the information on the Generic SQL connector for FIM/MIM
As described on the tech page:
“This article describes the Generic SQL Connector. The article applies to the following products:
- Microsoft Identity Manager 2016 (MIM2016)
- Forefront Identity Manager 2010 R2 (FIM2010R2)
- Must use hotfix 4.1.3461.0 or later KB2870703.
For MIM2016 and FIM2010R2 the Connector is available as a download from the Microsoft Download Center.
The Connector is supported with all 64-bit ODBC drivers. It has been tested with the following:
- Microsoft SQL Server & SQL Azure
- IBM DB2 10.x
- IBM DB2 9.x
- Oracle 10 & 11g
- MySQL 5.x
You might have some trouble to get to the download link, if so : keep an eye on it and retry later. The download will be activated any time soon…
Since the addition of the FIM Service and Portal in FIM 2010, the licensing model changed from a “server only” licensing to “server + CAL” licensing. (NOTE: CAL = Client Access License).
In April 2015 licensing update of FIM/MIM, the server license became virtually free.
The authoritative document that provides you with the full details is the PUR (Products Use Rights) document published by Microsoft.
See my post on the licensing change for all required info: http://aka.ms/LicenseToCAL. It does contain the links to the PUR (in various languages).
You can also check the TechNet Wiki page for the FIM/MIM licensing: http://aka.ms/LicenseToFIM)
In short: in general, you do NOT need to buy a FIM/MIM server license anymore, it’s included in the Windows Server license.
Still, keep in mind, some specific situations do require special/additional licenses: check the PUR.
You DO require CALs, which is mentioned by the PUR as:
“A CAL is also required for any person for whom the software issues or manages identity information.”
You can acquire FIM CALs via :
- Forefront Identity Manager 2010 R2 User CAL (device CALs are not available), or
- Enterprise Mobility Suite User SL, or
- Microsoft Azure Active Directory Premium
The april 2015 licensing change caused quite some confusion on the CAL requirements (as the FIM/MIM server license became ‘free’…)
One of the important reasons was the following paragraph in the PUR (quote):
A CAL is not required for users only using the Forefront Identity Manager synchronization service. /../”
To rephrase this statement: if you ONLY use the FIM Sync engine, you DO NOT need to buy/acquire any license (you got server license free and CAL not required).
This essentially means that IF you do install the FIM Service (and probably the FIM portal to manage it) and you DO connect the FIM Sync engine to the FIM service via the FIM MA, you DO NEED CALs.
This also applies to BHOLD and FIMCM.
This is how it was phrased by one of the FIM/MIM/AADConnect program managers: “As soon as you have installed the FIM Service MA (or BHOLD or CM) then you have triggered a CAL for everyone in the MV. ” It’s not relevant if the users are in FIM Service or not.
This is also the reason for built-in declarative provisioning (without a need for the FIM Service MA) in Azure AD Connect sync… this puts the FIM/MIM licensing model on the same frequency as the Azure AD connect licensing.
Now, this perfectly answers the question of Henrik on my post on the licensing update.
His question was: “What if you install FIM/MIM Sync and Service, both included in Windows Server licensing but you choose not to add object mappings in FIM/MIM MA for users and groups… This will allow you to import filter based sync rules from FIM/MIM Service.”
The short answer is: you still need to acquire the CAL.
- FIM/MIM server license is included in the Windows Server License
- you DO NEED CALs for FIM/MIM
- you can purchase CALS or acquire them via EMS/AAD premium/ECS
- for EVERY person managed
- 1 EXCEPTION:
- if you ONLY use the FIM/MIM Sync Engine, you do not need CALs
I hope that this explanation helps you to better understand the FIM/MIM licensing.
Feel free to contact me via any channel if you have any feedback or questions.