SharePoint 2016: High Availability Farm Topology

MinRole concept was introduced in SharePoint 2016 and it aims to simplify the process of designing the farms. However, I still find ambiguous information about the count of servers in SharePoint 2016 farm.

Let's ask ourselves the question - What is the minimum number of servers which allow High Availability MinRole farm?

According to technet we have the following options:

 Small High Availability (HA) MinRole farm 4 Four servers with two shared roles: ·        Two Front-end with Distributed Cache servers ·        Two Application with Search servers Medium High Availability (HA) MinRole farm (Search optimized) 6 Six servers with both dedicated and shared roles: ·        Two Front-end with Distributed Cache servers ·        Two Application servers ·        Two Search servers Medium High Availability (HA) MinRole farm (user optimized) 6 Six servers with both dedicated and shared ﻿roles: ·        Two Front-end servers ·        Two Distributed Cache servers ·        Two Application with Search servers Large High Availability (HA) MinRole farm 8 Eight servers with four dedicated roles: ·        Two Front-end servers ·        Two Distributed Cache servers ·        Two Application servers ·        Two Search servers

But there are several articles (this one is maybe the best), that explain in details that the Distributed Cache service has two specifics:
- we need three servers for availability of the service
- we can have only Availability, not High Availability

So based on this information, I would transform the above table in this way:

 Small High Availability (HA) MinRole farm 5 Four servers with two shared roles: ·        Three Front-end with Distributed Cache servers ·        Two Application with Search servers Medium High Availability (HA) MinRole farm (Search optimized) 7 Six servers with both dedicated and shared roles: ·        Three Front-end with Distributed Cache servers ·        Two Application server ·        Two Search servers Medium High Availability (HA) MinRole farm (user optimized) 6 Six servers with both dedicated and shared ﻿roles: ·        One Front-end server ·        One Front-end with Distributed Cache ·        Two Distributed Cache servers ·        Two Application with Search servers Large High Availability (HA) MinRole farm 9 Eight servers with four dedicated roles: ·        Two Front-end servers ·        Three Distributed Cache servers ·        Two Application servers ·        Two Search servers

Finally, if one small company wants to use SharePoint 2016 platform and ensure the availability of all services, it will end up with the following infrastructure:

And remember - the roles "Front End with Distributed Cache" and "Application with Search" are available after you install the SharePoint 2016 Feature Pack 1. They are not part of the SharePoint 2016 RTW (release to web) build.

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed.
The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before.
There is a new control called ClientPeoplePicker.

How to use it:

<%@RegisterTagPrefix="wssawc"Namespace="Microsoft.SharePoint.WebControls"Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>

<wssawc:ClientPeoplePicker Required="true" ValidationEnabled="true" ID="peoplePicker" runat="server" InitialHelpText="<%\$Resources:wss,aclinv_PickerIntialHelperText%>" VisibleSuggestions="3" Rows="1" AllowMultipleEntities="false" CssClass

The column name that you entered is already in use or reserved. Choose another name.

The problem:
You want to create column with a specific name in SharePoint but SharePoint gives you the message "The column name that you entered is already in use or reserved. Choose another name."

Why this is a problem?
Because you need to create custom columns and content types using the default SharePoint interface.
And the business users have to see properly named columns - for example "Description", not "My Description".

Solution:
It is important to know something technical about SharePoint (versions Office 365, 2013, 2010):
- it supports columns with same Display Names.
- you can’t have columns with same Internal names

Let’s implement the following common scenario:
You are creating a SharePoint customization and you need the following column:
Type: Multiple lines of text
Internal Name: MyProjectDescription
Display Name: Description

Here is the correct way to achieve it:
1. Create the column MyProjectDescription.
This will create column with I…

Office 365 Migration API: how to migrate the taxonomy metadata

If you wander whether the Office 365 Migration API supports migration of taxonomy metadata, the answer is YES. The API supports it but there isn't good documentation about how to modify your xml files after the command ConvertTo-SPOMigrationTargetedPackage.

In this post, I'm going to show you the approach. I assume that you have base knowledge of how to use the Migration API.

The scenario I'm going to use is simple - migrate single Document library with single document.
The document has one taxonomy column (MyTaxonomy) and three versions:

Here are the steps:

Step 1: Export the document library

Export-SPWeb "https://portal.cosingens.com/"  -ItemUrl "/Shared Documents"  -Path "\\cos-dev-03\export1\Export" ` -NoFileCompr -IncludeVersions 4
This command will export the document library and will create the initial package.
The command is not part of the Migration API. It is well know since SharePoint 2010 and is part of the server side obje…