To read the first part, click here.

Introduction

The SharePoint world is rapidly moving into the Cloud with SharePoint Online and Office 365, but some organizations are still not ready to move completely to Office 365 and SharePoint Online.

Upgrading to SharePoint 2016 or SharePoint 2019 that have support for hybrid scenarios can be a valid solution.

This post is based on upgrading a SharePoint 2010 farm into SharePoint 2016 using the database attach approach but should also be valid if you want to upgrade to SharePoint 2019. This post assumes that the we will only migrate the content database(s) from the source SharePoint 2010 to SharePoint 2016 and all other SharePoint databases are created in the target SharePoint 2016 farm during its installation process.

If you want to learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, click here and here.

There is another valid migration approach to migrate from SharePoint 2010 to SharePoint 2016 by using content migration. In this approach, the upgrade is not based in a database upgrade process but on content migration and typically a 3rd party solution is necessary to do the content migration. A few 3rd party solutions that can do the job are ShareGate, AvePoint and Metalogix.

Upgrading a SharePoint farm using the database attach approach can be a complex task and the upgrade process is composed by a series of steps:

• Migrating Custom Developed Solutions from SharePoint 2010 to SharePoint 2016 (outside of the scope of this post)
• Upgrade to a temporary SharePoint 2013 farm
• Upgrade to the target SharePoint 2016 farm

IMPORTANT NOTE: In a typical upgrade process, the below steps should be performed twice if there are custom developed solutions:

• The first time, to test the migration process and allow custom developed solutions to be properly migrated and tested by the end users
• The second time, to perform the final migration, after all custom developed solutions are migrated and tested by the end users

This post will cover:

• Upgrade to the target SharePoint 2016 farm

Upgrade to the target SharePoint 2016 farm

IMPORTANT NOTES:

• Migrating from SharePoint 2010 directly to SharePoint 2016 is not supported. To migrate from SharePoint 2010 to SharePoint 2016 we must first migrate to a temporary SharePoint 2013 farm and then migrate to SharePoint 2016
• To to be able to migrate to SharePoint 2016, the temporary SharePoint 2013 farm must at least have the March 2013 Public Update installed. For more details, click here

The migration is performed using the database attach upgrade method (the only supported method to upgrade from SharePoint 2010 to SharePoint 2016 using a database upgrade approach).

In the upgrade process, for both the temporary SharePoint 2013 and the target SharePoint 2016 farms, you should create an empty web application so that a valid SharePoint content database is created. To learn more on how to install a SharePoint 2016 farm (process also valid for SharePoint 2013), click here and here.

After having all custom developed solutions migrated to SharePoint 2016 (if there are any), you should follow the following steps:

• SharePoint 2013: Go to “Manage content databases” in Central Administration, select the web application and then the option “Remove content database”. This will make the web application unattached from any web application in the temporary SharePoint 2013 farm

• SharePoint 2013 Database Server (final migration only): Place the database in read-write mode so that users will be able to change content in the target SharePoint 2016 farm. This can be achieved by the following T-SQL command: ALTER DATABASE <CONTENT_DB_NAME> SET read_write
• SharePoint 2013 Database Server: Backup of the content database(s)

• SharePoint 2013 (final migration only): Go to “Manage content databases” in Central Administration, select the web application, then the option “Add content database” and finally select the name of the content database previously removed. This will make the web application available again in the temporary SharePoint 2013 farm

• SharePoint 2016 Database Server: Copy the database backup file from the temporary SharePoint 2013 database server to the database server that supports the target SharePoint 2016 farm
• SharePoint 2016:  Go to “Manage content databases” in Central Administration, select the web application where you want to migrate to and then the option “Remove content database”. This will make the database unattached from any web application.

• SharePoint 2016 Database Server: Restore the content database backup from the temporary SharePoint 2013 database server. The restore must replace the content database that was created during the SharePoint 2016 installation.

• SharePoint 2016:  If you have custom developed farm solutions, deploy all the migrated WSPs in the target SharePoint 2016 farm.
• SharePoint 2016  Execute the first of a series of PowerShell commands to associate the restored content database to the SharePoint 2016 farm (in this example the web application URL is http://sp2016): Test-SPContentDatabase -Name <Content_DB_Name> -WebApplication http://sp2016
  
  • This PowerShell cmdlet will test the content database against the web application to verify if all customizations referenced within the content database are also installed in the farm
  • In my case, I got some missing features errors but none of them are upgrade blocking

• SharePoint 2016:  Execute the second of a series of PowerShell commands to associate the restored content database to the SharePoint 2016 farm: Mount-SPContentDatabase -Name “<Content_DB_Name>” -DatabaseServer “<DBAlias>” -WebApplication “http://sp2016”
  • This PowerShell cmdlet attaches an existing content database to a web application
  • In my case, no errors or warnings were shown

• SharePoint 2016:  Execute the third of a series of PowerShell commands to associate the restored content database to the SharePoint 2016 farm: Test-SPSite http://sp2016
  • This PowerShell cmdlet runs a series of health checks on the site collection and its contents
  • In my case, I got a warning but once again nothing that is upgrade blocking

• SharePoint 2016:  Execute the fourth of a series of PowerShell commands to associate the restored content database to the SharePoint 2016 farm: Repair-SPSite -identity http://sp2016
  • This PowerShell cmdlet is similar to the Test-SPSite cmdlet but fixes any issues that it finds
  • The result was identical to the Test-SPSite cmdlet: no upgrading blocking issues were found

• SharePoint 2016:  Execute the fifth of a series of PowerShell commands to associate the restored content database to the SharePoint 2016 farm: Upgrade-SPSite http://sp2016 -VersionUpgrade
  • This PowerShell cmdlet will upgrade the site collections associated to the web application to SharePoint 2016 mode. Before this cmdlet was executed, the site collections were still in SharePoint 2013 mode.

After the migration is complete, your SharePoint web application is successfully displayed in your brand new SharePoint 2016 environment!

To read the first part of this two part step by step tutorial, click here.

Related Articles

If you want to convert your tenant’s root classic site into a modern SharePoint site, click here.

To learn why your business should migrate to SharePoint Online and Office 365, click here and here.

If you are a SharePoint administrator or a SharePoint developer who wants to learn more about how to install a SharePoint 2019 farm in an automated way using PowerShell, I invite you to click here and here.

If you want to learn how to upgrade a SharePoint 2013 farm to SharePoint 2019, click here and here.

If you want to learn all the steps and precautions necessary to successfully keep your SharePoint farm updated and be ready to start your move to the cloud, click here.

If you learn how to greatly speed up your SharePoint farm update process to ensure your SharePoint farm keeps updated and you stay one step closer to start your move to the cloud, click here.

If SharePoint 2019 is still not an option, you can learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, click here and here.

If you are new to SharePoint and Office 365 and want to learn all about it, take a look at these learning resources.

If you are work in a large organization who is using Office 365 or thinking to move to Office 365 and is considering between a single or multiple Office 365 tenants, I invite you to read this article.

If you want to know all about the latest SharePoint and Office 365 announcements from SharePoint Conference 2019, click here and here.

If your organization is still not ready to go all in to SharePoint Online and Office 365, a hybrid scenario may be the best choice. SharePoint 2019 RTM was recently announced and if you to learn all about SharePoint 2019 and all its features, click here.

Happy SharePointing!

The post How to upgrade from SharePoint 2010 to SharePoint 2016 Step by Step (Part 2) appeared first on Blog IT.

To read the second part, click here.

Introduction

The SharePoint world is rapidly moving into the Cloud with SharePoint Online and Office 365, but some organizations are still not ready to move completely to Office 365 and SharePoint Online.

Upgrading to SharePoint 2016 or SharePoint 2019 that have support for hybrid scenarios can be a valid solution.

This post is based on upgrading a SharePoint 2010 farm into SharePoint 2016 using the database attach approach but should also be valid if you want to upgrade to SharePoint 2019. This post assumes that the we will only migrate the content database(s) from the source SharePoint 2010 to SharePoint 2016 and all other SharePoint databases are created in the target SharePoint 2016 farm during its installation process.

If you want to learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, click here and here.

There is another valid migration approach to migrate from SharePoint 2010 to SharePoint 2016 by using a content migration. In this approach, the upgrade is not based in a database upgrade process but on content migration and typically a 3rd party solution is necessary to do the content migration. A few 3rd party solutions that can do the job are ShareGate, AvePoint and Metalogix.

Upgrading a SharePoint farm using the database attach approach can be a complex task and the upgrade process is composed by a series of steps:

• Migrating Custom Developed Solutions from SharePoint 2010 to SharePoint 2016 (outside of the scope of this post)
• Upgrade to a temporary SharePoint 2013 farm
• Upgrade to the target SharePoint 2016 farm

IMPORTANT NOTE: In a typical upgrade process, the below steps should be performed twice if there are custom developed solutions:

• The first time, to test the migration process and allow custom developed solutions to be properly migrated and tested by the end users
• The second time, to perform the final migration, after all custom developed solutions are migrated and tested by the end users

This post will cover:

• Migrating Custom Developed Solutions from SharePoint 2010 to SharePoint 2016
  (details about the migration of custom solutions are outside of the scope of this post)
• Upgrade to a temporary SharePoint 2013 farm

Migrating Custom Developed Solutions from SharePoint 2010 to SharePoint 2016

This step is outside the scope of this post but a few notes are important to mention if you have custom developed solutions that you want to migrate from SharePoint 2010 to SharePoint 2016:

• First, you should analyze the source SharePoint 2010 farm and look for custom developed solutions and in particular for farm solutions and/or sandboxed solutions
• If custom developed solutions are found and if you want to take the easiest migration path, you could simply upgrade your custom developed solutions to SharePoint 2016 without changing the architecture. This typically involves migrating server-side code from SharePoint 2010 to SharePoint 2016, possible migration of master pages and adjustments to CSS and JS files
• Despite more difficult, if possible, you should consider migrating the existing solutions to one of the following development models:
  • SharePoint Framework: the latest and the recommended development model for modern SharePoint solutions, enabling an easier migration path to SharePoint Online and Office 365
  • SharePoint Add-Ins: this development model is still supported and can be a valid solution depending on your scenario. However, when possible. you should consider migrating solutions to the SharePoint Framework development model

Upgrade into a temporary SharePoint 2013 farm

IMPORTANT NOTES:

• Migrating from SharePoint 2010 directly to SharePoint 2016 is not supported. To migrate from SharePoint 2010 to SharePoint 2016 we must first migrate to a temporary SharePoint 2013 farm and then migrate to SharePoint 2016
• To to be able to migrate to SharePoint 2016, the temporary SharePoint 2013 farm must at least have the March 2013 Public Update installed. For more details, click here

The migration is performed using the database attach upgrade method (the only supported method to upgrade from SharePoint 2010 to SharePoint 2016 using a database upgrade approach).

In the upgrade process, for both the temporary SharePoint 2013 and the target SharePoint 2016 farms, you should create an empty web application so that a valid SharePoint content database is created. To learn more on how to install a SharePoint 2016 farm (process also valid for SharePoint 2013), click here and here.

After having all custom developed solutions migrated to SharePoint 2016 (if there are any), you should follow the following steps:

• SharePoint 2010 (test migration only): Export all WSPs from the SharePoint 2010 farm to file system. To export the WSP files, you can use this PowerShell script.
  SharePoint 2010 (final migration only): Go to “Manage content databases” in Central Administration, select the web application and then the option “Remove content database”. This will temporarily make the web application unavailable in the source SharePoint 2010 farm

• SharePoint 2010 Database Server (final migration only): Place the database in read-only mode to ensure the source web application is made available again and so that users cannot change content anymore during the upgrade process. This can be achieved by the following T-SQL command: ALTER DATABASE <CONTENT_DB_NAME> SET read_only
• SharePoint 2010 Database Server: Backup of the content database(s) (in read-only mode in the final migration)

• SharePoint 2010 (final migration only): Go to “Manage content databases” in Central Administration, select the web application, then the option “Add content database” and finally select the name of the content database previously removed. This will make the web application available again in the source SharePoint 2010 farm in read-only mode, preventing users from changing any content

• SharePoint 2013 Database Server: Copy the database backup file from the source SharePoint 2010 database server to the database server that supports the temporary SharePoint 2013 farm
• SharePoint 2013:  Go to “Manage content databases” in Central Administration, select the web application where you want to migrate to and then the option “Remove content database”. This will make the database unattached from any web application.

• SharePoint 2013 Database Server: Restore the content database backup from the source SharePoint 2010 database server. The restore must replace the content database that was created during the SharePoint 2013 installation.

• SharePoint 2013:  If you have custom developed farm solutions, add all the exported WSPs (without deploying them) in the temporary SharePoint 2013 farm. For each WSP, run the following command:
  • Add-SPSolution -LiteralPath $location\solution.wsp where $location is the file system location of the WSP files
• SharePoint 2013:  Execute the first of a series of PowerShell commands to associate the restored content database to the temporary SharePoint 2013 farm (in this example the web application URL is http://sp2013): Test-SPContentDatabase -Name <Content_DB_Name> -WebApplication http://sp2013
  
  • This PowerShell cmdlet will test the content database against the web application to verify if all customizations referenced within the content database are also installed in the farm
  • In my case, I got some missing features errors but none of them are upgrade blocking

• SharePoint 2013:  Execute the second of a series of PowerShell commands to associate the restored content database to the temporary SharePoint 2013 farm: Mount-SPContentDatabase -Name “<Content_DB_Name>” -DatabaseServer “<DBAlias>” -WebApplication “http://sp2013”
  • This PowerShell cmdlet attaches an existing content database to a web application
  • In my case, I got an error that once again was not upgrade blocking. This cmdlet is very likely to throw an error but most times it is an error that will not block the upgrade process

• SharePoint 2013:  Execute the third of a series of PowerShell commands to associate the restored content database to the temporary SharePoint 2013 farm: Test-SPSite http://sp2013
  • This PowerShell cmdlet runs a series of health checks on the site collection and its contents
  • In my case, I got a warning but once again nothing that is upgrade blocking

• SharePoint 2013:  Execute the fourth of a series of PowerShell commands to associate the restored content database to the temporary SharePoint 2013 farm: Repair-SPSite -identity http://sp2013
  • This PowerShell cmdlet is similar to the Test-SPSite cmdlet but fixes any issues that it finds
  • The result was identical to the Test-SPSite cmdlet: no upgrading blocking issues were found

• SharePoint 2013:  Execute the fifth of a series of PowerShell commands to associate the restored content database to the temporary SharePoint 2013 farm: Upgrade-SPSite http://sp2013 -VersionUpgrade
  • This PowerShell cmdlet will upgrade the site collections associated to the web application to SharePoint 2013 mode. Before this cmdlet was executed, the site collections were still in SharePoint 2010 mode.

To read the second part of this two part step by step tutorial, click here.

Related Articles

If you want to convert your tenant’s root classic site into a modern SharePoint site, click here.

To learn why your business should migrate to SharePoint Online and Office 365, click here and here.

If you are a SharePoint administrator or a SharePoint developer who wants to learn more about how to install a SharePoint 2019 farm in an automated way using PowerShell, I invite you to click here and here.

If you want to learn how to upgrade a SharePoint 2013 farm to SharePoint 2019, click here and here.

If you want to learn all the steps and precautions necessary to successfully keep your SharePoint farm updated and be ready to start your move to the cloud, click here.

If you learn how to greatly speed up your SharePoint farm update process to ensure your SharePoint farm keeps updated and you stay one step closer to start your move to the cloud, click here.

If SharePoint 2019 is still not an option, you can learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, here and here.

If you are new to SharePoint and Office 365 and want to learn all about it, take a look at these learning resources.

If you are work in a large organization who is using Office 365 or thinking to move to Office 365 and is considering between a single or multiple Office 365 tenants, I invite you to read this article.

If you want to know all about the latest SharePoint and Office 365 announcements from SharePoint Conference 2019, click here and here.

If your organization is still not ready to go all in to SharePoint Online and Office 365, a hybrid scenario may be the best choice. SharePoint 2019 RTM was recently announced and if you to learn all about SharePoint 2019 and all its features, click here.

Happy SharePointing!

The post How to upgrade from SharePoint 2010 to SharePoint 2016 Step by Step (Part 1) appeared first on Blog IT.

Today, after migrating a SharePoint 2010 farm to SharePoint 2016, I suddenly caught an error with the current navigation in a SharePoint Publishing site. The site collection contains three main sub sites. For two of them, SharePoint navigation worked perfectly fine but for the other one, the navigation was not being shown.

The Problem

To try to find out the problem in the problematic sub site, I navigated to the Navigation settings page and caught the following error:

The given key was not present in the dictionary. Stack Trace: at System.ThrowHelper.ThrowKeyNotFoundException() at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at Microsoft.SharePoint.Publishing.CachedArea.CreateResultSetFromSuperUserAndSuperReader(StringCollection superReaderItemIDs, StringCollection superUserItemIDs, Dictionary`2 cachedObjects, SPWeb contextWeb, SPQuery query, List`1 fieldrefs, ICachedObjectFactory objectFactory) at Microsoft.SharePoint.Publishing.CachedArea.GetChildForListByQuery(String listName, SPQuery query, SPWeb contextWeb, Boolean onlyPopulateCache, List`1& itemsFetched, Boolean skipIfThrottled) at Microsoft.SharePoint.Publishing.Navigation.PortalWebSiteMapNode.FetchDynamicItems(PublishingWeb pubWeb, NodeTypes includedTypes, Boolean& websFetched, Boolean& pagesFetched) at Microsoft.SharePoint.Publishing.Navigation.PortalWebSiteMapNode.PopulateNavigationChildrenInner(NodeTypes includedTypes) at Microsoft.SharePoint.Publishing.Navigation.PortalWebSiteMapNode.PopulateNavigationChildren(NodeTypes includedTypes) at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedTypes, NodeTypes includedHiddenTypes, Boolean trimmingEnabled, OrderingMethod ordering, AutomaticSortingMethod method, Boolean ascending, Int32 lcid) at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedTypes, NodeTypes includedHiddenTypes, OrderingMethod ordering, AutomaticSortingMethod method, Boolean ascending, Int32 lcid) at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedHiddenTypes) at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider.GetChildNodes(PortalSiteMapNode node, NodeTypes includedHiddenTypes)

The Solution

To solve the problem, all I had to do was reactivating the “SharePoint Server Publishing”  Site Feature (not the corresponding Site Collection feature) on the problematic sub site:

After reactivating the feature, the navigation started to work as expected.

NOTE: This solution should also be applicable to other versions of SharePoint Server, including SharePoint 2019. To learn more about all the new features in SharePoint 2019, click here.

Hope this helps someone!

Related Articles

To learn why your business should migrate to SharePoint Online and Office 365, click here and here.

If you want to convert your tenant’s root classic site into a modern SharePoint site, click here.

In the meantime, SharePoint 2019 RTM is already out there! If you want to know all about the new features available in the new SharePoint Server release, click here.

If you are a SharePoint administrator or a SharePoint developer who wants to learn more about how to install a SharePoint 2019 farm in an automated way using PowerShell, I invite you to click here and here.

If you want to learn how to upgrade a SharePoint 2013 farm to SharePoint 2019, click here and here.

If you want to learn all the steps and precautions necessary to successfully keep your SharePoint farm updated and be ready to start your move to the cloud, click here.

If you learn how to greatly speed up your SharePoint farm update process to ensure your SharePoint farm keeps updated and you stay one step closer to start your move to the cloud, click here.

If SharePoint 2019 is still not an option, you can learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, click here and here.

If you are involved in a SharePoint upgrade and want to learn more about the upgrade process, click here and here.

If you are new to SharePoint and Office 365 and want to learn all about it, take a look at these learning resources.

If you are work in a large organization who is using Office 365 or thinking to move to Office 365 and is considering between a single or multiple Office 365 tenants, I invite you to read this article

If you want to know all about the latest SharePoint and Office 365 announcements from SharePoint Conference 2019, click here and here.

Happy SharePointing!

The post Fixing the “The given key was not present in the dictionary” navigation error in a SharePoint 2016 farm appeared first on Blog IT.

Introduction

• Downloading and installing SharePoint prerequisites
• Downloading and installing the SharePoint binaries
• Downloading and installing the lastest SharePoint updates
• Downloading and installing the required language packs (optional, necessary if you want the SharePoint interface to be presented in a language other than English)
• Configuring the SharePoint farm using SharePoint Products and Configuration Wizard

• Downloading the SharePoint installation package, click here for more details
• Installing SharePoint and configuring the SharePoint farm

• SharePoint 2010
• SharePoint 2013
• SharePoint 2016
• SharePoint 2019 (to learn more about all the new features in SharePoint 2019, click here)

• 1 SharePoint 2016 Server
• 1 Database Server

Managed Accounts and Pre-Installation Requisites

• To avoid problems executing the AutoSPInstaller script, ensure that the passwords of the above accounts do not contain any special characters (ex: $,%,&,/. etc)
• The above table contains a proposal to name the accounts for the SharePoint installation. If you choose to use different names, ensure that the account names do not exceed 20 characters since NETBIOS names have a limit of 20 characters

Download AutoSPInstaller PowerShell script

Creating the AutoSPInstaller configuration file

• SharePoint version to install
• The SharePoint product key
• The Farm Account and all Managed Accounts and their credentials
• The database instance that will support the SharePoint environment
• The web applications we want to create (ex: Intranet. My Site, etc)
• The service applications we want to enable and their configurations
• Outgoing email settings for the farm
• Database names: this is extremely useful since it allows us to have complete control over the names of all the databases that will be created during the SharePoint farm configuration and avoid having databases with unclear names containing GUIDs which is the default behavior if we configure the farm using SharePoint Products Configuration Wizard (PSConfig)

Installing SharePoint

• Managed accounts credentials will be validated. If any of the credentials is incorrect, the script will stop
• SharePoint prerequisites will be installed
• SharePoint will be installed
• SharePoint language packs will be installed
• SharePoint updates will be installed

Configuring the SharePoint Farm

• Create all managed accounts
• Configure IIS and SharePoint ULS log file paths
• Create the configured web applications (ex: Intranet, My Site)
• Configure the service applications
• Configure outgoing email settings for the farm

Multi-Server Installation

• What is your farm topology and the number of servers you want to consider (WFEs, Application Servers and Database Servers)
• Which services and service applications will be provisioned for each server
• Will you be using MinRoles or will you use a custom installation where you will be manually selecting the services and service applications that will be provisioned for each server?

• Front-end
• Application
• Distributed cache
• Search
• Custom
• Single-server farm
• Front-end with Distributed Cache (merge of Front-end and Distributed cache MinRoles). available with Feature Pack 1 update or later
• Application with Search (merge of Application and Search MinRoles). available with Feature Pack 1 update or later

• Use Remote Installation
• Install SharePoint individually in each SharePoint server

AutoSPInstaller Input File Configuration for Multi-Server Installation Notes when not using MinRoles

• <Custom Provision=” false” />
• <SingleServerFarm Provision=”localhost ” />

• <Custom Provision=”localhost” />
• <SingleServerFarm Provision=”false” />

<ServerRoles>
    <Custom Provision="localhost" />
    <WebFrontEnd Provision="false" />
    <WebFrontEndWithDistributedCache Provision="false" />
    <SingleServerFarm Provision="false" />
    <Search Provision="false" />
    <Application Provision="false" />
    <ApplicationWithSearch Provision="false" />
    <DistributedCache Provision="false" />
</ServerRoles>

Remote Installation

Install SharePoint individually in each SharePoint server

• SharePoint bits must be installed on all servers but farm configuration must only be done once all servers have the SharePoint bits installed. You may Install the SharePoint bits (all steps before the “Configuring the SharePoint Farm” in this post) in all servers at the same time but you must stop the installation process once you are asked to continue with farm configuration
• After the SharePoint bits are installed on all servers, you may proceed to the “Configuring the SharePoint Farm” section of this post BUT this must be done server by server, one at a time, sequentially. The AutoSPInstaller configuration file will determine what services and service applications are going to be provisioned on each server:
  • When you run the farm configuration in the first server, the farm will be created and the services and service applications that are configured to run on that server will be provisioned
  • When you run the farm configuration on the other servers, each server will be added to the farm and the services and service applications that are configured to run on that server will be provisioned

Related Articles

The post How to install a SharePoint 2016 farm using PowerShell and AutoSPInstaller Step by Step (Part 2) appeared first on Blog IT.

To read the second part, click here.

Introduction

Before installing a SharePoint 2016 farm, it is important to be familiar with its requirements. To learn more about SharePoint 2016 hardware and software requirements, click here.

Installing a SharePoint farm can be a complex task and the installation process is composed by a series of steps:

• Downloading and installing SharePoint prerequisites
• Downloading and installing the SharePoint binaries
• Downloading and installing the lastest SharePoint updates
• Downloading and installing the required language packs (optional, necessary if you want the SharePoint interface to be presented in a language other than English)
• Configuring the SharePoint farm using SharePoint Products and Configuration Wizard

All the above steps are time consuming and can be error prone if, for example, you miss to download any of the prerequisites.

Fortunately, it is possible to fully automate a SharePoint farm installation using PowerShell by using a script called AutoSPInstaller. The installation process can be divided in two major steps:

• Downloading the SharePoint installation package
• Installing SharePoint and configuring the SharePoint farm

This process can be used for the following versions of SharePoint:

• SharePoint 2010
• SharePoint 2013
• SharePoint 2016
• SharePoint 2019 (to learn more about all the new features in SharePoint 2019, click here)

In this post, I will talk about the first part of the process: downloading the SharePoint installation package and I will use SharePoint 2016 as an example.

Downloading the SharePoint installation package

The download process will be managed by a script called AutoSPSourceBuilder that will download the SharePoint installation package and all its dependencies and will create a folder structure ready to be used in AutoSPInstaller. The AutoSPSourceBuilder script will download:

• All SharePoint prerequisites
• The latest SharePoint updates
• If specified. the desired language pack

To download the SharePoint 2016 installation package, follow the steps below:

1. Download SharePoint 2016.

2. Download AutoSPSourceBuilder. After download, the folder should contain the following structure.

3. Mount the .iso image of SharePoint 2016.

After mount, the mounted drive will have SharePoint installation files.

4. Run the following script in a PowerShell window (run as administrator).

.\AutoSPSourceBuilder.ps1 -GetPrerequisites $true -SharePointVersion “2016” -Languages “pt-pt”

This script will download SharePoint 2016 with all prerequisites and the Portuguese language pack. Change the “Languages” parameter to the Language Pack you want to include in your installation.

The script will start by detecting the SharePoint image that was previously downloaded. If successfully detected, it will extract the SharePoint installation files from the mounted image to the C:\SP\2016 folder.

5. Once the SharePoint installation files extraction is completed, you will be asked to select the SharePoint update that you want to include on your installation package. Select the latest available package (all SharePoint 2016 updates are cumulative and include all updates contained in the previous updates).

6. After selecting the SharePoint update, the script will resume and start downloading the SharePoint prerequisites. the selected language pack and the selected SharePoint update.

7. After completion, the PowerShell window should look like the image below.

The end result will be a structure of folders and files that will contain all the necessary files to install SharePoint with AutoSPInstaller.

Root folder:

Language Packs folder:

SharePoint bits folder (slipstreamed installation structure):

Updates folder:

To read the second part of this two part step by step tutorial, click here.

Related Articles

To learn why your business should migrate to SharePoint Online and Office 365, click here and here.

If you want to convert your tenant’s root classic site into a modern SharePoint site, click here.

AutoSPInstaller is also already available for the recently announced new version SharePoint, SharePoint 2019. To learn more about all the new features in SharePoint 2019, click here.

If you are a SharePoint administrator or a SharePoint developer who wants to learn more about how to install a SharePoint 2019 farm in an automated way using PowerShell, I invite you to click here and here.

If you want to learn how to upgrade a SharePoint 2013 farm to SharePoint 2019, click here and here.

If you want to learn all the steps and precautions necessary to successfully keep your SharePoint farm updated and be ready to start your move to the cloud, click here.

If you learn how to greatly speed up your SharePoint farm update process to ensure your SharePoint farm keeps updated and you stay one step closer to start your move to the cloud, click here.

If you want to learn how to upgrade a SharePoint 2010 farm to SharePoint 2016, click here and here.

If you are new to SharePoint and Office 365 and want to learn all about it, take a look at these learning resources.

If you are work in a large organization who is using Office 365 or thinking to move to Office 365 and is considering between a single or multiple Office 365 tenants, I invite you to read this article.

If you want to know all about the latest SharePoint and Office 365 announcements from SharePoint Conference 2019, click here and here.

Happy SharePointing!

The post How to install a SharePoint 2016 farm using PowerShell and AutoSPInstaller Step by Step (Part 1) appeared first on Blog IT.

Today i will talk about Publishing Features!!! During this afternoon I was trying to activate Publishing Features but i wasn’t having success because Page Library not was created on activation! So there are more than two Publishing Feature that we need have in consideration, it’s not enough Activate Publishing Infrastructure Feature and Publishing Feature. If you want activate all Publishing Features you can do it pragmatically or using Powershell script:

SharePoint Server – Powershell:

 
Disable-SPFeature –identity 'publishingSite' -URL http://server/ -force
Disable-SPFeature –identity 'PublishingResources' -URL http://server/-force
Disable-SPFeature –identity 'Publishing' -URL http://server/ -force
Disable-SPFeature –identity 'PublishingLayouts' -URL http://server/ -force
Disable-SPFeature –identity 'publishingweb' -URL http://server/ -force

Enable-SPFeature –identity 'publishingSite' -URL http://server/ -force
Enable-SPFeature –identity 'PublishingResources' -URL http://server/ -force
Enable-SPFeature –identity 'Publishing' -URL http://server/ -force
Enable-SPFeature –identity 'PublishingLayouts' -URL http://server/ -force
Enable-SPFeature –identity 'publishingweb' -URL http://server/ -force

SharePoint Online – Powershell:

 
Disable-SPOFeature –Identity "F6924D36-2FA8-4f0b-B16D-06B7250180FA" -Scope Site
Disable-SPOFeature –Identity "AEBC918D-B20F-4a11-A1DB-9ED84D79C87E" -Scope Site
Disable-SPOFeature –Identity "22A9EF51-737B-4ff2-9346-694633FE4416" -Scope Web
Disable-SPOFeature –Identity "D3F51BE2-38A8-4e44-BA84-940D35BE1566" -Scope Site
Disable-SPOFeature –Identity "94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB" -Scope Web

Enable-SPOFeature –Identity "F6924D36-2FA8-4f0b-B16D-06B7250180FA" -Scope Site
Enable-SPOFeature –Identity "AEBC918D-B20F-4a11-A1DB-9ED84D79C87E" -Scope Site
Enable-SPOFeature –Identity "22A9EF51-737B-4ff2-9346-694633FE4416" -Scope Web
Enable-SPOFeature –Identity "D3F51BE2-38A8-4e44-BA84-940D35BE1566" -Scope Site
Enable-SPOFeature –Identity "94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB" -Scope Web

Also that you can activate Programmatically:

 

        private void ActivatePublishingFeatures(SPWeb web, SPSite site)
        {
            // Publishing Site
            string sharePointPublishingSite = "f6924d36-2fa8-4f0b-b16d-06b7250180fa";
            Guid sharePointPublishingSiteGuid = new Guid(sharePointPublishingSite);

            if (site.Features[sharePointPublishingSiteGuid] == null)
            {
                site.Features.Add(sharePointPublishingSiteGuid, true);
            }

            // Publishing Resources
            string sharePointPublishingResources = "aebc918d-b20f-4a11-a1db-9ed84d79c87e";
            Guid sharePointPublishingResourcesGuid = new Guid(sharePointPublishingResources);

            if (site.Features[sharePointPublishingResourcesGuid] == null)
            {
                site.Features.Add(sharePointPublishingResourcesGuid, true);
            }

            // Publishing
            string sharePointPublishing = "22a9ef51-737b-4ff2-9346-694633fe4416";
            Guid sharePointPublishingGuid = new Guid(sharePointPublishing);

            if (web.Features[sharePointPublishingGuid] == null)
            {
                web.Features.Add(sharePointPublishingGuid, true);
            }

            // Publishing Layouts
            string sharePointPublishingLayouts = "d3f51be2-38a8-4e44-ba84-940d35be1566";
            Guid sharePointPublishingLayoutsGuid = new Guid(sharePointPublishingLayouts);

            if (site.Features[sharePointPublishingLayoutsGuid] == null)
            {
                site.Features.Add(sharePointPublishingLayoutsGuid, true);
            }

            // Publishing Web
            string sharePointServerPublishingWeb = "94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb";
            Guid sharePointServerPublishingWebGuid = new Guid(sharePointServerPublishingWeb);

            if (web.Features[sharePointServerPublishingWebGuid] == null)
            {
                web.Features.Add(sharePointServerPublishingWebGuid, true);
            }
        }

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post Activating all Publishing Feature – Programmatically & Powershell – SharePoint 2010, 2013, 2016 & Online: appeared first on Blog IT.

Today i will share a fantastic Google Chrome Extension that you can use on your developments on SharePoint.

A Google Chrome Extension for creating and updating files (js, css), injecting files to sites, modifying web/list propertybag values (add, edit, remove, index) and creating webhook subscriptions, edit/add/remove webparts from publishing pages and run sp-pnp-js typescript snippets in SP2013, SP2016 and SharePoint Online from Chrome Developer Tools.

https://chrome.google.com/webstore/search/speditor

Take a look at  the great introduction video by Jeff Jones!

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SP Editor – Create and update SharePoint Online/SP2013/SP2016 css/js files, inject files to web, manage web properties and list Webhook appeared first on Blog IT.

Today i will show you how can you get internal field names in a SharePoint List Items.
As you know SharePoint have two types of Names – Internal Name and Display Name, it is extremity important when you are developing SharePoint solution get your fields by internal name, the InternalName never changes, you only can change DisplayName, this maintain your solution stable.

So let’s Look some ways to get the Internal Name:

1. Open the List Settings page
2. Under the Columns section, select a column to view the Edit Column page
3. The URL of this page includes the internal name in the query string. For example, the URL for the Created By field includes the following query string List=%7BF641CEF1%2DCDE2%2D49E1%2D9800%2D861A408EF890%7D&Field=Author. The value for the Field parameter, Author, is the internal name for Created By.

You can also apply a sort order on your list view on the column that you want get the internal name, this will generate an URL that contains the Internal Name:

FolderCTID%3D0x012000DDDEBA09D4201845A62AEDBA6A906745-SortField%3DAuthor-SortDir%3DAsc-

Now i will demonstrate how you can get Internal Name by Display Name using SPGetStaticFromDisplay

 

var internalName = $().SPServices.SPGetStaticFromDisplay ({
  listName: "Cars",
  columnDisplayName: "Car Models"
});

Read more: http://sympmarc.com/2015/01/27/get-the-internalname-for-a-sharepoint-list-column/

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint Online – Internal Fields Names & how to use SPServices to get them!!! appeared first on Blog IT.

Today i will talk about List and Library Alerts and how can you get all Active alerts for a specific list using powershell script and how can you disable all alerts.

This is very useful script, when you need move a large list of items on a maintenance routine and you don’t want send a large number of emails/ notifications for users who subscribe alerts, this script help you disable and enable them.

This first PowerShell Script get all SharePoint list alerts with state active.

 

Add-PSSnapin Microsoft.SharePoint.PowerShell –ErrorAction SilentlyContinue

#Variables
$WebURL = "http://YourWebUrl"
$ListName="YourListName"

#Function to Get All Active Alerts on a Given List
Function Get-ListAlerts($WebURL, $ListName)
{
  #Get the Web and List objects
  $Web = Get-SPWeb $WebURL
  $List = $web.Lists.TryGetList($ListName)

  #Get All Alerts created in the list - Which are Active
  $ListAlerts = $Web.Alerts | Where-Object {($_.List.Title -eq $List.Title) -and ($_.Status -eq "ON")}

  foreach($Alert in $ListAlerts)
  {
          write-host "Alert' - $($Alert.Title)' Created for User - '$($Alert.User.Name)'"
  }

 #Dispose web object
 $Web.Dispose()
}

#Call the function Appropriately to Disable or Enable Alerts 
Disable-ListAlerts $WebURL $ListName

 

If you want disable all alerts on this specific list you just need run the following script.

 

Add-PSSnapin Microsoft.SharePoint.PowerShell –ErrorAction SilentlyContinue

#Variables
$WebURL = "http://YourWebUrl"
$ListName="YourListName"

#Function to Disable All Active Alerts on a Given List
Function Disable-ListAlerts($WebURL, $ListName)
{
  #Get the Web and List objects
  $Web = Get-SPWeb $WebURL
  $List = $web.Lists.TryGetList($ListName)

  #Get All Alerts created in the list - Which are Active
  $ListAlerts = $Web.Alerts | Where-Object {($_.List.Title -eq $List.Title) -and ($_.Status -eq "ON")}

  Write-host "Total Number of Active Alerts Found in the list: $($ListAlerts.Count)" 
 
  #Iterate through each alert and turn it OFF
  foreach($Alert in $ListAlerts)
  {
     $Alert.Status="OFF"
     $Alert.Update()
     write-host "Disabled the Alert' $($Alert.Title)' Created for User '$($Alert.User.Name)'"
  }
 
 #Dispose web object
 $Web.Dispose()
}

#Call the function Appropriately to Disable or Enable Alerts 
Disable-ListAlerts $WebURL $ListName

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint – Get all alerts from a specific SP List/Library using Powershell appeared first on Blog IT.

Today i will talk about Storage Metrics in your SharePoint Site Collection!!!

Everyone knows what is the main feature on SharePoint that you could interact with and Structure of SharePoint Site Collections! right!? Site Content and Struct (/_layouts/sitemanager.aspx)!!!

Site Content and Structure page, give you a great overview about all your Site Collection structure. This feature, available since Microsoft Office SharePoint Server 2007, give the capability to navigate dynamically on your site collection hierarchy, it is familiar to Windows Explorer in fact. You can see the site collection hierarchy in the navigation pane as a tree view on the left of the Site Content and Structure page.

But, if you need know more details about storage, probably don’t help you as you expect, so in this case you case access to Storage Metrics (/_layouts/storman.aspx).

Storage Metrics underneath Site Collection Administration, access to your all sub-sites and libraries in SharePoint Online ( also available for SharePoint 2010, SharePoint 2013 and SharePoint 2016) and give you the information about how much storage they are consuming.

It is great!!! Because Storage Metrics allows you to drill down to each site, library and even folder to show a very granular report on your storage consumption, this is very important if you need migrate a large lists or even you are planning an migration between SharePoint Versions without any 3rd Party tool.

Take a Look:

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint Online – Storage Metrics – Monitor storage usage in your Site Collection appeared first on Blog IT.