Will my KWizCom products continue to work if I upgrade to SharePoint 2016?
KWizCom is upgrading its SharePoint add-ons to SharePoint 2016 to enable our customers to keep using our add-ons after they upgrade their SharePoint environment.
If you have an annual support plan, you can download the new product version for SharePoint 2016 from our web site and install it on your SharePoint 2016 server. Please make sure you have renewed your product's annual support plan so you'll be able to install the new product version for SharePoint 2016.
If you haven’t already, be sure to contact our sales department at email@example.com or 905-370-0333 ext 104 to renew your support plan.
If you are upgrading from SharePoint 2010 or earlier version, you must first must complete the SharePoint 2013 upgrade process before moving to SharePoint 2016.
- You cannot upgrade from SharePoint 2010 or earlier version directly to SharePoint 2016
- There is no need to install the backward compatible packages on the 2013 server *if* you do not defer any sites to SharePoint 2010 UI and plan to finish the upgrade on all sites to SharePoint 2013 UI
If you have already completed the SharePoint 2013 upgrade process or never had to upgrade your KWizCom solution to SharePoint 2013, at that point you will not need to install the backward compatible packages on SharePoint 2016. Please follow the instructions below to upgrade your KWizCom solution to SharePoint 2016.
This article will help you understand how the process of upgrading KWizCom products from SharePoint 2013 to SharePoint 2016 works. The recommended approach by Microsoft for upgrading a SharePoint site collection is the database-attach method. The entire upgrade process is clearly outlined by the following article on TechNet:
But the section most pertinent to KWizCom products doesn’t come until later in the process in the Upgrade Databases section:
This article assumes that you have already performed these initial steps:
2 Upgrade your KWizCom products on SharePoint 2010
On your SharePoint 2013 environment, upgrade all KWizCom products and Foundation to the latest SharePoint 2013 version. This will ensure all product features and fixes are up to date with the latest versions.
NOTE: If you have installed KWizCom backward compatibility packages for your migration KWizCom product upgrade from SharePoint 2010 to 2013, please uninstall these packages because they are no longer needed in SharePoint 2016
Instructions to install/upgrade KWizCom products and foundation versions is outline in this KB article: http://support.kwizcom.com/KnowledgebaseArticle50001.aspx
2.1 Verify that all products work correctly
Once you have finished upgrading, please verify that all KWizCom products work correctly. If the products do not work correctly, please contact KWizCom Support at firstname.lastname@example.org to help resolve your issue.
3 Install your KWizCom products on SharePoint 2016
On your SharePoint 2016 environment, Install all KWizCom products and Foundation to the latest 2016 version. The product version numbers should match the ones you installed on SharePoint 2013 in section 2.
Ex: If you Installed “KWizCom SharePoint List Aggregator web part 2013 v14.4.03.wsp” on SharePoint 2013, then you need to install “KWizCom SharePoint List Aggregator web part 2016 v14.4.03.wsp” on SharePoint 2016.
4 Upgrade Content Databases
This section outlines what has to be done at each step in the Upgrade Content Databases to 2016 section:
4.1 Create Web Application
There are no KWizCom specific instructions for this step other than to make sure that when you create the web application it uses the same URL as the source SharePoint 2013 web application. Some KWizCom products use the existing web application URL to find resources that are critical to the product functionality.
4.2 Reapply Customizations
You will now have to deploy the 2013 version of KWizCom Foundation and all KWizCom products to the target web application that were installed in the source SharePoint 2010 web application.
4.3 Verify Custom Components
In this step you are responsible for determining which KWizCom products have not been deployed to the target web application but are present in the content database. The PowerShell “Test-SPContentDatabase” command will enumerate all files, features and web parts that are present inthe content database but not deployed to the target.
If any KWizCom files, features or web partsare missing, please make sure that pertinent KWizCom product is deployed to thetarget web application. At this point in the upgrade it is the 2010 version ofthe KWizCom product that must be deployed to the target web application or the “Test-SPContentDatabase”command will report errors.
4.4 Attach a content database to a web application and upgrade the database
There are no KWizCom specific instructions for this step. As long as all the previously deployed KWizCom products are installed you should now be able to use KWizCom products inside the target web application.
5 Visually Upgrade Site Collections
Once you have verified that your site collections are working correctly in 2013 computability mode you can begin to follow this guideline to upgrade your site collections to SharePoint 2016 visual UI:
At this point you should be able to use the KWizCom products on site collections with the SharePoint 2016 UI.
6 Update product license
After you've done an attach database upgrade from SharePoint 2013 to SharePoint 2016, follow these steps to get your KWizCom product activation codes for SharePoint 2016:
1. Deactivate your KWizCom product activation key on your SharePoint 2013 environment by using the deactivation page: /support/product-deactivation/
2. Get your activation key for your SharePoint 2016 product from KWizCom, by using the activation page: /support/product-activation
3. Use your new activation key to activate your KWizCom product on SharePoint 2016
If you need assistance with your activation, please contact our activation department email@example.com
Optionally provide private feedback to help us improve this article...
Thank you for your feedback!