Installing SharePoint Server 2016 – Part 3


User Profile Synchronization service which uses the famour FIM (Forefront Identity Manager) has been removed in SharePoint 2016.  Microsoft suggest customers to use Active Directory Import to import profiles in SharePoint 2016.  Active Directory has limitation so Microsoft has provided Microsoft Identity Manager which is actually next generation of FIM.  MIM covers all limitations of Directory Import include multi forest import and profile pictures.  In this post we will set it up.

1. First you have to login to your MSDN Subscription and download the tool.  If you do not have MSDN subscription, you can download it from your volume licensing site.

image

2. Then download the following update https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=3092179&kbln=en-us Extract it to find the synchronization service hotfix 14 MB.

3. Next you need to create a service account for MIM.  I will create MIMService in my contoso domain.

image image

4. Next you need to download the script from github that Microsoft has written to import the MIM management agents for Active directory and SharePoint.

Open https://github.com/OfficeDev/PnP-Tools and click Download ZIP from middle right section.   The folder we are interested in is PnP-Tools/Solutions/

5. You need to Download and Install SharePoint Management Agent (SPMA) which is an essential if you need to connect MIM to your SharePoint installation. 

http://www.microsoft.com/en-us/download/details.aspx?id=41164

Mount the ISO for MIM.  Open Synchronization Service Folder and right click on Setup and choose Run as Administrator.  Click Yes on Setup

image

image

image

image

image

image

image

image

image

You would be asked to save the key.

image 

image 

You need to log off and log in again.

Now Install the hotfix update.  If you try to runt he setup you will see the following error message.

image 

Now open PowerShell as Administrator and Browse to the location of patch and type its name.  It will open.

image

image

Go to services and stop the Forefront Identity Manager Synchronization service then click Retry

image

image 

Now start the Forefront service if it is not started automatically.

image

Now Let’s Installt he MS Identity Manager SharePoint Connector

image 

image

Click Install and Finish.

image

Restart the Forefront Service again.

image

Let’s run the script for MIM management objects for AD and SharePoint and run a full Synchronization

Copy UserProfi.eMIMSync folder to C Drive.  Do not cut. keep the orignal version.

image

run PowerShell ISE as Administrator by Right Clicking on PowerShell ICON and then right click on PowerShell ISE and choose Run as Administrator.  Click New File ICON.  Now copy paste or type the following powershell.

Set-ExecutionPolicy unrestricted -Force

Import-Module C:\UserProfile.MIMSync\SharePointSync.psm1 -Force

### Install the SharePoint Sync Configuration
Install-SharePointSyncConfiguration `
  -Path C:\UserProfile.MIMSync `
  -ForestDnsName contoso.local `
  -ForestCredential (Get-Credential contoso\contosoadmin) `
  -OrganizationalUnit ‘ou=Users,dc=contoso,dc=local’ `
  -SharePointUrl http://sps-app-0:2016 `
  -SharePointCredential (Get-Credential contoso\spadmin) `
  -Verbose 

#Chaneg Forest Name

#Change Forest Credentials (Same Permission applies)

#Change OrganizationUnit

#Change SharePoint Url (Central Admin URL)

#Change SharePoint Farm Account Url

image

image

Verbose Output will appear on the screen

image

Now Open Synchronization Service to confirm that Management agents are imported successfully.  Restart the Forefront service.

image

Click on Management Agents.  to Add more containers to the import you must select ADMA and choose properties.

Click on Configure Directory Partitions –> Select your domain.com.  do not select configuration.

image

Click on Containers.  You must be asked to enter the credentials.

image

Select the desired Containers and Click OK and OK Again. 

image

I choose all 🙂 to see what happens

image

Run the following cmdlet to run full import.

Start-SharePointSync –Verbose

Note

First time I got “Stopped Server” error in Full Import Step of ADMA.  For some reason my SharePoint Server was uanble to ping the AD Server so I went to ADMA properties, in Directory Partitions -> I add a Preffered domain Controller as my domain controller name.  Then I ran the script again and bingo.

image

image

Once Synchronization service manager was able to connect to DC the preferred domain controller option got unchecked automatically.

image

You can snow see that I have 327 Profiles.  But I also have the Directory import Jobs running.  So lets disable them.

image

Click on Configure Synchronization Settings

image

Select Enable External Identity Manager and Click OK.

image

Now Notice the change.

image

Now let’s fix the Containers and run a full sync to remove the unwanted profiles from SharePoint.

image

image

You can see that 16 unwanted profiles are now marked for deletion.

image

We can do lot more with MIM.  Trevor Seward has written a series of articles on how to do User Profile property import, export, full and deleta synchronization using Task Schedular.  I suggest you check the series out.    There is no need to re-write the same thing that he has already done with details.

Microsoft Identity Manager Series by SharePoint MVP Trevor Seward
Part 1: Automating MIM User Profile Synchronization with SharePoint 2016

Part 2: Using MIM to Import Custom Attributes into SharePoint 2016

Part 3: Using MIM to Export Custom Attributes from SharePoint 2016

Part 4: Default MIM to SharePoint 2016 Attribute Mappings

Part 5: Basic MIM Configuration to Support SharePoint 2016

Part 6: Scoping the Active Directory Management Agent in MIM

Here is how the new My Site Looks

image 

The new App Launcher provides access to locations without breaking the User interface.

image

The new one drive experience in SharePoint on-premises

clip_image002

Next Creating Cloud Search Service Application and crawling content.

Installing SharePoint Server 2016 – Part 2


Its time to install SharePoint 2016.  SharePoint Server 2016 is the next generation of Micorosft SharePoint product which target hybrid deployments with Office365.  Cloud Search service application has been introduced to index On-Premises Content stored in SharePoint 2013, 2010 or even 2007.  The index will reside in SharePoint Online which reduce the need for storage and management of index.  Users in Office365 will be able to find content from Office365 or on-premises. 

Integration with Office365 include the ability to redirect my sites to OnDrive in SharePoint online.  App Launchers allows users in Office365 to access on-premises sites. 

Other major improvement include the removal of User Profile Synchronization Service.  Microsoft has decided to go back to set Active Directory Import as default method to synchronize profiles to SharePoint.  Microsoft Identity Manager 2015 or MIM can be used as an external tool to synchronize projects to SharePoint. 

There has been serious changes in the business intelligence front where Excel Services have been repalced with Excel in Office Online Server 2016.  You would need to setup trust with your BI Servers (Analysis Services) to Office Online servers to provide data refresh using PowerPivot and PowerView.

To find more information about What is new in SharePoint 2013 please check the following blog

https://blogs.office.com/2016/03/14/sharepoint-2016-rtm-and-the-future-of-sharepoint-event/

Resources to help you get started with SharePoint Server 2016

You can download the SharePoint Server 2016 Image from https://www.microsoft.com/en-us/download/details.aspx?id=51493

In this guide I will focus on OOTB installation.  Will post about using AutoSPInstaller later.

To mount the downloaded image to HyperV you must rename the file from img to ISO. Then mount the image to SharePoint VM.  Double Click on Drive ICON.

image

Install Software Prerequisites

image

image 

image

image 

Your VM will restart few times.

image

image

Better to restart the VM again before starting the setup.  Click on install SharePoint Server after reboot.

Enter the key

image

Accept the Terms and click Install Now

image

image

image

image

image

image

image

image

This screen shows you option for MinRole configuration.  There is not standalone option as it is replaced with SingleServer Farm.

image

image

image

The Wizard is compelte

image

image

Before we go to next step.  Let’s first disable loopback check.  Run the following PowerShell

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name “DisableLoopbackCheck” -value “1” -PropertyType dword

The best pratice for production farm is not to disable it.  Use the proper host name approach for production.

I will be running the configuration wizard as this is a dev farm.

image

image

image

 image

image

Click Next

Once the wizard is finished you must type Site collection details

image

image

image

image

image

Next Step : Installing and Configuring Microsoft Identity Manager for User Profiles.

Installing SharePoint Server 2016


SharePoint Server 2016 is RTM so its time to go back to the installation of latest software.  I am using SQL Server 2016 RC0 and Windows Server 2012 R2.  The goal is to complete installation for single Server SharePoint with Business intelligence.

3 Server Farm Setup

In this step I have

Active Directory VM : 700 MB RAM 2 Cores

SQL Server  VM: Dynamic Memory : 4 GB to 8 GB and 4 Cores

SharePoint Server VM: Dynamic Memory 8 GB to 12 GB and 6 Cores

All of this setup is on Windows 10 HyperV.  I am running it all on SSD so performance is pretty good.

I have Windows Server 2012 R2 with all latest updates installed.  I have basic service accounts already setup.

  • SPFArm
  • SPServices
  • SPWebApps
  • SPSearchService
  • SPContentAccess
  • SQLAdmin
  • SQLService

Installing SQL Server 2016 Release Candidate 0

I downloaded the RC 0 from MSDN and below are steps to install it.  I Mounted the ISO to My VM Media.

image

image 

image

Here you will notice a nice change.  You can either install SQL Server, Management Tools or Data Tools.  I choose New SQL Server stand-alone Installation

image

Choose Evaluation

image

image

Restart is needed

image

After Reboot – Did the same steps and ended up checking for updates.

image

image

image

Windows Firewall warning is import – We have to disable it as this is a lab environment.

image

image

image

image 

Re-Run the Check to confirm

image

Choose Database Engine and Analysis Services.  You would not find Management Tools any more. Click Next

image

Choose Named Instance.  Better to use for Office Online Server and Excel.  Click Next.  Here it took a little bit time for me.

image

Enter Account name and password for Agent, Database Engine and Analysis Services.  I am using the same, you can change if needed.

image

Select Mixed Mode Authentication, Enter password, and choose Add Current User.  I am also adding contoso\spadmin as SysAdmin as this is a lab.

image

Changed the data directores for easy management

image

Really Liked the new Temp DB View.  Click Next

image 

Choose PowerPivot Mode.

Click Add Current User, Now add SPFarm, SPAdmin, SPWebApp, SPServices account here for Office Online Server.

I did not changed the Data Directories for Analysis Services

image

Ready to Install

image

Updates

image

image

On my machine SQL took around 5 minutes.  You think SQL is done but it is not.  Let’s Install the management tools. 

image

You should welcome the new Visual Studio look of Management Studio Setup.

image

image

This should take 5 to 10 minutes

image

Reboot is required.

image

Search and Pin Management Studio and Configuration Manager on the desktop

image

image

image

Right Click on Server Node and Select Properites

image

Click Advanced and Select Max Degree of Paralleslism to 1 and Clik OK.

image

Let’s Open Analysis Services

image image

image

Test the Connectivity with SQL Server from SharePoint Box.

Login to SharePoint VM or Server as SPAdmin or SPSetup Account.

Create a New Text File on the Desktop and Save it as Test.UDL.  Make sure you choose All files.

image

Double Click on the UDL File.  Type Server name as Machine\SharePoint.

image

If you can see the 4 Out of the Box SQL Databases you can all good for SQL Now.  You can click Test connection after selecting a database.

image

Next Step – Installing SharePoint Server 2016.