My comments on What’s new and the release notes for FIM 2010 R2 SP1: Rank Feature Impact 1 Deferred evaluation of criteria based groups This setting can be enabled one group at a time. You can also change the default so that as new criteria based groups are created they will be set for Deferred. The default is to calculate group membership twice a day at 2:30 AM and 2:30 PM.
After re-reading my earlier post on this subject I decided I could be clearer. GUIDs are often used in three different formats: Representation Example Canonical form 8c4ac332-975f-4717-ad7b-ba4a4e968fff Octet String 32c34a8c5f971747ad7bba4a4e968fff Base64 Encoded MsNKjF+XF0ete7pKTpaP/w== Representation Comment Used in Canonical form This format stems from the way GUIDs (UUIDs) are generated. Each dash separating the various components. In version one of the UUID specification, the first the last component was the MAC address of the computer that generated the GUID.
On the eve of Thanksgiving I offer 5 reasons to be thankful for Identity Management (user provisioning, deprovisioning, group and role management, etc.): What other compliance project can actually have a positive ROI? You get improved compliance (and the ability to show it) You also get better security as accounts are disabled quickly Then you save money through the automation Identity Management can help support your corporate goals You can empower users to serve themselves with password resets, group/role requests It can help keep your organization out of the shame columns in the trade rags We have all read about the disgruntled former employee accessing data.
Today Microsoft announced the discontinuing or subsuming of many products in the Forefront line To be crystal clear Forefront Identity Manager (FIM) and Forefront Unified Access Gateway (UAG) live on as separate products with ongoing investment! Insert the obligatory Mark Twain quote here. “The rumors of my death have been greatly exaggerated” Product Fate Forefront Identity Manager (FIM) Lives on. R2 was just released in June Forefront Unified Access Gateway (UAG)
We have purchased to original copy, are we entitle… FMustafa - Sep 2, 2012We have purchased to original copy, are we entitled to get a free upgrade to R2 version?? This comment has been removed by the author. Any tentative date for print edition The print edition is already available. Just downloaded the EBook version from Lulu. Would love to see this available in a Kindle (or other e-reader) edition. At the very least, it would be nice to have the PDF re-published to Lulu with the table of contents feature turned on to make it easier to navigate.
Just this morning I have published the updated for R2 edition of FIM Best Practices Volume 1. Now called FIM R2 Best Practices Volume 1: Introduction, Architecture And Installation Of Forefront Identity Manager 2010 R2. The EBook edition is in color! Print Edition of FIM R2 Best Practices Volume 1 is still B/W Go to the lulu.com home page to get a coupon code for 20% off (offer expires 11:59 PM Sept 7 2012).
SO, where (or when !?) can we download that hotfix ? redarc coder - Nov 2, 2014SO, where (or when !?) can we download that hotfix ? So, where (or when !?) can we download that hotfix !?
On Aug 24th Microsoft released a new version of PCNS. Version number 4.1.2515.0. No release notes are provided with the download. However, this version number matches the version number of the latest FIM R2 hotfix rollup http://support.microsoft.com/kb/2734159 and it does tell us what is fixed: Assume that you run Password Change Notification Service (PCNS) setup together with the SCHEMAUPDATE=TRUE option and the schema is updated successfully. In this situation, an error message is displayed at the end of the setup process incorrectly.
In Part 1 of How to import the Domain attribute into the FIM Portal I provided you the simple technique for the single domain forest, and the technique that works although is a bit unwieldy – that of looking at the first 41 characters of the object’s SID and using a lookup table through nested IIF statements and this doesn’t . What if there was a simpler way? What about using the Domain Component option in the attribute flow?
If you have a single domain forest then you should use a constant flow in your sync rule or advanced attribute flow. If you have a multi-domain forest, then using a constant in the advanced attribute flow won’t work. You could create multiple inbound sync rules one for each domain with scoping filters and then use a constant. However, this seems like a waste. You could also follow the guidance provided in article originated by my friend Markus Vilcinskas and maintained by the community http://social.
