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 2019 that has support for a hybrid scenario can be a valid solution to allow a gradual move to the cloud.

This post is based on upgrading a SharePoint 2013 farm to SharePoint 2019 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 2013 to SharePoint 2019 and all other SharePoint databases are created in the target SharePoint 2019 farm during its installation process.

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

There is another valid migration approach to migrate from SharePoint 2013 to SharePoint 2019 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 2013 to SharePoint 2019
  (details about the migration of custom solutions are outside of the scope of this post)
• Upgrade to a temporary SharePoint 2016 farm
• Upgrade to the target SharePoint 2019 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 2019 farm

Upgrade to the target SharePoint 2019 farm

IMPORTANT NOTE: Migrating from SharePoint 2013 directly to SharePoint 2019 is not supported. To migrate from SharePoint 2013 to SharePoint 2019 we must first migrate to a temporary SharePoint 2016 farm and then migrate to SharePoint 2019.

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

In the upgrade process, for both the temporary SharePoint 2016 and the target SharePoint 2019 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 2019 farm, click here and here.

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

• SharePoint 2016: 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 2016 farm

• SharePoint 2016 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 2019 farm. This can be achieved by the following T-SQL command: ALTER DATABASE <CONTENT_DB_NAME> SET read_write
• SharePoint 2016 Database Server: Backup of the content database(s)

• SharePoint 2016 (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 2016 farm

• SharePoint 2019 Database Server: Copy the database backup file from the temporary SharePoint 2016 database server to the database server that supports the target SharePoint 2019 farm
• SharePoint 2019: 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 2019 Database Server: Restore the content database backup from the temporary SharePoint 2016 database server. The restore must replace the content database that was created during the SharePoint 2019 installation.

• SharePoint 2019: If you have custom developed farm solutions, deploy all the migrated WSPs in the target SharePoint 2019 farm.
• SharePoint 2019: As a farm administrator, execute the first of a series of PowerShell commands to associate the restored content database to the SharePoint 2019 farm (in this example the web application URL is http://sp2019): Test-SPContentDatabase -Name <Content_DB_Name> -WebApplication http://sp2019
  
  • 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 2019: As a farm administrator, execute the second of a series of PowerShell commands to associate the restored content database to the SharePoint 2019 farm: Mount-SPContentDatabase -Name “<Content_DB_Name>” -DatabaseServer “<DBAlias>” -WebApplication “http://sp2019”
  • This PowerShell cmdlet attaches an existing content database to a web application
  • In my case, no errors or warnings were shown

• SharePoint 2019: As a farm administrator, execute the third of a series of PowerShell commands to associate the restored content database to the SharePoint 2019 farm: Test-SPSite http://sp2019
  • 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 2019: As a farm administrator, execute the fourth of a series of PowerShell commands to associate the restored content database to the SharePoint 2019 farm: Repair-SPSite -identity http://sp2019
  • 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 2019: As a farm administrator, execute the fifth of a series of PowerShell commands to associate the restored content database to the SharePoint 2019 farm: Upgrade-SPSite http://sp2019 -VersionUpgrade
  • This PowerShell cmdlet will upgrade the site collections associated to the web application to SharePoint 2019 mode. Before this cmdlet was executed, the site collections were still in SharePoint 2016 mode.

After the migration is complete, your SharePoint web application is successfully displayed in your brand new SharePoint 2019 environment! The site is presented using the classic site experience, but from now on, you will be able to take advantage of the new modern experiences in your SharePoint 2019 environment!

To download the SharePoint 2019 migration PowerShell files, click here.

To read the first 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 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 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 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.

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 2013 to SharePoint 2019 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 2019 that has support for a hybrid scenario can be a valid solution to allow a gradual move to the cloud.

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

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

There is another valid migration approach to migrate from SharePoint 2013 to SharePoint 2019 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 2013 to SharePoint 2019 (outside of the scope of this post)
• Upgrade to a temporary SharePoint 2016 farm
• Upgrade to the target SharePoint 2019 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 2013 to SharePoint 2019 (details about the migration of custom solutions are outside of the scope of this post)
• Upgrade to a temporary SharePoint 2016 farm

Migrating Custom Developed Solutions from SharePoint 2013 to SharePoint 2019

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 2013 to SharePoint 2019:

• First, you should analyze the source SharePoint 2013 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 2019 without changing the solution architecture. This typically involves migrating server-side code from SharePoint 2013 to SharePoint 2019, 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 2016 farm

IMPORTANT NOTES:

• Migrating from SharePoint 2013 directly to SharePoint 2019 is not supported. To migrate from SharePoint 2013 to SharePoint 2019 we must first migrate to a temporary SharePoint 2016 farm and then migrate to SharePoint 2019
• To to be able to migrate to SharePoint 2016 and then to SharePoint 2019, the 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 2013 to SharePoint 2019 using a database upgrade approach).

In the upgrade process, for both the temporary SharePoint 2016 and the target SharePoint 2019 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 2019 farm, click here and here.

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

• SharePoint 2013 (test migration only): Export all WSPs from the SharePoint 2013 farm to file system. To export the WSP files, you can use this PowerShell script.
  SharePoint 2013 (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 2013 farm

• SharePoint 2013 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 2013 Database Server: Backup of the content database(s) (in read-only mode in the final migration)

• 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 source SharePoint 2013 farm in read-only mode, preventing users from changing any content

• SharePoint 2016 Database Server: Copy the database backup file from the source SharePoint 2013 database server to the database server that supports the temporary 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 source 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, add all the exported WSPs (without deploying them) in the temporary SharePoint 2016 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 2016: Execute the first of a series of PowerShell commands to associate the restored content database to the temporary 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 warnings 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 temporary 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 temporary 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 temporary 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 temporary 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.

To download the SharePoint 2016 migration PowerShell files, click here.

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 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 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.

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 2013 to SharePoint 2019 Step by Step (Part 1) appeared first on Blog IT.

Recently, a customer reported problems with Search in a SharePoint 2013 farm. Instead of showing search results, the following error was being shown:

The Problem

To diagnose the problem, I opened Central Administration and the Search Service Application page indicated problems with the Index Partition component in the Search Service Application Topology.

To further diagnose the problem, I opened up a PowerShell window (used the option “Run As Administrator” to ensure proper permissions) and executed the following commands:

$ssa = Get-SPServiceApplication -Name “Search Service Application”
Get-SPEnterpriseSearchStatus -SearchApplication $ssa -Detailed -Text

After execution, the result confirmed a problem with the Index Partition, showing the Index component with the Degraded state. According to Microsoft “The reason for the degraded status is typically a transient situation related to a restart or network issues” but from my experience it is not easy to understand why this happens.

The Solution

The solution was composed by two steps:

• Reset the Search Index – this operation will clear all index content but will NOT delete any custom managed properties you may have created in the search service application
• Perform a Full Crawl on Search Content Source to crawl and reindex all your content

Reset the Search Index

To reset the Search Index, I went to the Reset Index page in the Search Service Application in Central Administration and clicked the “Reset Now” button.

To confirm the Index Reset, I clicked “OK” in the popup message.

Perform a Full Crawl on Search Content Sources

After resetting the index, the search index data was deleted and to allow search results to be shown again, we need to perform a Full Crawl on all Content Sources in the farm. To do that, we must go to the Content Sources page in the Search Service Application in Central Administration and for each available Content Sources, select “Start Full Crawl”.

NOTE: If you have more than one Content Source, let the Full Crawl on the previous Content Source finish before starting to Full Crawl the next Content Source.

After the Full Crawl on all Content Sources finished, I returned to Central Administration and the Search Service Application page to check the Search Service Application status. The page now indicates a healthy status for all Search components.

To confirm that the problem is solved, I ran the same commands previously executed in the PowerShell window.

$ssa = Get-SPServiceApplication -Name “Search Service Application”
Get-SPEnterpriseSearchStatus -SearchApplication $ssa -Detailed -Text

After execution, the result confirms that the problem with the Index Partion is solved,
showing an Activate state in the Index component.

After the above steps, SharePoint sites started returning search results again!

Related Articles

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

This solution should be also valid for SharePoint 2016 and SharePoint 2019. If you want to know all about the new features available in the new SharePoint Server release, click here.

To find a solution to a search crawling issue I recently found in a SharePoint 2016 farm, click here.

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

SharePoint 2019 RTM was recently announced! To learn all about SharePoint 2019 and all its features, 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.

Hope this can help someone with the same problem!

Happy SharePointing!

The post How To Fix a Degraded Search Index Partition in a SharePoint 2013 farm 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.

Today i will show you how can you create SharePoint 2016 Service Accounts using PowerShell script following the Best Practices.

The script not only create all the accounts but also create the respectives OU (Organizational Unit):

• SharePoint Accounts
• SQL Accounts

Service Accounts:

Script:

 

$mydom = (get-addomain).distinguishedname 
$password = "pass@word1" | ConvertTo-SecureString -AsPlainText -Force 

$ouNameSP = "SharePoint Accounts"
$oudnSP = "OU=$ounameSP,$mydom" 

$ouNameSQL = "SQL Accounts" 
$oudnSQL = "OU=$ounameSQL,$mydom" 

#----------------------------> Organizational Unit <---------------------------- 

New-ADOrganizationalUnit -Name $OUNameSP -Path $mydom 
Write-Host "OU $OUNameSP Created" -foregroundcolor green 

New-ADOrganizationalUnit -Name $OUNameSQL -Path $mydom 
Write-Host "OU $OUNameSQL Created" -foregroundcolor green 

#-----------------------------> SharePoint 2016 <-------------------------------

$usersArraySP = @("SP_Farm","SP_Admin","SP_Pool","SP_Services","SP_Crawl","SP_Search",
                  "SP_UserProfiles","SP_PortalSuperReader","SP_CacheSuperUser","SP_VisioUser",
                  "SP_PerfPointUser","WF_Service","SP_MySitePool","SP_PortalSuperUser")

foreach ($usp in $usersArraySP) {
        New-ADUser -Name $usp -DisplayName $usp -SamAccountName $usp -AccountPassword $password 
        -ChangePasswordAtLogon $false -PassThru -PasswordNeverExpires $true -Path $oudnSP 
        Write-Host "$usp Created" -foregroundcolor green
 }

#----------------------------------> SQL <--------------------------------------
$usersArraySQL = @("SQL_Admin","SQL_Service")

foreach ($usql in $usersArraySQL) {
       New-ADUser -Name $usql -DisplayName $usql -SamAccountName $usql -AccountPassword $password 
       -ChangePasswordAtLogon $false -PassThru -PasswordNeverExpires $true -Path $oudnSQL
       Write-Host "$usql Created" -foregroundcolor green
 }

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint 2016 – Create Service Accounts using PowerShell script appeared first on Blog IT.

Today i’m going to talk about SharePoint Scenarios and what are the main difference between this three types of scenarios and what scenario should be the option for your environment…

So, the three types of architecture scenario that you can have on your SharePoint environment are the following:

What should you choose?! Well in fact there are so many question that you need answered before take an decision!?

It isn’t easy take a decision, let’s analyse what are the main benefits each architecture:

SharePoint On-Premises:

• Private Cloud
• Dedicated environment
• Internally hosted
• Internally managed
• Internal designed

• Migration Flow:

SharePoint Online:

• Public Cloud
• Partially or fully dedicated
• Externally hosted
• Externally or Internally managed
• Internally managed
• Minimal customization

Cloud benefits according to cloud users?

• Increase efficiency (55 %)
• Improved employee mobility (49 %)
• Increased ability to Innovate (32 %)
• Freed current IT staff for other projects (31 %)
• Reduce IT operation costs (25 %)
• Enabled us to offer new products/ services (24 %)

• Migration Flow:

SharePoint Hybrid Solution:

What is Hybrid SharePoint?

“Productivity services in SharePoint Online (Office 365) which are securely integrated with on-premises SharePoint Server 2016 to provide unified functionality and access to data.”

Why considering a Hybrid SharePoint Solution?

• Large existing investments (customized SP deployments w/lots of data and settings,custom solutions, LOB systems, etc…)
• Functionalities I can’t do in the Cloud that i can do on premises;
• Keep Sensitive Data on Premise
• Collaboration with External Partners
• Capacity Flexibility
• Intranet – Extranet
• Geo Location

Same Benefits of Hybrid SharePoint Solution?

SharePoint Business to Business Collaboration: Extranet for Partners with Office 365

“on-premises extranet site involves complex configuration to establish security measures and governance, including granting access inside the corporate firewall, and expensive initial and on-going cost….SharePoint Online, partners connect directly to a members-only site in Office 365, without access to the corporate on-premises environment or any other Office 365 site. Office 365 Extranet sites can be accessed anywhere…”

SharePoint hybrid sites and search

“A hybrid environment can help your company get started in the cloud, taking a first step to explore the cloud functionality at own your pace. It also enables enterprise users to be connected from almost anywhere to the resources and content they need… SharePoint hybrid features, you can consolidate search results between SharePoint Server and Office 365, consolidate user profiles in Office 365, and offload your users’ personal storage to the cloud…”

• Migration/Interactions Flow:

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint Scenarios – Online, On-Premises or Hybrid!? appeared first on Blog IT.