SharePoint 2016 Feature Pack 2

by Robi 13. March 2018 21:20
It has become something of a habit for Microsoft to announce many new features for its products before and during the annual Ignite conference and it was no different this year. Feature pack 2 The cumulative September 2017 update brought with it not just minor fixes. It also included the SharePoint Framework, also known as SPFx, to on premise environments. With this fix, it is now possible to develop solutions and web parts the same way as in an O365 environment. SharePoint Framework (SPFx) For those of you who might not know the SharePoint Framework, let me just mention a few of its main characteristics. It runs in the context of the current user and the browser connection. It doesn't use any iFrames to develop solutions. All controls are drawn in the normal DOM of a page. It enables developers to use different levels of page loading, including "render", "serialize", "configuration changes", … It can use different JavaScript frameworks. It does not affect the general server performance. To use SharePoint data, SharePoint REST services or JSOM can be used. It should be noted that we will have to upgrade our skills and know how to use SPFx as it is now a part of SharePoint and SharePoint Online development. Besides SPFx, the feature pack also includes all the fixes and upgrades that Feature Pack 1 contained. In case you have already forgotten them, it is worth noting the following changes: Administrative Actions Logging. The logging of actions that administrators make. MinRole enhancements. Various MinRole improvements, including new server roles, mainly for minor environments where various roles are merged. SharePoint Custom Tiles. Making your own connections in App Launcher. Hybrid Auditing (preview) Hybrid Taxonomy Connection between the Managed Metadata service app with the one in O365. OneDrive API for SharePoint on premise. SharePoint 2019 We have listed a lot of new features, but we still can't forget about the announcement of SharePoint 2019 Server. The release date of this new product is expected to happen in late 2018. Two key characteristics are going to be: It will be built based on SharePoint 2016 Server. O365 connectivity. Microsoft has said that for the 2019 version, they will try to focus mainly on four key areas: Sharing and collaboration. A reliable client for synchronizing OneDrive for Business and SharePoint sites. A modern approach to employee collaboration. A modern way of sharing information and documents. Reporting and reacting. It is of vital importance to stay on top of all activities of different work groups and departments. Transformation of business processes. Maximizing productivity. Modern applications and effective business processes. Added value for admins and developers. A safe and modern infrastructure. A consistent user experience (O365 and on premise). Those of you who feared that SharePoint 2016 was the last on-premise version can now rest easy – SharePoint Server will stay on premise for quite some time. Robi Vončina Office Servers and Services MVP

Tags:

SharePoint 2016

SharePoint 2016 and MIM 2016

by Robi 13. March 2018 21:18
Part 2 In my previous article, I described the procedure for successfully installing Microsoft Identity Manager 2016 on a server. We described the prerequisites for a successful installation of the MIM 2016 synchronization service. In this article, we will take a look at what needs to be done to install MIM 2016 and connect it to SharePoint 2016 Server. Installing MIM 2016 To install MIM 2016 you need the installation files for MIM 2016 Server. If you do, launch the MIM Synchronization Service Installer. On the Configure MIM Synchronization Service Database Connection step, make sure you type the name and instance of the SQL Server where you want to create the synchronization database. In the next step, you need to type the name of the service account that you created for the synchronization service. In most cases, this will be MIMSync. When the installer asks you about groups, enter the appropriate AD security groups, as shown in the screenshot. When you click next and confirm the warning message, the installation of MIM Server will begin. This is more or less everything SharePoint Server needs you to do from the MIM Server side. After MIM Server has been installed, it is recommended to install SP1 for MIM 2016. You need to be careful when doing that, because the SharePointSync.psm1 module requires some manual intervention when PowerShell is checking the version of the MIM PowerShell Assembly. You can read more about this on the following page: Microsoft Identity Manager 2016 Service Pack 1 is now available! http://www.harbar.net/archive/2016/10/06/Microsoft-Identity-Manager-2016-Service-Pack-1-is-now-available.aspx Preparing MIM Server for integration with SharePoint 2016 SharePoint Connector The MIM Connector for SharePoint 2016 must also be installed after installing MIM Server. You can find it on the Microsoft Download portal. Download Forefront Identity Manager Connector for SharePoint User Profile Store from Official Microsoft Download Center https://www.microsoft.com/en-us/download/details.aspx?id=41164 SharePoint Connector is a MIM interface which allows us to use MIM synchronization to update profiles that are stored in the SharePoint User Profile Service Application. Integration To integrate MIM and SharePoint 2016 Server, Microsoft has prepared an example of integration and the necessary files. All the file are on the following GitHub portal: PnP-Tools/Solutions/UserProfile.MIMSync at master · SharePoint/PnP-Tools · GitHub https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/UserProfile.MIMSync We need to download the following files: SharePointSync.psm1 – a Windows PowerShell module for deploying and starting the synchronization solution. MA-AD.xml – This is the MIM management agent for Active Directory. MA-SP.xml – This is the MIM management agent for SharePoint Server. MV.xml – This XML file contains additional User Profile Synchronization configuration. I would also recommend reading Spencer Harbar's article who improved the script for creating a new SharePoint Management Agent and removed the need to reopen MA and enter the synchronization credentials again after enabling it. Enabling multiple OUs and avoiding credential touch up with the MIMSync "toolset" for SharePoint Server 2016 http://www.harbar.net/archive/2016/08/25/Enabling-multiple-OUs-and-avoiding-credential-touch-up-with-the.aspx We need to save all of the files to a place on MIM Server and then run a PowerShell command, so the SharePoint management agent is created in MIM. But before you can run the command written below, you need to fill in the missing data, so the script can execute successfully. #import module Import-Module "X:\Scripts\MIM\UserProfile.MIMSync\SharePointSync.psm1"  # ======================================== variables ==================== #$path="C:\Users\mim_admin\Downloads\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync" $path="C:\Create-MIM-MAs\" $forestName="dev.local" $forestSyncUser="dev\mimsync" $ouUnit="OU=Zaposleni,dc=dev,dc=local" $forestSyncPass=ConvertTo-SecureString -AsPlainText -Force 'Pa$$w0rd' $forestSyncCred=New-Object -TypeName System.Management.Automation.PSCredential -argumentlist $forestSyncUser,$forestSyncPass $spCentralAdminUrl="http://w-sp04:55555" $spadminUser="dev\sp16_admin_svc" $spadminPass=ConvertTo-SecureString -AsPlainText -Force 'Pa$$w0rd' $spAdminCred=New-Object -TypeName System.Management.Automation.PSCredential -argumentlist $spadminUser,$spadminPass # ======================================== variables =====================  ### Install the SharePoint Sync Configuration Install-SharePointSyncConfiguration ` -Path $path ` -ForestDnsName $forestName ` -ForestCredential $forestSyncCred ` -OrganizationalUnit $ouUnit ` -SharePointUrl $spCentralAdminUrl ` -SharePointCredential $spAdminCred ` -Verbose    After the script has executed, you should see the following entries in MIM Server: With the following command you start the synchronization of MIM with SharePoint and AD servers and users from AD should show up in the SharePoint User Profile service application. ### Run the Synchronization Service management agents  Start-SharePointSync -Verbose I hope this article will help you configure integration between MIM and SharePoint Server. In case you have any additional questions, you can contact me at robi@kompas-xnet.si Robi Vončina SharePoint MVP

Tags:

SharePoint 2016 | Microsoft Identity Manager

Calendar

<<  October 2018  >>
MonTueWedThuFriSatSun
24252627282930
1234567
891011121314
15161718192021
22232425262728
2930311234

View posts in large calendar

Page List

Month List