Was a current Prinect backup including the database backup made and completed without errors?

Has a regular backup of the computers in the system environment been made? This also applies to shadow copies of any existing virtual machines.

Has all proof output been completed?

Note: Print jobs that are in an output queue during a product upgrade will be lost. A print job should always be output completely with the same Prinect version.

Are all CTP systems and digital presses controlled by Prinect output software switched on? Did you make sure that no output processes are running?

Are all Prinect operators informed that the Prinect system will not be available during the system upgrade? This also applies to the machine presettings and the production data collection.

Are all operators of the affected computers informed that these computers might reboot more than once during the system upgrade?

Are all user interfaces to be updated closed?

During installation of the upgrade or update packages, currently running instances of the software to be updated, e.g. Prinect Cockpits, will be automatically terminated and the operator notified accordingly. For reasons of safety, we recommend closing all involved Prinect applications before starting the upgrade or update installation so that critical work steps need not be interrupted abruptly because of the update installations. This also applies to Adobe Acrobat, as Acrobat plug-ins may also be included in the update scope.

Is a backup in progress?

If a program such as the Windows Task Scheduler is currently running a system server back up, the PMC cannot start a product update, system upgrade, or cumulative update on that computer.

Is there a valid license for a system upgrade?

To upgrade your system, you must have a valid license for the new product version. The existing license is automatically upgraded to the new version if there is a valid maintenance or subscription contract. If the Prinect software is licensed via online protection, updating the licenses by the Prinect Trust Service is possible automatically. In this case, a "LUX file" is first transferred to the PSC and then to the PMC, which causes the licenses to be updated on the local License Server.

If you experience licensing issues and the updated Prinect components do not start due to missing licenses, check the following: Automatic License Import. For further support, please contact your HEIDELBERG representative.

For general information about online licensing, click this link: Online Licensing Information or in the Online Help of License Manager.