But what does this mean for you?
Biggest Implications
- Exchange Online (Office365) for the MIM Service
- without losing the ability to approve requests from within Outlook, and the requesting of groups within Outlook.
- Since lots of orgs are using Office 365 no more embarrassing conversations about these great features you can't have.
- Support for other browsers for MIM Portal
- SSPR already supported other browsers but now MIM Portal will support Chrome, Firefox and Safari.
- This means less customer resistance
- Platform Support -- MIM now supports all of the latest platforms Windows 2016, Active Directory 2016, SQL 2016, SharePoint 2016, Exchange 2016.
- Sync, Service and Portal
- Can now run on these
- Portal can now run on SharePoint 2016
- But there is not a foundations version meaning a free version
- So keep running on SharePoint 2013 Foundations for now unless MSFT starts including a license for SharePoint 2016
- SharePoint 2016 no longer uses FIM/MIM
- You can use MIM, but the default is the new built in Active Directory Import
- If you do use MIM to synch to SharePoint check Spencer Harbar's notes
- BHOLD
- The supported platform page lists that with MIM 2016 SP1 BHOLD now supports SQL 2014
- Say what? Why not SQL 2016? is this an error? If true this implies that BHOLD isn't as highly prioritized.
- MIM Certificate Management
- Lists the only supported client as Windows 7
- Again -- if true this suggest lower priority. In general most new MFA solutions aren't using smart cards and certs.
- PAM now supports Windows Server 2016 and forest functional level 2016
- Kerberos tickets are now time limited based on the time left on your role activation
- Improved security!
Finally, look at Jorge's screenshot by screenshot post on how to upgrade
No comments:
Post a Comment