I have spent this week in Munich Germany, where it has been mostly cloudy, lots of rain, and a little thunder. I have seen a number of familiar faces to those who attended Directory Experts conference: Pamela Dingle, Alex Simons, Alex Weinert, Jackson Shaw, Jonathan Sander, Kim Cameron, and others. Also a lot of faces familiar to those who have attended Cloud Identity Summits: Andrew Hindle, Colin Wallis, Steve Hutchinson, Eve Maler, and Ian Glazer and fellow Microsoft MVP: Naohiro Fujie.
Working on a customer’s lab and look what I found. They had created (through some other process) two user accounts for the same user, and the samAccountName was nearly identical, just a space, ascii 32, appended to the end of one of the samAccountNames differentiates the two. Apparently, AD allows this. The account with the space was projected into the Metaverse, and then later in the sync the account without the space attempted to join, and it matched.
I will speak at Kuppinger Cole’s European Identity Conference on Top 10 Lessons from Disasters in Identity Management in May in Munich. With great automation capability comes great responsibility! Come discuss and learn vital lessons gleaned from disasters in Identity Management. So if you would like your disaster story to be considered for inclusion let me know. I would love to add to the stories. This will be a fun interactive session.
Last summer I attended and spoke at the Cloud Identity Summit in Chicago. First big news: it was renamed to Identiverse and 2018 will be in Boston. As a consultant I have limited time to attend conferences and speak. So conferences have to be great. I do love this one, but in the interest of time, I will be skipping it this year in favor of speaking at the European Identity Conference in May 2018 in Munich, Germany.
In the original To Farm or Not to Farm post I discussed the pros and cons of setting up FIM on a SharePoint farm or using Stand Alone. Well we now have SharePoint 2016 and it isn’t possible to install Stand Alone, although you can do a single server farm. Also, absolutely everything is virtualized and so we tend to share lots and lots of processing so we can’t really think of a server as having spare cycles, because we share those processors with lots of other VM’s.
So I went to install SQL 2016 on a server (been using it for a while, I get vm’s on CloudShare where SQL is preinstallled, so first time installing it for myself) – no problem. Hey, where is SQL Management Studio (SSMS)? Well it isn’t include in the 2.6 GB SQL Server ISO. You have to download it separately. 800 MB. All I can say is You’re Welcome! I get why they did it – they can update SSMS much more often etc.
As you install SharePoint 2013 Foundations pre-reqs if you encounter “Microsoft Identity Extensions Installation error” and then when you install it manually you might encounter “Installation of Microsoft Identity Extensions requires Windows Identity Foundation v1.0 to be installed” Then when you go to install WIF through the Server Manager you realize that it is WIF 3.5 rather than WIF 1.0 and you think hmm… maybe that will work.
In 2017 and the beginning of 2018 I have had some rough times. The Long and the Short of it is that late last year my mother passed away in the hospital. Then early this year, my father died, probably of a broken heart. Thanks to many friends from church, our neighborhood, professionally, other Microsoft MVP’s, I have had a lot of support while mourning their temporary absence from my life.
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.
As most of you know I am regarded as one of the SQL gurus among the Microsoft Identity Management Gurus. For years, in my book and in speaking I have been recommending Ola Hallengren’s SQL Maintenance Solution to help take care of your ILM/FIM/MIM databases. But the SQL Maintenance Plan Wizard has come a long way. Tomorrow morning at 10 AM at Grand Canyon University I will be presenting as part of SQL Saturday #726 a showdown between the SQL Maintenance Plan Wizard and Ola’s solution, discussing when you want to use one vs the other.