FIMBob
MVP Awardee 2012-2017 (FIM/MIM/EMS)
Microsoft Community Contributor
My Company
-
Recent Posts
Blogroll
Archives
- May 2023
- April 2020
- July 2018
- February 2018
- January 2018
- March 2017
- February 2017
- January 2017
- September 2016
- August 2016
- June 2016
- April 2016
- March 2016
- February 2016
- August 2015
- June 2015
- April 2015
- December 2014
- September 2014
- July 2014
- June 2014
- April 2014
- January 2014
- November 2013
- September 2013
- July 2013
- June 2013
- April 2013
- March 2013
- February 2013
- December 2012
- October 2012
- September 2012
- July 2012
- June 2012
- May 2012
- January 2012
- November 2009
- September 2009
- July 2009
- June 2009
- February 2009
- January 2009
Categories
- Access Governance
- Active Directory
- Azure Active Directory
- Azure AD Connect Sync
- Event Broker for FIM 2010
- FIM (ForeFront Identity Manager) 2010
- HyperSync Panel
- Identity Lifecycle
- Identity Panel
- ILM (Identity Lifecycle Manager) 2007
- Microsoft Entra
- MIM (Microsoft Identity Manager) 2016
- SSPR
- Uncategorized
- UNIFY Broker PLUS
- Windows AzMan
- XML Programming
Meta
Category Archives: FIM (ForeFront Identity Manager) 2010
Simple #MIM2016 Reporting in PowerShell
As a veteran MIM implementer now, I can’t help being constantly impressed with how much Ryan Newington‘s work on his Lithnet Github site has changed the landscape for those of us continually faced with the task of extracting data from the … Continue reading
Upgrading #FIM2010 (not R2) to #MIM2016
Some time ago former FIM MVP Thomas Vuylsteke blogged this really helpful post on the above subject. I figure my customer isn’t the only one stuck in a pre-R2 limbo as we barrel towards the October 2017 FIM 2010 EOL … Continue reading
Your #MIM2016 or #FIM2010 Starter Pack
With all the excitement this week of the announcement of the Azure AD and SailPoint collaboration, it got me thinking about how the Microsoft IAM landscape is continuing to evolve both on premises and in the Microsoft cloud. The message … Continue reading
Azure EMS Conditional Access and Enterprise IAM
This week part 2 of a series of blog posts on implementing Azure EMS Conditional Access (CA – part 1 here) was published on Microsoft’s Enterprise Mobility and Security Blog. Predictably, perhaps, this got me thinking about what I might … Continue reading
Managing Office 365 Licenses with #MIM2016 and #AzMan – Part 2
In my last post I introduced the concept of using Windows Authorisation Manager (AzMan) to manage the automation of Office 365 licenses. In this post I will go into detail on how the solution hangs together. Complementing AAD Connect with … Continue reading
Managing Office 365 Licenses with #MIM2016 and #AzMan – Part 1
One of the things we Microsoft FIM/MIM folks find ourselves doing of late is having to find ways of automating Office 365 license assignment for our “hybrid” (AD+AAD) customers, initially as part of provision the initial Exchange Online mailbox which … Continue reading
Building in #MIM2016 Solution Resilience
Disasters can happen for all sorts of reasons, and when we’re automating we risk large-scale mishaps. What sort of precautions do you take to disaster-proof (or at least contain) your IAM solution? Continue reading
Using .Where instead of | Where-Object
I’ve been fighting a problem today whereby the PowerShell Where-Object commandlet was returning results of varying object types from the same XML document. Specifically, when trying to check for the numbers of adds/deletes/updates from a CSExport xml file, where I had … Continue reading
Using -ReadCount 0 with Get-Content
Not that I’m an expert in PowerShell by any means, but here’s my tip of the day … use the -ReadCount parameter with Get-Content! From the Get-Content page on TechNet … -ReadCount<Int64> Specifies how many lines of content are sent through the pipeline … Continue reading
#FIM2010 MIISActivate – FIM Sync service terminated with service-specific error %%-2146234334
Originally posted on Identity Underground:
This article has been posted on TNWiki at: FIM2010 Troubleshooting: MIISActivate – FIM Sync service terminated with service-specific error %%-2146234334. ? Situation ? Failing over a FIM Sync Server to the standby FIM sync server…
You must be logged in to post a comment.