Before you begin, clear up as much space on the server as possible because temp files and log files generated during the upgrade could potentially use up all your drive space, which would prevent the upgrade from finishing.
Have at least the size of your database (or more) free to eliminate possible issues.
Refer to the database in c:\program files\MySQL\MySQL server 5.5\data/ibdata1.
The log files are located at c:\inetpub\logs\Log Files\W3SVC1.
Before you start the upgrade, back up your database and web files (just in case). If you can take a snapshot of the server, then that is also recommended because the snapshot is the easiest way to restore the server if anything happens.
While the upgrade does not take long, the database backup can take a while depending on the size of your PrinterLogic database.
Clear out any old backups from your server. These backups are located in c:\ program files \Printer Properties Pro\Printer Installer\Backups\database.
When doing an update for a major release (17.1, 18.2, etc.), the recommended best practice is that you perform an advanced upgrade rather than a standard upgrade.
An upgrade provides the option to auto-upgrade the client at the same time you are upgrading PrinterLogic. If you decide to upgrade the client at another time, open the Admin Console, and click Tools > Settings > Client. In the Client Update section, click Enable automatic update during the next client check-in or refresh.
Older versions of the client will work with new versions of PrinterLogic on the server. However, the recommended best practice is to use the most recent version of the client as well.