1. Max Fritz Senior Systems Consultant, Now Micro
Using Microsoft Identity Manager with SharePoint 2016 to fill the UPS Gap
Max Fritz
Senior Systems Consultant, Now Micro
@theCloudSherpa

2. Thank You Sponsors for participating in SPS St. Louis 2017!
You can use the hashtag #SPSSTL & follow Gold Sponsors Silver Sponsors

3. Max Fritz
Senior Consultant MCSA Office 365, MCSE Productivity Working with Office 365 for over 5 years Specialize in the Education Industry Focus in Azure AD, Exchange, and SharePoint Online
Contact Details
Twitter Blog: maxafritz.com LinkedIn : in/maxafritz

4. Max Fritz
Senior Consultant MCSA Office 365, MCSE Productivity Working with Office 365 for over 5 years Specialize in the Education Industry Focus in Azure AD, Exchange, and SharePoint Online
Contact Details
Twitter Website/Blog: maxafritz.com LinkedIn : in/maxafritz

5. Now Micro is a Consulting & Device Life Cycle Management company
Now Micro’s Consulting Practice focuses on helping organization deliver the best end user experience by designing and implementing the most robust Systems Management, Cloud Productivity, and Identity Management solutions available.

6. User Profile Sync Overview Microsoft Identity Manager Overview History
Agenda
User Profile Sync Overview
Microsoft Identity Manager Overview
History
Demo

7. What is (was) SharePoint User Profile Sync?
A way for user properties to be synchronized to SharePoint from Active Directory (and back)
Department, Description, Profile Picture, Phone, etc…
Allows that information to be accessed within SharePoint, and synchronized back to active directory
In , uses a lightweight, built in, version of FIM
One of the most frustrating services within SharePoint

8. What is Microsoft Identity Manager?
Successor to Forefront Identity Manager
Introduced in 2016
Manage the users, credentials, policies, and access within your organization
Provide self service group management and user properties management through a web interface
Synchronize identities across platforms
Privileged Access Management for administrator accounts

9. History Lesson

10. SharePoint User Profile Sync History
Import from AD
SharePoint 2010
Built in FIM
SharePoint 2013
AD Import
SharePoint 2016

11. SharePoint User Profile Sync History
2010:
SharePoint got together with FIM team
Built a lightweight version of FIM for use in SharePoint
Required a lot of maintenance
Failed to start constantly
All around frustrating
SharePoint 2007
Import from AD
SharePoint 2010
Built in FIM
SharePoint 2013
AD Import
SharePoint 2016

12. SharePoint User Profile Sync History
2013:
Oops
Built in FIM didn’t work so well
Introduced AD Import
Easier to configure and run
Less features
Kept Built in FIM as an option
SharePoint 2007
Import from AD
SharePoint 2010
Built in FIM
SharePoint 2013
AD Import
SharePoint 2016

13. SharePoint User Profile Sync History
2016:
AD Import extremely popular in 2013
Led to the removal of Built in FIM completely
Those who need FIM features can deploy MIM
Easier to manage when it’s deployed seperately
SharePoint 2007
Import from AD
SharePoint 2010
Built in FIM
SharePoint 2013
AD Import
SharePoint 2016

14. MIM vs Active Directory Import (ADI)
Pros
1. Flexibility allows for customized import.
2. Can be customized for bidirectional flow.
3. Imports user profile photos automatically.
4. Supports non-Active Directory LDAP sources.
5. Multi-forest scenarios are supported.
1. Very fast and performant.
2. Known to be reliable (used by Office 365).
3. Configurable inside of Central Administration. (Less complex.)
Cons
1. A separate MIM server is recommended for use with your SharePoint farm.
2. The more customized the more complex the architecture, deployment, and management.
1. Import is unidirectional (changes go from Active Directory to SharePoint Server Profile).
2. Import from a single Active Directory forest only.
3. Does not import user photos.
4. Supports Active Directory LDAP only.
5. Multi-forest scenarios are not supported.

15. Deploying MIM One of the more difficult tools to deploy from Microsoft
As a fellow consultant put it, they failed to take the “f” out of “FIM”
Requires a SQL 2012 SP2 or higher client
Can exist on the same server
Can use a separate installation of SharePoint 2013 single server
Must be installed on the same server
Required to use the MIM portal (self service features)
We will not be demoing the install of this (it would take hours)

16. Demo Time

17. Questions ?

18. Thank you! Come ask me questions! Join me later today: Stay in touch!
A Hitchhiker’s Guide to Azure Active Directory (1:30-2:30, this room)
Stay in touch!
Twitter
Website/Blog: maxafritz.com
LinkedIn : in/maxafritz