Thursday, March 29, 2018

Top 10 Lessons from Disasters in Identity Management


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.

Identiverse, Cloud Identity Summit

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.

I have enjoyed the Cloud Identity Summit every year I have attended, Vail, Napa, and Chicago. The family atmosphere is incredible. Each year it seems to grow. Lots of great content.

Andre Durand, CEO of Ping Identity, is always very approachable. His wife plans the family events. My kids have some great memories from the repelling, special trampoline, pool parties, story times, museum visits, and gondola rides.

Andre led off with a great keynote, talking about how someone invaded his hot tub at his vacation home. He even showed us video. With more to protect, just enough, just in time access is the key. Running, blocking and hiding are the instinctual first level of defense, but it isn't enough. Memory and habit is the next level, i.e. don't click on email links, but yet we must still reach further to intelligent reaction. Environmental awareness, to pattern recognition to avoid the threat in order to survive. Summing it up with Intelligent Identity equaling real time contextual authentication.
In the last two years they have added more content discussing actual implementations of different kinds of Identity Management technology, for example my friend Frank Drewes delivered a session on Identity Challenges to Office 365 deployment. I think that is very important.

To Farm or not to Farm Part 2

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.

This first point got me thinking and the last point now has me convinced that we shouldn't do Stand Alone on SharePoint 2013 Foundations or any other, because it adds the overhead of SQL Express when we can get better overall performance by using the real SQL Server, even if the SharePoint databases share it with all of the MIM databases. However, the patching issues brought up by Paul Williams are still real.

I think a lot of people have been sticking with the free option -- SharePoint Foundations 2013. Which is  possible to install on Windows Server 2016 even if it is not exactly supported. So a lot of folks have avoided thinking about SharePoint. Here are some points to consider
  1. The challenge has to do with the way MIM does its updates. If you separate MIM Service from the MIM Portal then you are better off when it comes to the MIM updates if you are in a multi-server farm.
  2. I have not seen any guidance from Microsoft Identity about what roles are needed in SharePoint 2016. However, it appears to me that the MIM solution is essentially a content farm which perMSFT would require 3 roles or 2 servers with shared roles, or the single server farm: Front End, Application and Distributed Cache.
  3. For Zero Downtime patching to apply you need to be in a Highly Available solution. With Min Role that takes 4 servers. Unfortunately, I don't know if that will allow you to update the MIM solution pack without downtime. One of the changes that the SharePoint team made is to keep stored procedures in the SharePoint databases backwards compatible. I don't think the MIM product group has made any such guarantees. So when we patch MIM Service it will update the database and the MIM Service. At that instant only updated MIM Service instances should talk to the database (they might work, but no guarantees), and only updated Portals should talk to the update MIM Service Instance. So I think we still end up with downtime, the key is to minimize it. The Zero downtime patching would certainly reduce it when you patch the actual SharePoint binaries. But we could accomplish the same thing with two single server farms load balanced through NLB.

Anyone else have any thoughts or experiences to share?
So for now, I recommend essentially a single server farm on SharePoint 2013 Foundations, and to use your own variant of Spencer Harbar's scripts to configure it. If you want to do that don't check this box:


For HA: deploy another one (be sure to use different database names) and then load balance.

SQL Server Management Studio SQL 2016

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.But what a surprise.

SharePoint Foundations 2013 -- Identity Extensions Installation error

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. It will. Take heart.

Finding my groove, again

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. Especially, thanks to my wife, kids, siblings, aunts, uncles, and cousins.

Last Saturday, one of my sisters was married, it was a beautiful but slightly sad moment for our family.

I am feeling a return to my usual high energy levels and am resuming blogging to help you, my friends, avoid the pains that I have endured and that I have seen others endure as we labor to implement Identity Management across the world.

I am also excited about some other projects that I will soon announce here and through other venues.

Well back to blogging about the technical stuff!

SharePoint Foundation 2013 IIS Configuration Error

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.

Should you encounter the following message:
Application Server Role, Web Server (IIS) Role: configuration error
If you click on Review the Log File and find this:

 - "C:\WINDOWS\system32\cscript.exe" "C:\WINDOWS\system32\iisext.vbs" /enext "ASP.NET v4.0.30319"
 - Install process returned (1)
- [In HRESULT format] (-2147024895)

 - Error when enabling ASP.NET v4.0.30319

Then the issue is you are missing some of the IIS Role Services -- specifically the IIS 6 Scripting Tools:
Yes this is a screenshot from my book. Yes, I clearly identify that you need these role services. So I must have made this mistake just out of the goodness of my heart in order to help anyone else.