How to upgrade Pronestor Planner On-premise

Introduction and requirements

During the upgrade, Pronestor Planner is taken offline so make sure to schedule it outside business hours or inform your users.
It is important that the .net framework is installed on the server before the upgrade begins, since it requires a restart.
You should always make a backup of the SQL database and the Pronestor Planner installation before you begin.

IMPORTANT - Access to https://license.pronestor.com from the installation server is required. This is required for validating the license. Failing to do this will result in a server error.

Please note: the recommendation below should be read as minimum requirements and should be scaled up for larger setups.

Server - software:

Microsoft server 2012* or newer

Internet Information Service 7.0 or newer
Microsoft .net 4.8 framework or newer
ASP.NET framework 4.8
Message Queuing Service (if connected to Exchange)
* Extended support for Windows Server 2012 and Windows Server 2012 R2 will end on October 10, 2023

Dependencies:

Microsoft SQL 2016 or newer
Microsoft Exchange 2016 CU3 or newer
SMTP sending permissions
It is recommended that the Planner is on a dedicated server and that the SQL server is a separate server from the application server.

Server - Hardware

CPU min. 2.5GHZ (min. 4 CPU cores)
Min. 4 GB RAM (+10MB/per concurrent user)
Min 500 MB disk space for application files
Min 250 MB disk space for database files

The recommendation is only for the Sign In Workspace software (formerly Pronestor), thus not including CPU/memory for OS and Windows Services. Please follow Microsoft's recommendation on this.

We strongly recommend that you establish two environments, one for testing and one for production. When upgrading on premise installations, the test environment will be used for validating the upgrade process as well as for testing the installation and become familiar with new or changed features.

Check the database integrity.

The upgrade can only proceed if the database integrity can be verified.
Run a pronestor tool called diag.aspx, which is located in web site or directory called "Pronestor"
This is done from Internet Information Services (IIS). Go to your site, and make sure it's set to content view. Right click diag.aspx and choose browse.
When you open it, it will ask you to login. Contact the Pronestor team and ask for the diag login.
Scroll down to “Data Integrity” section and Run Integrity Check.
Run “Fix All Checked” after the check has run and confirm all errors are resolved.
There are a few errors that it cannot handle automatically. If you can, you can go to the database and correct them manually and run the diag again. Otherwise, contact helpdesk@pronestor.com for assistence, and abort this guide.
Warning, do not proceed with this guide unless all the errors in diag were fixed!
Close browser once all errors are fixed and proceed.

Unpack the Pronestor files

Warning, do not proceed with this guide unless all the errors in diag were fixed!

It is critical that you stop the application pool before you proceed. Go to IIS, press "Application Pool" and right click.
Press stop.
Go to the server and find the installation folder of your Pronestor installation. In this guide we use the example C:\inetpub\wwwroot\pronestor but it could be anything that you choose when you installed Pronestor the first time.
If you already have an upgrade folder, please delete it.
Now create an upgrade folder and unpack zip file into it.
Open the command promt as an administrator. It is important that it is run as administrator, and not just normally.
In the command promt, go to the upgrade folder and run FULL_UPGRADE.bat
Once that is done, run diag.aspx again. It will update the database to the new version.

If you are updating to version 8.1.22 or newer

After you did the update, but before you open the site, go to the installation path, fx c:\inetpub\wwwroot\yoursitename and delete the folder named App_Code

This is only relevant if you are upgrading from an on-premise version older than 8.1.22. If the App_Code folder isn't there, you can skip this step.

Updating the Outlook add-in

This is done automatically as of version 11.

Updating the Exchange integration module

Stop the application pool for your Pronestor Planner site.
Open the servers Services.msc
Find and stop "ExchangeBookingSyncService"
Go to https://downloads.pronestor.com/
Download Exchange Synchronization Service
Unzip ExchangeBookingSyncService.zip
In the folder ExchangeBookingSyncService, delete the file "ExchangeBookingSyncService.exe.config"
Copy the folder ExchangeBookingSyncService to your install folder. For example "C:\Program Files\proNestor"
Open the servers Services.msc
Find and start "ExchangeBookingSyncService"
Start the application pool for Pronestor Planner again

Roll back

IMPORTANT - Any changes made after the database was backed up and before the rollback will be lost.

Steps involved in a roll back

Stop application pool for Pronestor Web Site
Stop Sync service
Restore database from backup set
Restore files into the web folder from backup of web folder and sync service
(set permissions write permission on license, app_data, content folder in Pronestor folder - for the application pool user)
Restore Sync Service files
Start Sync Service
Start Application pool

Table of contents: