Upgrading WorkPoint 2016 to WorkPoint 2019

Article published on the 4th of January, 2022.

This article will guide you though the upgrading process from WorkPoint 2016 to WorkPoint 2019.

Step 1: Preparing WorkPoint 2016 for upgrade

The first step when upgrading from WorkPoint 2016 to WorkPoint 2019 is to prepare your 2016 version for the upgrade.

To properly prepare WorkPoint 2016 for upgrading, please perform the following actions:

  1. Disable the WorkPoint Buffer Site TimerJob
  2. Delete all buffer sites
    • Use Clear-WPSiteCache <url>
  3. Save the current site collection numerator value (only relevant for multi site collection setups).

Use the following PowerShell script to get the current site numerator value (remember to substitute <root site url> with the root of your WorkPoint root site url):

$s = Get-SPSite <root site url>
$wa = $s.WebApplication
$key = "WP_CURRENT_SITE_ID" + $s.ID
$numeratorValue = $wa.Properties[$key]
  1. Remove all deleted sites in the recycle bin and deleted sites collections from the content database.
  2. Remove all orphan sites from the site collections within the content database, e.g. sites with no linked entity.

Step 2: Attach content databases

Next, perform the following step:

  1. Attach the content database from 2016 to the 2019 farm where WorkPoint is already deployed. If WorkPoint is not deployed, please follow the guide for setting up a WorkPoint solution. If the WorkPoint 2016 solution uses multiple content databases, all databases must be attached to the 2019 farm.

Note: With the attached databases, the farm administrator MUST have the db.owner role. If this is not the case, you will corrupt the database.

Also note: The upgrade log will contain issues with missing WorkPoint assembly and setup files. This will be resolved in the next step of this article.

Step 3: Upgrade solution to WorkPoint 2019

In this step you will upgrade your solution to WorkPoint 2019.

  1. Open Windows Power Shell in Administrator mode.
  2. Run the WorkPoint Cmdlet Update-WPVersion<url>

The output of the Cmdlet should show various updates being applied:

If this not the case, please ensure that you have a web property on your WorkPoint root web (Replace "http://workpoint" with your WorkPoint root site url in the examples below) called "WorkPointVersion" and it is in the interval ->

If that is not the case, either add it if it is missing, or update it to “” and run the command again:

Adding new

Updating existing

  1. Set the site collection numerator value by running the following script (remember to substitute <root site url> with the root of your WorkPoint root site url):
$s = Get-SPSite <root site url>
$wa = $s.WebApplication
$key = "WP_CURRENT_SITE_ID" + $s.ID
$wa.Properties[$key] = <the value extracted from the 2013 WebApplication>
  1. Run Set-WPRegEdit -Url <url> on reach Frontend server and restart them.

Step 4: Test Content Database on SharePoint 2019

  1. For the final step, please run Test-SPContentDatabase on all WorkPoint content databases and verify that all issues are resolved. If any issues persist, they should be resolved manually.
Have more questions? Submit a request