Hybrid SharePoint 2013/2016

Submitted by Vladilen on Sat, 10/29/2016 - 20:05

Step-by-step script of my recent Hybrid SharePoint 2016 - Office 365 implementation:


Office 365 Prerequisites

  • set and configure custom domain name
  • synchronize users (e.g. like this)
  • provide Office 365 licenses for hybrid users
  • (for hybrid search or Sharepoint 2016 DLP) provide license for farm account

On-Premises AD prerequisites

  • AD group "HybridUsers" for hybrid users

On-premises SharePoint Prerequisites

SharePoint 2013 Streamlined Architecture

Submitted by Vladilen on Thu, 01/28/2016 - 15:50

Based on "Streamlined Topologies for SharePoint Server 2013" diagram from Microsoft ("Topology design guidance for maximizing system resources"), 

Simplified for 4-servers high-available 3-tier farms:


Front-End Servers

Service applications, services, and components that serve user requests directly are placed on front-end servers. These servers are optimized for fast performance.

Low and Very low latency.

About ancient Kazakhs

Submitted by Vladilen on Mon, 11/30/2015 - 06:05

Will try to translate in english this joke-article from Askar Isabekov.

Ancient Kazakhs were tall blue-eyed blondes. And not because it is sucks to be a little narrow-eyed brunette, but because everyone knows that the real Kazakhs - a blue-eyed blondes. Legend has it - once in ancient times in one village in which they lived narrow-eyed and dark-haired Kazakhs, blue-eyed blondes came, and then all the inhabitants of the village came out and said blondes - you blondes are real Kazakhs, and we are not real. A blondes asked the fake Kazakhs - Why are we - real Kazakhs? And then fake Kazakhs responded blondes - And because the real Kazakhs - blue-eyed blondes. Here's a ancient legend.

step-by-step SharePoint Setup with AutoSPInstaller

Submitted by Vladilen on Tue, 09/08/2015 - 05:48

(the article is under construction)

How to setup SharePoint 2013/2016/2019 using AutoSPinstaller

the quick and easy way which can be used in your lab environment, as well in test and even in production and later be scaled-out, as performance and/or availability requirements grows up

Assume 3-tier topology - Front-End Server, Batch-Processing Server and SQL Server. Accounts according to least privilege principle.

Treat all server names, account names and domain names in this article are "for example", i.e. you should use your own names.