I watched through SQL Profiler to better understand what these checks do, and I found an error with check #10. It says it is “Checking Lineage Guid table for MV objects with invalid MV object ids” but the SQL query it issues is the same as the query for Check # 9 “Checking Lineage Date table for MV objects with invalid MV object ids.” It queries the Lineate Date table instead of the Lineage GUID table like it says.
On occasion you (usually with the help of PSS – Product Support Services) may need to verify the integrity of the MIM Synchronization Service Database. To do this you can use the Store Check tool, StoreChk.exe located in the bin folder under the root of your MIM Synchronization install. While the storechk tool does read the registry to find the name of the database (almost always is FIMSynchronizationService) it does not read the Server or Instance name registry values in the parameters key of the registry.
Image from: https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-overview Edited July 2 2022 after reviewing my Facebook discussion with Eugene Sergeev on Microsoft’s product team. MIM 2016 SP2 (and 4.4.1459.0 or later supports SQL Server Always On Availability Groups (AG))! Yeah! Ok let’s implement it! But wait! It won’t give us all we hope for! Up to the moment distributed backup of the data – yes! Automatic instant failover – not without a huge caveat! What do you mean it won’t give us Automatic Instant Failover?
SharePoint is a great product but I wish that FIM and MIM did not use it. In my opinion, it adds unnecessary infrastructure and really complicates the setup, because SharePoint must be installed and configured (and maintained). Leaving that aside, allow me to point out some gotchas that might impede your ability to install this MIM/FIM prerequisite. First up: if your server has limited access to the Internet you should probably download all of these prerequisites and copy them to the server – because that’s what the SharePoint Installer has to do – it doesn’t include these items.
JefTek created a niche hybrid tool that tackles a few pieces of the sync and service puzzle in a way that none of the others do. One noteable one for sync: Get and Export MIM Deltas to CSV (based on a drop file either stop and drop or the audit log dropped during the export It is great for setting up SharePoint and the Kerberos authentication to it. While it doesn’t do all that IS4U-FIM-PowerShell (see my review), does or Lithnext resourcemanagement-powershell or Lithnet-miis-powershell (see my review), or even the he FIM PowerShell Module (see my review), it fills a small niche that none of the rest of them do.
Gil Kirkpatrick (a great guy, fellow MVP, who has taught me a lot over the years) created one of the very first, if not the first, PowerShell commandlets libraries to manage FIM/MIM service. It hasn’t had any activity in years, but it served as a great example to get others going. If you like this simple approach you could check out Adam Weigert’s PowerShell for FIM 2010 (see my review).
Wim Beck’s IS4U-FIM-PowerShell is a great example of open source, in that he has built on top of the FIM PowerShell Module (see my review). This is what Open Source is about, building upon each other’s contributions to make great stuff! When I looked at it in Dec 2016 I almost dismissed it since it lacked a wiki, but since then Wim has added a lot of pages. They still lack examples, I plan on pitching in to help out with that by adding some examples to my fork and then asking Wim to pull it in.
Ryan Newington’s Lithnet consists of several items: miis-powershell resourcemanagement-powershell resourcemanagement-webservice googleapps-managementagent acma “Codeless business rules engine for FIM/MIM” umare “Codeless data transform engine for FIM/MIM” I will only review the items I know Managing Sync miis-powershell is amazing it can almost everything you can do through the UI. For example, Clear-FullSyncWarning and it has a great wiki.
PowerShell for FIM 2010 by Adam Weigert consists of three parts but I further break the last into two: Management Agent(MA) and MetaVerse (MV) Extensions that let you run PowerShell scripts as your extensions A Workflow Activity A PowerShell module Managing Sync Managing Service Management Agent(MA) and MetaVerse (MV) Extensions The work done to enable you to write PowerShell scripts to be MA and MV extensions is crazy brilliant.
The FIM PowerShell Module (started by Craig Martin and now updated most frequently by Brian Desmond) is a great set of commandlets that help you to automate Interactions with FIM Service and FIM Sync Service. Managing Sync This library is great for automating tests. This library and Ryan Newington’s Lithnet-Miis-PowerShell (see my review on LithNet) are very complimentary. You can retrieve CS Objects, Run History, start an MA. I found that the most interesting Sync related Cmdlets are the
