SharePoint 2016

What’s new in SharePoint Server 2016 Installation and Deployment

System Requirements

Scenario Deployment type and scale Processor RAM Hard disk
Database server running a single SQL instance Development or evaluation installation with the minimum recommended services 64-bit, 4 cores 12-16 GB 80 GB for system drive

100 GB for second drive

Database server running a single SQL instance Pilot, user acceptance test running all available services 64-bit, 4 cores 16-24 GB 80 GB for system drive

100 GB for second drive and additional drives

Web server or application server in a three-tier farm Development or evaluation installation with the minimum number of services 64-bit, 4 cores 8-12 GB 80 GB for system drive

80 GB for second drive

Web server or application server in a three-tier farm Pilot, user acceptance test running all available services 64-bit, 4 cores 12-16 GB 80 GB for system drive

80 GB for second drive and additional drives

NOTE Disk space and number of drives depends on the amount of content and the method chosen to distribute data for a SharePoint environment.

Deployment Scenarios

SharePoint Server 2013 SharePoint Server 2016
Workgroup Unsupported Unsupported
Domain Controller Developer Installation Developer Installation
Client OS Unsupported Unsupported
Dynamic Memory Unsupported Unsupported
Windows Web Server Unsupported Unsupported

Operating System Requirements

SharePoint Server 2016 is supported on Windows Server 2012 R2 and Windows Server Technical Preview. Evaluation copies of both operating systems can be downloaded from the TechNet Evaluation Center:

 

.NET Framework

The required version of .NET Framework is different for Windows Server 2012 R2 and Windows Server Technical Preview “Threshold”.

  • Windows Server 2012 R2: SharePoint 16 requires .NET Framework 4.5.2
  • Windows Server Technical Preview “Threshold”: SharePoint 16 requires .NET Framework 4.6 Preview, which comes with Windows Server Technical Preview “Threshold”.

NOTE Beginning January 13, 2016, .NET Framework 4.5.2 will be the minimum version of .NET Framework 4.x supported by Microsoft. See the Microsoft .NET Framework Support Lifecycle Policy FAQ at http://support.microsoft.com/gp/Framework_FAQ for more information.

 

Prerequisites

SharePoint Server 2016 prerequisites are similar to those required to install SharePoint Server 2013 and can be installed manually or with the Prerequisite Installer:

All the required prerequisites are installed by the SharePoint Prerequisite installer.

The SharePoint Server 16 Prerequisite Installer (prerequisiteinstaller.exe) installs the following software, if it has not already been installed on the target server:

Application Server Role, Web Server (IIS) Role. You can enable the Web Server (IIS) role and the Application Server role in Server Manager. However if the server is not connected to the Internet, the http://support.microsoft.com/en-us/kb/2765260 article has an Offline method that explains how to use several Window PowerShell cmdlets to add and enable these roles.

Microsoft SQL Server 2012 Native Client. Installs with the Microsoft SQL Server 2012 Feature Pack [http://www.microsoft.com/en-us/download/details.aspx?id=29065]

The Microsoft® SQL Server® 2012 Feature Pack is a collection of stand-alone packages which provide additional value for Microsoft® SQL Server® 2012. It includes the latest versions of:

    • Tool and components for Microsoft® SQL Server® 2012.
    • Add-on providers for Microsoft® SQL Server® 2012.

Microsoft ODBC Driver 11 for SQL Server [http://www.microsoft.com/en-us/download/details.aspx?id=36434]

Microsoft ODBC Driver 11 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2005, 2008, 2008 R2, SQL Server 2012, SQL Server 2014 and Windows Azure SQL Database.   This redistributable installer for Microsoft ODBC Driver 11 for SQL Server installs the client components needed during run time to take advantage of new SQL Server 2012 features, and optionally installs the header files needed to develop an application that uses the ODBC API.

Microsoft Sync Framework Runtime v1.0 SP1 (x64) [http://www.microsoft.com/en-us/download/details.aspx?id=17616]

Microsoft Sync Framework is a comprehensive synchronization platform that enables collaboration and offline scenarios for applications, services, and devices. Developers can build synchronization ecosystems that integrate any application and any type of data, using any protocol over any network. This service pack is intended to fix a handful of bugs as well as to transition to a public-facing change tracking API that is new in SQL Compact 3.5 SP2.

Windows Server AppFabric 1.1 [http://www.microsoft.com/en-us/download/details.aspx?id=27115]

AppFabric is a set of integrated technologies that make it easier to build, scale, and manage Web and composite applications that run on IIS. AppFabric targets applications built using ASP.NET, Windows Communication Foundation (WCF), and Windows Workflow Foundation (WF).

It provides out-of-the-box capabilities for you to easily build and manage composite applications, including:

    • Enhanced design and development tools in Visual Studio to build rich composite applications
    • Management and monitoring of services and workflows via integration with IIS Manager and Windows PowerShell
    • Distributed in-memory application cache to improve application performance

Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB2671763) [http://support.microsoft.com/en-us/kb/2671763]

Cumulative update package 1 for Microsoft AppFabric 1.1 for Windows Server. This hotfix package resolves several issues and adds several features that are described at https://support.microsoft.com/en-us/kb/2671763.

Microsoft Identity Extensions [http://www.microsoft.com/en-us/download/details.aspx?id=15373]

Microsoft Federation Extensions for SharePoint 3.0 enables interoperable federated access to SharePoint 3.0 sites using the WS-Federation standard. It is built using the Windows Identity Foundation and supports use of ADFS 2.0 as an identity provider.

Microsoft Information Protection and Control Client [http://go.microsoft.com/fwlink/?LinkID=528177]

The Active Directory Rights Management Services (AD RMS) Client 2.x is software designed for your computers to help protect access to and usage of information flowing through applications that use AD RMS.

Microsoft WCF Data Services 5.0 [http://www.microsoft.com/en-us/download/details.aspx?id=29306]

WCF Data Services 5.0 enables creation and consumption of data services for the Web according to version 3 of the Open Data Protocol (OData), which facilitates data access and change via standard HTTP verbs. WCF Data Services 5.0 includes .NET Framework server and client libraries as well as Silverlight client libraries.

Microsoft WCF Data Services 5.6 [http://www.microsoft.com/en-us/download/details.aspx?id=45308]

This installer will update the NuGet packages referenced by the WCF Data Services item templates to version 5.6.3. This installer also makes the code generation (the “Add Service Reference”) for consuming OData V3 endpoints available for all current and future .Net 4.5.X versions.

Microsoft .NET Framework 4.5.2 [http://support.microsoft.com/en-us/kb/2934520]

The Microsoft .NET Framework 4.5.2 is a highly compatible, in-place update to the .NET Framework 4.5.1, the .NET Framework 4.5, and the .NET Framework 4. However, it can run side by side with the .NET Framework 3.5 Service Pack 1 (SP1) and earlier versions of the .NET Framework.

The .NET Framework 4.5.2 for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2 is available on Windows Update and on Windows Server Update Service (WSUS).

Update for Microsoft .NET Framework to disable RC4 in Transport Layer Security (KB2898850) [http://www.microsoft.com/en-us/download/details.aspx?id=42883]

Resolved a security issue that has been identified that could allow an unauthenticated remote attacker to compromise a system and gain access to information.

Visual C++ Redistributable Package for Visual Studio 2013 [http://www.microsoft.com/en-us/download/details.aspx?id=40784]

The Visual C++ Redistributable Packages install run-time components that are required to run applications that are developed by using Visual Studio 2013, on computers that don’t have Visual Studio 2013 installed. These packages install run-time components of these libraries: C Runtime (CRT), Standard C++, ATL, MFC, C++ AMP, and OpenMP.

SharePoint Database Server Requirements

SharePoint Server 2016 requires SQL Server 2014 for its databases. You can download SQL Server from the TechNet Evaluation Center at http://www.microsoft.com/en-us/evalcenter/evaluate-sql-server-2014.   In addition SharePoint Server 2016 will support SQL Server 2016.  For additional information on SQL Server 2016 see also http://www.microsoft.com/en-us/server-cloud/products/sql-server-2016/.

MinRole (v1) Overview

One of the early new infrastructure advancements in SharePoint Server 2016 is a new concept, MinRole. MinRole is designed to transform guidance into code, simplifying deployment and scale with SharePoint ensuring a request is served end-to-end by the receiving server based on the origination of the request (I.e. end user or batch processing) and role of the destination server.

In previous versions of SharePoint, installation is role agnostic, which being a SharePoint servers’ role was only defined by what services were provisioned and its placement in a SharePoint Farm topology.  In many cases to serve a request, whether end user initiated or otherwise, the request traversed the scope of the SharePoint topology.

In addition, for each role there were specific documented recommendations to address performance and capacity planning, see also Streamlined Topologies for SharePoint Server 2013.

image

In SharePoint Server 2016 documentation was put into code based on the experience of running SharePoint at scale in Office 365.  MinRole provides an out-of-the-box experience that provides topology recommendations, simplifies on-premises server farm deployments, and reduces the unit of scale to simplify capacity planning while providing predictable performance characteristics through enabling selective provisioning of SharePoint server roles based on position and function within a topology.

image

MinRole enables an administrator to select the appropriate server role for a specific server when provisioning SharePoint Server 2016 based on five (5) predefined configurations:

Role Name Description
Special Load Reserved for services to be isolated from other services, I.e. 3rd party, PerformancePoint, etc.
Web Front End Services end user requests, optimized for low latency.
Single Server Farm Provisions all services on the server for a single server deployment.  This role is provided for evaluation and development purposes.
Search Reserved for Search services.
Application Services the backend jobs or the requests triggered by backend jobs, optimized for high throughput.
Distributed Cache Services distributed cache for the farm. Optionally, the server assigned to this role can load balance end user requests among the web front ends.

A predefined server role is configured and optimized for its intended purpose provisioning the expected services designed to support its function within a server farm environment.

In SharePoint Server 2016 MinRole can be instrumented through the PSConfig GUI or command line.

 

PSConfig and Windows PowerShell

MinRole adds a new command line parameter, localserverrole, that can be used to specify the role that should be assigned to a specific server when configuring SharePoint Products and Technologies and accepts the following values:

  • SpecialLoad
  • WebFrontEnd
  • SingleServerFarm
  • Search
  • Application
  • DistributedCache

 

Example 1 PSConfig.exe

clip_image002

psconfig.exe -cmd configdb -create –server [Database Server Name] –database [Configuration Database Name] –user [Farm Service Account] –password [Farm Service Account Password] –passphrase [Passphrase] –admincontentdatabase [Central Administration Content Database Name] -localserverrole SingleServerFarm

 

Example 2 Windows PowerShell

New-SPConfigurationDatabase –DatabaseName [Configuration Database Name] –DatabaseServer [Database Server]
–AdministrationContentDatabaseName [Central Administration Content Database Name] –Passphrase (ConvertTo-SecureString
[Passphrase] –AsPlaintext –Force) –FarmCredentials (Get-Credential) -localserverrole SingleServerFarm

 

PSConfigUI.exe

MinRole provisioning is available through PSConfigUI.exe in addition to PSConfig.exe.

 

Example 1 PSConfigUI.exe

clip_image003

Demo Video

http://1drv.ms/1EBogcv

NOTE Sequences shortened.

 

Health Rules and Compliance

To ensure role-based servers remain in compliance with their specified configuration – SharePoint Server 2016 includes new SharePoint Health Analyzer Health Rules to evaluate individual server role compliance and notify administrators of any changes to a predefined server role.

image

For example, if a server role is provisioned as a Web Front End and an unexpected service (I.e. Search) is provisioned on that machine, the SharePoint Health Analyzer will detect the deviation and generate a warning indicating the server is out of compliance in addition to providing an option to programmatically resolve the issue and bring the server back within compliance with its configured role definition.

image

The Health Rules that monitor the status of server roles scan daily comparing the service instances on servers to their expected configuration (per the assigned role) and generated a Health Report detailing any deviation from the assigned role to include:

  • Service instances that are stopped, but we were expecting them to be started​
  • Service instances that are started, but we were expecting them to be stopped​

NOTE The Special Load role is exempt from scanning.

Administrators can change the scan schedule and/or disable the scan entirely in addition to disabling the auto-fix capabilities designed to ensure a server remains within compliance with its assigned role.  In the event automatic fix is disabled, MinRole will not enforce compliance with the servers’ assigned role.   In addition MinRole provides support for automatic provisioning of services assigned to a servers’ respective role.

In conclusion, MinRole improves performance and reliability through ensuring an incoming request is served by the receiving server, reducing server to server interaction, reducing dependencies, and improving speed – enabling a model based on unit scale that provides better load distribution and proper sizing when compared to SharePoint Server 2013.

NOTE SharePoint Server 2016 does not support standalone installation which automatically installed SQL Server Express Edition and configured the farm on a single computer.

You can deploy SQL Server and then configure the SharePoint farm separately using SharePoint Farm Configuration Wizard in Central Administration.

Upgrade and Migration

SharePoint Server 2016 will support upgrade from SharePoint Server 2013.  To upgrade from SharePoint Server 2013 to SharePoint Server 2016, you can use the database-attach method to upgrade. In the database-attach method, you first create and configure a SharePoint Server 2016 farm. Then you copy the content and service application databases from the SharePoint Server 2013 farm, and then attach and upgrade the databases.  This upgrades the data to the new version.

NOTE Site collections provisioned in backward compatible SharePoint 2010 (14) mode, must be upgraded to 2013 prior to upgrading to SharePoint Server 2016.  For additional information on upgrading site collections to SharePoint 2013 see also https://technet.microsoft.com/en-us/library/jj219650.aspx.

Additional Resources

Learn more about the evolution of SharePoint, roadmap, futures, and the road ahead:

BLOG The Evolution of SharePoint [http://blogs.office.com/2015/02/02/evolution-sharepoint/]

BLOG SharePoint Server 2016 Update [http://blogs.office.com/2015/04/16/sharepoint-server-2016-update/]

VIDEO The Evolution of SharePoint: Overview and Roadmap [https://channel9.msdn.com/Events/Ignite/2015/FND2203]

SLIDES The Evolution of SharePoint: Overview and Roadmap [http://video.ch9.ms/sessions/ignite/2015/decks/FND2203_Baer.pptx]

Learn more about platform investments in SharePoint Server 2016:

VIDEO What’s new for IT Professionals in SharePoint 2016 [https://channel9.msdn.com/Events/Ignite/2015/BRK2188]

SLIDES What’s new for IT Professionals in SharePoint 2016 [http://video.ch9.ms/sessions/ignite/2015/decks/BRK2188_Walters.pptx]

Reference :

https://blogs.technet.microsoft.com/wbaer/2015/05/12/whats-new-in-sharepoint-server-2016-installation-and-deployment/ 

*************************************************************************************

Original: https://sharepointsolutiontips.blogspot.in/2016/06/sharepoint-server-2016-beta-2-and-sp.html

SharePoint Server 2016Beta 2 and SP 2016 RC (Single Server Farm) Technical Preview Deployment Guide-Part 1

Overview/Introduction
This guide shows you how to create a closed environment with an Active Directory on a separate server. With a closed environment depend on connectivity to your company’s AD or on a person managing it (e.g. if you need accounts or changes).
SharePoint Server 2016 IT Preview provides a first look of overall Product Improvements and Features with
SharePoint Server 2016 IT Preview provides a first look of overall Product Improvements and Features with
Its latest release. This Version is not fully armed with the complete set of features and capabilities. As always
The final product will be announced with RTM (Released to Manufacture) Version.
This Book will guide you to install and Configure Microsoft SharePoint Server 2016 in a Multi-Server Farm
Mode for testing and Developmental Purposes.
Microsoft has Released SharePoint Server 2016 Technical Preview which is specifically targeting the
Technical audience to allow this latest version to be tested prior to its next major releases. Microsoft
Marking another Milestone with their one of the largest product family ‘SharePoint Server’ with this
Release.
Some of the Key benefits of 2016 are:


  • Improved Provisioning capabilities
  • Mobile and Touch support
  • App Launcher
  • New and improved Controls
  • SharePoint Insights
  • Simple and Natural Sharing
  • Large File Support
  • Compliance Tools
  • Cloud Hybrid Search
  • Hybrid Scenarios Coverage
 SHAREPOINT 2016 – NEW & IMPROVED FEATURES
New information available for SharePoint 2016 can be classified in 4 categories:
Hardware Requirements


Installation Scenario
Memory / RAM
Processor
Hard Disk
Single Server*
16-24 GB
64-bit, 4 cores
80 GB
Farm Server
12-16 GB
64-bit, 4 cores
80 GB
Database Server
Refer system requirement for 64-bit version of SQL Server 2014 Service Pack 1 or SQL
*There is a built in SQL Server. You need to install a separate SQL Express/Developer or any other edition even for development server.
Software Requirements
  • Any one of Windows Server 2012 R2 | Windows Server 10
  • Windows Management Framework 3.0
  • Application Server Role
  • Web Server (IIS) Role
  • Microsoft .NET Framework 4.5.2 (in on Windows Server 10, then Microsoft .NET Framework 4.5.6)
  • Update for the .NET Framework 4 (KB2898850)
  • Microsoft SQL Server 2012 Native Client
  • Microsoft Identity Extensions
  • Microsoft Sync Framework Runtime v1.0 SP1 (x64)
  • Windows Server AppFabric v1.1 (MS is planning tend AppFabric, but it will be supported for SP 2013 and 2016).
  • Windows Identity Foundation v1.1
  • Microsoft Information Protection and Control Client
  • Microsoft WCF Data Services.
Upgrade and Migration
  • Upgrade path is from 2013 to 2016
    • Upgrade 14.5 mode site t15 mode and then upgrade
    • Allow the same database attach upgrade process
  • Migrate Content t2016 (using migration APIs or partner tools)
Auth N-Z
  • Windows Identity over SAML claims
  • Trying to normalize on oAuth/OpenID standards
SMTP Connection
  • Allow using non-default ports
  • Allowing to use STARTTLS connection encryption.
Reliability, Performance and scalability
  • Moving from SharePoint 2013 based job enable / disable to predefined set of logic executing on a machine (Termed as MinRole Topology)
  • New Server Roles in SharePoint 2016
    • Special Load – custom service applications, services, third party components which are outside of MinRole Topology
    • Web Front End – services end user requests. Servers are optimized for low latency
    • Search – service application provisioning, indexing service and other search components.
    • Application – services backend jobs or requests triggered by backend jobs. Servers are optimized for high throughput
    • Distributed Cache – servers distributed cache for the farm.
    • Single Server Farm – for development purpose, configure (excluding SQL Server) all services on one server.
  • New Service categories in SharePoint 2016
    • User Services
    • Robot Services
    • Caching Services
  • Server Role and Health Analyzer
  • Patching Updates
  • Improvement in boundaries and limits
    • Content DB size up tTB’s (not yet identified the limit)
    • 100K sites per site collection
    • List view threshold > 5000 items
    • Upload file size up t10 GB and removed character restrictions
    • Search scaling up t500 M items.
  • Better File Performance
    • Use BITS (Background Intelligent Transfer Service) for better file performance
  • Fast Site Creation
    • Create faster site collections at database level using the standard site template saved as site.
    • Remove feature activation overhead
  • User Profile Service
    • Bi-directional sync using external FIM service. Nbuilt in FIM anymore.
  • Project Server
    • Still require separate Project Server Licensing, but SharePoint and Project Server content database is merged.
  • Durable Links
    • New sharing URLs are resources Id based, thus renaming file, moving file will not break the link already shared.
Analytics (Insights and Data)
  • Real time data analysis on various parameters
    • Usage
      • daily active users
      • Weekly active users
      • Usage by browser
      • Usage by agent
      • Usage by OS
    • Storage
      • Storage by site template
      • Daily storage
      • File type
      • Storage breakout
    • Health Reports
    • Network
    • Portals
 Cloud Experience
  • Compliance Center
    • This showcase the feasibility of bringing same compliance system ton-premises which works well in O365 with Azure RMS.
    • Discover and preserve with hybrid eDiscovery.
  • Cloud Search Service Application
    • This unifies the on-premises and cloud data search from one search center.
    • This also adds value to Office Graph / Delve textend the presence on on-premises.
    • This can alsleave search running in cloud only while indexing from on-premises and online.
  • Extranet
    • Making easier to maintain and publish sites to Internet.
    • Using O365 Identity federation services.
  • Team Sites
    • Separate the data in either on-premises or in cloud
    • Follow sites, documents or people in on-premises and master the information in cloud.
    • Allowing ODF files creation.
  • Scenario Picker
    • Hybrid deployment automation
    • Select the Hybrid configuration required and use automated and wizard driven information to setup Hybrid (forget the lengthy procedures and PowerShell scripts to run)
Note: the information in this blog post is based on the information presented and available on public forums. The actual product SharePoint 2016 can have difference from what is available. Please take time to check the new features when the product is released.
ARCHITECTURE OF THIS SCENARIO
A Three-Tier farm is used for this scenario together with a Separate Active Directory Server in order to demonstrate the three layers as below figure.



Note: Here we are going for single server farm server

 

HARDWARE REQUIREMENTS

DEMO SERVER
Component
Requirements
Processor
64-bit, four cores (small deployments)
64-bit, eight cores (medium deployments)
RAM
12 GB (small deployments)
24 GB (medium deployments)
Hard disk
127 GB

 

SOFTWARE REQUIREMENTS

In order to deploy SharePoint 2016 beta 2 you need the 64-bit edition of one of the following operating

Systems:

 

  1. Windows Server 2012 R2 – Standard
  2. Microsoft SQL server 2014 SP1
  3. Microsoft .net framework 4.5

    **************************************************************************

    SharePoint Server 2016Beta 2 and SP 2016 RC (Single Server Farm) Technical Preview Deployment Guide-Part 2

    1.1 INSTALLATION

    1. Start the install wizard for Windows Server 2012 R2.
    2. Install an operating system which includes the GUI.
    3. Select ‘Custom: Install Windows only (advanced)’ and create a new partition using the drive options.

     

    1. Use the newly created partition to install Windows Server 2012 R2.

     


     

    1. Wait for the installation to complete.


     

     

    Note: At this point you have a basic but not configured Windows Server 2012 R2 image.


    1.2 ADD ‘ACTIVE DIRECTORY DOMAIN SERVICES’ ROLE TO THE SERVER AND PROMOTE THE SERVER AS ‘DOMAIN CONTROLLER’

    1. Open Control Panel > Programs and Features > Turn Windows Features On and Off > Add Roles and Features > Click ‘Next’ from the Prompt Window and opt for ‘Role based and Feature Based Installation.
    2. Select the Local Server from next Window and click ‘Next’.
    3. Select ‘Active Directory Domain Services’ from next window. Setup will prompt for dependent features that are required for Active Directory Domain Services installation. Click on ‘Add Features’.
      http://www.codeproject.com/KB/sharepoint/1072286/add_role_and_feature_before_pre-reqs.png
  • After Clicking ‘Add Features’ from the previous window, installation will begin. Click ‘Close’ once the installation is completed.http://www.codeproject.com/KB/sharepoint/1072286/add_role_and_feature_before_pre-reqs_2.png
  • Now that the Active Directory domain services are installed, we need to promote the server as Domain Controller and create a Domain. Click on the warning sign appearing on the main Server Manager Window. A popup will appear. From the popup, click on ‘Promote this server to a domain controller’ link.

http://www.codeproject.com/KB/sharepoint/1072286/add_role_and_feature_before_pre-reqs_3.png

  • Active Directory Domain Services Configuration Wizard will start. Select ‘Add a new forest’ option, give your root domain a domain name and click next.http://www.codeproject.com/KB/sharepoint/1072286/add_role_and_feature_before_pre-reqs_4.png
  • On the next window, provide the password for ‘Directory Services Restore Mode’ and click next.
  • Click on the Install button and wait for the installation to complete.http://www.codeproject.com/KB/sharepoint/1072286/add_role_and_feature_before_pre-reqs_6.png
  1. You need to restart the server once domain controller is setup. After restart, you will see your domain name prefix with your local admin account. (Demo server\Administrator).

    1.3 COMPUTER SETTINGS


    1. Login to the DEMO SERVER servers and Join a domain and if necessary. Restart your Servers.
  2. 1.4 IE ENHANCED SECURITY CONFIGURATION

    1. Disable IE Enhanced Security Configuration if you have an isolated Hyper-V environment and you want to work directly on the server (e.g. open Central Administration). By login to the server and on Computer management options


    1.5 NETWORK SETTINGS


    1. Login to the all servers and Go to ‘Control Panel > Network and Internet > Network and Sharing Center’ and select ‘Change advanced sharing settings’.
    2. On the Change Sharing options for different Network Profiles, Enable ‘File and printer sharing’.


    This allows you to ping your servers and helps you to trouble shoot problems e.g. checking connectivity.

    1.6 VIRTUAL MEMORY

    1. Login to the all server and Enable virtual memory using ‘Control Panel > System and Security > System’.

    1.7 REMOTE DESKTOP

    1. Login to all server and Enable remote desktop using ‘Control Panel > System and Security > System’.


    1.8 FIREWALL SETTINGS

    1. Login to all server and Turn off Windows Firewall for domain networks from the firewall setting page under control panel.

    1.9 USER ACCOUNT CONTROL SETTINGS

    Login to all servers and Disable User Account Control Settings if you have an isolated Hyper-V environment for your setup administrator.  Control Panel -> User Account -> Change user Account Control Settings

SharePoint Server 2016Beta 2 and SP 2016 RC (Single Server Farm) Technical Preview Deployment Guide-Part 3

  1. SQL Server installation

  1. Login to server (DEMO SERVER) by remote with user account “Domain\Administrator” using password: “Your password”
  2. Open mount SQL server 2014 SP1 ISO file and right click on Setup run as Administrator.

 

  1. The landing page looks pretty similar to the earlier versions, and you can choose the installation tab to get things started.
  2. Run System configuration checker
  1. Select new server standalone installation or add features to an existing installation

 

  1. Choose the stand-alone install option, and it will take you to the product key page.
https://sandroaspbiztalkblog.files.wordpress.com/2014/12/23-bts-2013-r2-sql-server-2014-product-key.png
  1. This screen is where you need to accept the license terms.

 

  1. These are the steps where Global Rules, Product Updates are checked and Setup files are extracted and installed. If the checks are good, then the install will proceed to the next step automatically.
  1. Install rules are checked for this step.

 

  1. This step provides you with Feature installation options. In this install I will discuss about the first option, ie SQLServer Feature Installation.
SQL2014 RTM Install6

 

  1. This step is where you will select the features. I’m choosing only those ones which I need for my testing
SQL2014 RTM Install7

 

  1. This step lets you decide if you want to go with Default Instance or a Named Instance.

 

  1. We select the account for the services.
  1. Select the Authentication mode, Data directories, and File Stream options as mixed mode, For Data Engine configuration and File stream let it be by default only and do next.

 

  1. On the analysis service configuration wizard select default multidimensional and data mining mode and add current user and do next.
  2. On Reporting services configuration select install only, Later we can configure.
  1. Distributed client and controller is optional we can do default configuration  After Click next Ready to install wizard will appear, review and do install

 

  1. On the “Complete” page you can view the Setup summary log by clicking the blue link provided on the bottom this page. To exit the SQL Server Installation Wizard, click Close,
  1. open SQL studio 2014

SharePoint Server 2016 Beta 2 and SP 2016 RC (Single Server Farm) Technical Preview Deployment Guide-Part 4

SharePoint 2016 Beta 2 installation

  1. Login to server (DEMO SERVER) by remote with user account “Domain\Administrator” using password: “Your password”

 

  1. Download SharePoint server 2016 beta2 from below link and mount to server(DEMO SERVER)

 

https://www.microsoft.com/en-us/download/details.aspx?id=49961

 

  1. Go the directory where do you have your installation files. Then click on Install software prerequisites to start Prerequisite tools installer or you can find out the Prerequisite.exe file and run as run as Administrator.
  1. It will start product preparation tool do next and install this, Once this will finish server will get restart.

  1. Go the directory where do you have your installation files. Find out the setup.exe file and run as Administrator. On the “Enter Your Product Key” screen, fill your product key then press “Continue” button (SharePoint Server 2016 Preview trial key NQTMW-K63MQ-39G6H-B2CH9-FRDWJ)
  1. On the Choose a file location screen, verify the installation path that you want to store system files
  2. Click Install to start installation progress.
  1. Once installation will finish don’t run the SharePoint 2016 Products and Configuration Wizard, Close wizard and run configuration wizard.

  1. Click “Yes” button on the warning box. Then On the following screen, check on “Create a new server farm” radio button then click “Next” button

  1. On the “Specify Configuration Database Settings” screen, fill corresponding “Database server” and “Database name” information. With the “Database Access Account”,

  1. Fill “Passphrase” on the following screen, remember to note the “Passphrase” for using later
  1. On the Specify Server Role, select which kind of server role that you want to deploy this server to the farm. In this deployment, I would like to deploy as Single Server Farm for testing and development purpose. Select “Single-Server Farm” and click Next

  1. On the following screen, you can check on the “Specify port number” check box to specify the port number of the central admin site, if not, the port number will be a default number. Check on the “NTLM” radio button then click “Next” button to continue
  1. Click Next to preview configuration summary.

Then, click next. The Configuration process will be progress.

  1. Checked from Database server, there are 2 databases created. Noted that in previous version, in this step only 1 Configuration database will be created. From SharePoint 2016, Another database name was created SharePoint_AdminContent_GUIID
  2. Once installation will finish, Automatic Central admin site will get open as below.

 

  1. Cancel Start wizard and click on central administrator.

2. Installation of SharePoint Server 2016 RC

2.1 Get a SharePoint Server 2016 Release Candidate Patch

 

From the following URL, you obtain the RC of the patch.
https://www.microsoft.com/en-us/download/details.aspx?id=50737

 

More than one patch is available for download, but, what is needed is “SharePoint Server 2016 Release Candidate Global Patch.zip”.

2016-01-25 7-07-31

2.2 Download language pack and install SharePoint 2012 candidate English perquisite installer from below link:

https://www.microsoft.com/en-us/download/details.aspx?id=50737

 

2.3 It will download in zip format, unzip and install prerequisite installer, once it will install, server will get restart and finish installation.

 

2.4 Application of Patch Each Patch because that is the zip, leave expand it. First, expand the SharePoint Server 2016 Release Candidate Global Patch, run the sts.msi.

2.5 By the way, the message to close the AppFabric cache service as shown in the following figure came out in the hand of the verification environment. Here there is no problem to go with [OK].

2.6 Once all done we need to restart server (recommended)

2.7 After installation of the patch, to access the SharePoint Central Administration site, click Upgrade and Migration> management of the state of the update, and then verify that each patch has been applied.

2.8 You will run the SharePoint Products Configuration Wizard, Open SharePoint 2016 Products Configuration wizard and run this

Click on finish button

2.9 In addition, the SharePoint Central Administration site, make sure that it is the [System Settings]> to access the [this server management of the farm], version of the configuration database is “16.0.4327.1000”. By the way, in Beta 2 this version was “16.0.4306.1001”.

Thanks.

*********************************************************************************

How to Install SharePoint 2016 (Single-Server Farm) on VM

Below is the summary of SharePoint 2016 installation process.

  1. Add ‘Active Directory Domain Services’ Role to the server and promote the server as Domain Controller.
  2. Install SQL Server 2012 SP1.
  3. Install SharePoint 2016 Prerequisites on the server.
  4. Install SharePoint 2016 Beta 2 on the server.
  5. Run the SharePoint 2016 Products Configuration Wizard.
  6. Configure SharePoint Farm.

1. Add ‘Active Directory Domain Services’ Role to the Server and Promote the Server as ‘Domain Controller’

  1. Open Control Panel > Programs and Features > Turn Windows Features On and Off > Add Roles and Features > Click ‘Next’ from the Prompt Window and opt for ‘Role based and Feature Based Installation.
  2. Select the Local Server from next Window and click ‘Next’.
  3. Select ‘Active Directory Domain Services’ from next window. Setup will prompt for dependent features that are required for Active Directory Domain Services installation. Click on ‘Add Features’.
  4. After Clicking ‘Add Features’ from the previous window, installation will begin. Click ‘Close’ once the installation is completed.
  5. Now that the Active Directory domain services are installed, we need to promote the server as Domain Controller and create a Domain. Click on the warning sign appearing on the main Server Manager Window. A popup will appear. From the popup, click on ‘Promote this server to a domain controller’ link.
  6. Active Directory Domain Services Configuration Wizard will start. Select ‘Add a new forest’ option, give your root domain a domain name and click Next.
  7. On the next window, provide the password for ‘Directory Services Restore Mode’ and click Next.
  8. Click on the Install button and wait for the installation to complete.

You need to restart the server once domain controller is setup. After restart, you will see your domain name prefix with your local admin account. (DEV\Administrator).

2. Install SQL Server 2012 SP1

I assume you already know how to install SQL Server 2012. Run the SQL Server 2012 Wizard and install the server. Refer to this article if you need any help.

Also note that since we are setting up only virtual environment for development purpose, creating separate service accounts for different SharePoint and SQL services is beyond the scope of the article. We will only use default Local Administrator account.

3. Install SharePoint 2016 Prerequisites

(Note that you need to have internet access on your VM to download prerequisites software).

  1. Mount the SharePoint 2016 ISO file to the VM. Double click on the drive to start the SharePoint 2016 setup (Alternately, you can open the drive and run default.exe or setup.exe).
  2. SharePoint 2016 installation wizard will start.
  3. From the SharePoint 2016 setup wizard, under ‘Install’, click on ‘Install the software prerequisites’.
  4. Click Next from the welcome window.
  5. Once the Application Server and Web Server Roles are configured, setup will prompt to restart the Server. Restart your VM.
  6. After restart, setup will continue installation. Once the installation is successfully completed, click Finish button.

4. Install SharePoint 2016 Beta 2

Here is the main part.

  1. Run the SharePoint 2016 installation media and click on ‘Install SharePoint Server’ link from the installation dialog. SharePoint 2016 setup Wizard will start.
  2. Enter the SharePoint 2016 Trial Beta 2 Version Product Key NQGJR-63HC8-XCRQH-MYVCH-3J3QR and click continue.If this trial key does not work, please refer to the ‘Install Instructions’ section of Microsoft SharePoint 2016 Beta 2 trail version download page to get the latest key.

  3. Accept the Microsoft Software License Term and click Continue.
  4. From next window, if you want to change default installation path, click Browse and provide location otherwise leave default installation path and click ‘Install Now’.
  5. Installation will start.
  6. Once the SharePoint 2016 Installation is finished, setup will auto select ‘Run the SharePoint Products Configuration Wizard now’ option. Leave this option selected and click ‘Close’.

5. Run the SharePoint 2016 Product and Configuration Wizard.

  1. From the SharePoint Products Welcome window, click Next.
  2. Select ‘Create a new server farm’ option and click Next.
  3. Provide the database server name. If database is installed on the same VM, you can just enter dot which means local server. You can also enter local or remove database server name.Leave the Database name as SharePoint_Config. This will be the SharePoint central admin configuration database.

    Provide the Username and Password to connect to the database and click Next.

  4. Enter the SharePoint Farm Passphrase and click Next. This Passphrase is required to connect with the Farm while adding a new server.
  5. Select the Role of the Server. Since we are setting up Single Server Farm, select ‘Single-Server Farm’ from this option and click Next.
  6. From Next window, specify SharePoint Central Administration Web App port number and click Next. I suggest you to keep the default port.
  7. SharePoint Product configuration will start.
  8. Once configuration is completed, copy the central administration URL and click Finished.

6. Configure SharePoint Farm

  1. Open a new browser and hit SharePoint 2016 Central Administration URL.SharePoint Farm configuration will start. Click on ‘Start the Wizard’ button.

  2. From the Service Application and Services screen, leave the default option selected and click Next.
  3. SharePoint will configure the SharePoint Farm Level Applications and Services.
  4. Once Farm Level Application and Service are successfully provisioned, you will receive the Farm Configuration completion message on the screen. Scroll down and click on Finish.

Now you can go to central admin and create your first SharePoint 2016 web application.

Congratulations, you have successfully installed and configured SharePoint 2016 !!

Original post :http://dotnetgeekstalk.blogspot.in/2016/01/

 

Advertisements