Menu "View" > "Software Update"

In this view you will carry out the actual updates. Furthermore, you can manage update groups in this view by adding computers to an update group that are independent of the system or by removing them.

Note: If Task Scheduler performs a data backup of the Prinect System, you will not be able to start a Product Update or System Upgrade via the PMC.

Note: A Windows update will be disabled automatically prior to the Prinect installation and enabled after installation is complete. This is to ensure the installation processes started by PMC will not fail.

Description of the icons used

"Software Update" > Navigation Pane

Structure of the navigation pane (section on left)

You can maintain computers in the navigation pane on the left. This is where you select the comput­ers or systems for an update. You can group computers to update groups to update them together. In addition, you can set up custom computer groups.

The elements that make up the navigation pane in detail

•"Computer": All the computers listed in "Computer" are standalone computers or movable com­puters. In this context, movable means that these computers can be moved to a system group or a user-defined group and vice versa. This is done using the context menu > "Move".

•"System/System group": All the computers listed in a system are part of this system. A differ­ence must be made between movable (see above) computers and computers that are perma­nent in the system.

You cannot remove computers that are permanent in the system from the system group. These computers are entered in a system file and are also linked to the system through the Prinect Supervisor. The "Move" function does not display in the context menu for these computers.

Movable computers are all computers located in "Computer". Computers in a system can also be movable. You can remove these computers from the system group with "Move" in the context menu and move them either to "Computer" or to a user-defined computer group.

The color of the computer icons differs, depending on whether or not the computers are mem­bers of the system group, see Description of the icons used .

•User-defined computer group: To set up a group with computers, click the "+" sign beside "Soft­ware Update". You can give the group any name, but it may not contain one of the following characters: "%'*;<>?^`{|}~/\". All movable computers from all systems and from "Computer" are presented to you in this group. The group must have at least one computer. If not, it will not be created or will be automatically deleted when the last computer is removed from it.

This grouping function gives you the option of removing Cockpit clients temporarily from a sys­tem and compiling them to a group. This often has benefits if you want to split up a system update into the time-consuming server update and the update of the clients. You can then con­tinue working on the clients during the server update. After the server update, you can move the clients back to the system and trigger another update of the whole system to now update the clients as well.

•"Subsystems": If applicable, the installed Supervisors will automatically split a Workflow System into a Main System and one or several Subsystems. By splitting the Workflow System, it is pos­sible to perform updating not as a whole but step by step.

Note: When doing so, please note that you must always update the Main System first before you can start updating the Subsystems.

The advantage: if a Workflow System comprising a Prinect System and imagesetters and printing presses is split into Main Systems and Subsystems, you can first update the Prinect System (Main System) without having to stop imagesetters and printing presses. The connected image­setters and printing presses (Subsystems) can then be updated individually. This reduces the machine downtimes.

The Main System comprises the system computer of the Workflow System on which the Super­visor Master is usually running, and the computers with Supervisor Slave connected to this Supervisor Master. In addition, the main system contains those computers of the workflow sys­tem that were connected to each other via the Prinect Cockpits.

The Subsystems comprise the Computers with the other Supervisors. Each computer with a Supervisor Master forms a Subsystem with those computers having a Supervisor Slave allocated to this Supervisor Master.

You can manually include subsystems in a main system and also exclude them again from a main system. For this purpose, the context menu of the Main System or Subsystem offers the following functions:

·Context menu of the Main System > "Restore Subsystems": This function will perform the division into Main System and Subsystem again. Free computers that may have been present in a Subsystem beforehand will remain in the Main System.

·Context menu of the Subsystem > "Dissolve Subsystem": With this function, the Subsys­tem will become part of the Main System again. This is possible only if Main System and Subsystem are of the same Workflow Type (e.g. Prinect Integration Manager, Prinect Dig­ital Print Manager etc.).

Update group

Usually, you select a system for the update and this is then the update group. A system is not always identical to the update group because movable computers can be removed from a system and/or added to it.

For the terms "computer" and "system", see also Update group, Computer and System / System Group .

Display of the views in the main pane

When you left-click the header of a system, a computer or a user-defined computer group, you can view the related view of the main pane.

Context Menu of a Computer

In the context menu of a computer you have the following options:

•"Send Message": This function lets you send messages to all computers you select in the context menu. In this way, you can inform about a pending update or upgrade, for example. The relevant computers are pre-selected, depending on the computer or system from which you invoke the function. All active computers are pre-selected if you invoke the function with the "Extras" menu > "Send Message". You cannot select computers that are not accessible.

•"Show Prinect Supervisor": You can select this option only if a Master Supervisor is running on the selected computer. Clicking this option will open the Supervisor view for the selected com­puter.

•"Show Inventory": Click this menu item to call up the inventory of this computer in the main pane. This will open the "Computer" view, refer to Menu "View” > "Computer Inventory" .

•"Remove from Maintenance Center": This means that a computer no longer displays in the nav­igation pane and is no longer supplied with update packages by the PMC.

You can only remove movable computers that strictly speaking are not part of a system as such (see System / System Group ). These computers have a yellow icon, . The com­puter on which the PMC is running is an exception to this. In other words, this computer may never be removed.

•"Move": This function lets you move movable computers between "Computer", "System" and the user-defined computer groups. See also Structure of the navigation pane (section on left).

•"Verify Login Data": Prior to running a product update or a system upgrade, the login data will be verified, possibly for two different user accounts. The product update or system upgrade starts only after the correct login data are set. The login data must be correct for all computers involved in the product update or system upgrade. This feature lets you verify the login data before installation.

Clicking "Verify Login Data" while the computer is in a system will cause all the computers of the system to be verified. If the computer is a standalone computer, only the login data on this com­puter are verified.

Click "Verify Login Data". The "Verify Login Data" dialog appears. In this dialog you can enter a user name and password and start the verification. A result displays for each computer in a sys­tem. "Failed" means that the login data for this computer are not correct. With the button "Repeat", you can repeat the verification with different login data.

See also Checking the User Privileges for a Product Update or System Upgrade.

•"Create service report": The service report is used to document and communicate the system situation in case of PMC software errors.

You can select the computers to include in the service report in the "Service Report" dialog. If you invoke this function from the context menu of a system group computer, all computers of this system group will be selected by default. If you invoke this function from the context menu of a computer that is not part of the system group, only this computer will be selected by default. You cannot start the service report if inaccessible computers (red tag) are selected.

Only those files that were created or modified after the date in the date field will be taken into account. Once the report has been generated successfully, you can download it to your local computer with "OK". You can press "Download" to download the latest report archive once again.

A report generation in progress will continue even if you close this dialog with "Close dialog".

Note: If the PMC no longer responds, you can nevertheless use the URL
"http://PMC_computer:port_number/report" entered in a browser to create a service report (in most cases, the port number is 65200).

•"Update Information about Pending Operating System Updates": A system upgrade or product update can be severely hampered by a pending operating system update or a pending computer restart, and vice versa. For this reason, we recommend updating the information regarding pending OS updates and performing any pending OS updates or reboots prior to updating.

Otherwise, the following processes will apply:

·Product update: The dialog "Pending Operating System Updates and Computer Restarts" may appear after installation was started. (This dialog does not display if only computers with service tools are included in the job that do not support the operating system update and computer restart functions). Before you can start the installation of a product update, this dialog checks for pending operating system updates and computer restarts. You can cancel the check and continue the installation by setting the "Skip" option and then clicking "Next". We do not recommend this in most cases. If operating system updates and/or computer restarts are pending, you can run them yourself and then recheck with "Repeat Check". Click "Cancel" to cancel a product update at any time.

·System Upgrade: Step 2 of the System Upgrade Assistant warns you and checks whether an operating system update or a computer restart is pending. If this is the case, you can take the necessary action and repeat step 2 or explicitly ignore the warning using the "Ignore" option.

Context Menu of Headers Computer/System

•"Send Message": This function lets you send messages to all computers you select in the context menu. In this way, you can inform about a pending update or upgrade, for example. The relevant computers are pre-selected, depending on the computer or system from which you invoke the function. All active computers are pre-selected if you invoke the function with the "Extras" menu > "Send Message". You cannot select computers that are not accessible.

•"Show Prinect Supervisor": You can select this option only if a Master Supervisor is running on the system computer of the selected system or subsystem. Clicking this option will open the Supervisor view for the system computer. (For the term "System Computer", see System Computer .)

•"Rename Group": Renames a custom computer group.

•"Delete Group": Deletes a custom computer group.

•"Move Movable Computers to": Lets you move movable computers. The context menu offers the following targets: "Computer" as a pre-defined group of movable computers, a group of movable computers you may have set up yourself, a system or a subsystem that may be present.

•"Add Movable Computers from": Lets you add movable computers. The context menu offers the following sources: "Computer" as a pre-defined group of movable computers, a group of mov­able computers you may have set up yourself, a system or a subsystem that may be present.

•"Restore Subsystems": This function will perform the division into Main System and Subsystem again. Free computers that may have been present in a Subsystem beforehand will remain in the Main System. ("Subsystem" see also The elements that make up the navigation pane in detail.)

•"Dissolve Subsystem": With this function, the Subsystem will become part of the Main System again. This is possible only if Main System and Subsystem are of the same Workflow Type (e.g. Prinect Integration Manager, Prinect Digital Print Manager etc.). ("Subsystem" see also The elements that make up the navigation pane in detail.)

•"Update Information about Pending Operating System Updates": See the item with the same name in the context menu of a computer, "Update Information about Pending Operating System Updates": A system upgrade or product update can be severely hampered by a pending operating system update or a pending computer restart, and vice versa. For this reason, we recommend updating the information regarding pending OS updates and performing any pending OS updates or reboots prior to updating. .

"Software Update" > Main Pane

Note: Before a product update or system upgrade, make sure that the update packages to be installed are valid and complete at the time of installation.
If you want to start a product update or system upgrade and the request for new update packages is more than two hours ago, a warning message appears. You are prompted to click the "Open Status Dialog of Heidelberg Connection" button and start a software comparison in the "Status of Heidelberg connection" dialog with "Search for New Software".

Note: If the Windows Task Scheduler is running a data backup of the Prinect System, you will not be able to start a product update or system upgrade via the PMC.

The view in the main pane changes according to the update status of the selected system/computer.

View in Main Pane: "System Upgrade Available"

In this section, we describe the situation when a system upgrade is available for installation. The cap­tion of the main pane displays the message "System Upgrade Available" and the button "Start System Upgrade Assistant" as soon as a system upgrade is available.

At the same time, you can choose whether or not to install product updates that may exist for the currently installed master version, and either the message "Product Update Available" or "No product update available" appears. If product updates are available, you can install these irrespective of the system upgrade; see also View in Main Pane: "Product Update Available" .

Prerequisites: You will need new licenses to upgrade your system. An automatic license import must have been run for this.
The license information about the products you purchased is to be processed automatically so that manual licensing actions are unnecessary prior to an automatic system upgrade.
Using a LUX file, the PSC automatically transfers the license information to the PMC that processes and submits the processed information to the License Server. An automatic system upgrade is possi­ble only if the respective license keys for the new version were transferred to the License Server and saved there. If errors should occur, please refer to Automatic License Import.

Prerequisites: The following minimum prerequisite for running a system upgrade applies: the minimum software versions of all the computers in the selected system group are equal to or later than the minimum software version required for the system upgrade.

Note: We recommend terminating all affected Prinect applications and Adobe Acrobat on all computers involved prior to starting a product update or system upgrade.

Note: A system upgrade can be severely hampered by a pending operating system update or a pending computer restart, and vice versa. That is why step 2 of the System Upgrade Assis­tant warns you and checks whether an operating system update or a computer restart is pending. If this is the case, you can take the necessary action and repeat step 2 or explicitly ignore the warning using the "Ignore" option.

System Upgrade to the Version After Next

•System upgrades up to and including version 2018.00:

To run a system upgrade to the version after next, you must first run a system upgrade to the version in between. For example, to run a system upgrade from version 2016 to version 2018, you must first run a system upgrade to version 2017. To save time in this case, only those product updates that are absolutely necessary are installed for the version in between. This is an auto­matic process that cannot be disabled. The intermediate and also the target version will be indi­cated. Although further product updates for the version in between are shown, these do not have to be installed for a system upgrade to the target version.

•System upgrades from version 2018.00 onward:

First of all, we make a difference between series version and series production status, see table below:

From version 2018.00 onward, a system upgrade can run automatically to the series version after next without having to jump manually to the versions in between. A series version can always be skipped. The version jumps can be as indicated in this matrix:

For example, as the matrix shows, you can upgrade your system to the target version 2020.10 from the installed versions 2018.00, 2019.00, 2019.10 and 2020.00. These must be started and running.

Depending on the Prinect version you are upgrading the system from, you must also follow the relevant documentation for the version releases in between. You can find this documentation here.

View in Main Pane: "No update available"

This section describes the situation of neither a system upgrade nor a product update being available for the system selected in the navigation pane. This means your system is up to date.

You see the Heidelberg Prinect products installed on the selected system, with installation date, basic version and current version (see Basic Version and Current Version for a description of the terms). The version shown refers to the current version if no basic version is entered. A remote update is currently not possible for a product if no current version is entered.

Click the "Refresh view" button to look for recently transferred update packages for the selected com­puter. The PMC repository is then scanned and the list of update packages refreshed, if needed. You will find more important details about this topic in the "Refresh View" button .

View in Main Pane: "Product Update Available"

This section describes a situation where there is no system upgrade but where new product updates are available for the currently installed master version for the system selected in the navigation pane. In this case, new update packages are available in the PMC Repository, and you can perform a prod­uct update.

To enable you to get started quickly with this topic, we will now give you a brief, general overview of the steps to be taken during the installation of update packages. Use the links to go directly to the documentation with details.

Overview of a Typical Update Procedure

Note: We recommend terminating all affected Prinect applications and Adobe Acrobat on all computers involved prior to starting a product update or system upgrade.

Note: An update can run only if the Heidelberg signature was verified successfully. If the sig­nature is incorrect or cannot be verified, you will see an appropriate error message and can­not run any update.

(1).If necessary, set up the update group you want (see also Update group) in the navi­gation pane ("Software Update" > Navigation Pane ).

(2).In the navigation pane, select the update group or computer you wish to update.

3.The view in the main pane changes according to the update status of the selected system/com­puter ("Software Update" > Main Pane ).

In this example, we will assume that the current software is available and that "Product Update Available" can be seen in the main pane.

Set the "Update system (recommended)" option below "Select Software Updates" ("Update system (recommended)" option ).

(4).If you set the "Wait after data transfer" option, the product update is first of all only prepared but not triggered (see also Prepare product update or system upgrade without installation).

5.Click "Start Installation" ("Start Installation" button ).

After you click "Start Installation", relevant update messages and also any update e-mails will be sent. See also Update messages.

6.If installation is successful, the "Start installation" button becomes "Finish process". Click this button to complete the update.

7.After installation, you will see the "No product update available" view in the main pane, with a list of all installed products.

(8).If necessary, click the "Refresh view" button to refresh the list of update packages ("Refresh View" button ). If new installable update packages are available in the PMC repository in the meantime, the view in the main pane changes and you will see "Product Update Available" again. See item 3.

"Update system (recommended)" option

In the list of update packages (see "Select Software Updates" (list of update packages) ), select the packages you wish to install. You have the following choices:

•Automatic selection: Set the "Update system (recommended)" option. All of the update pack­ages that must be installed to bring the entire system up-to-date are selected automatically. As this list is sorted in ascending order, by the version to be installed, the selected update packages are at the end of the list.

•User-defined Selection: Deactivate the "Update system (recommended)" option. Now you can manually select a specific version of packages or package sets for a product that, however, need not match the latest version available.

As soon as you have made your selection, all the computers affected by the installation together with the update packages to be installed display below the list in "The following computers will be updated" (see also "The following computers will be updated" (update cards) ).

"Select Software Updates" (list of update packages)

This list shows you all the update packages that are available in the PMC repository and can be installed. The selection is sorted in ascending order by version to be installed, i.e. the latest update packages are located at the end of the list. The latest update packages are selected by default if the option "Bring system up to date (recommended)" has been enabled.

At the end of each item in the list, you see an icon  that you can click to view the description of the update package.

Note: The list is accordingly complex if you are running a complex system comprising several computers and several software components with mutual cross-dependencies (Version). If cross-dependencies are found, the selection will not only include the individual update package you wanted but also automatically sets of related update packages. This ensures that your software components function at all times.

Click the "Refresh view" button to look for recently transferred update packages for the selected sys­tem/computer. The PMC repository is then scanned and the list of update packages refreshed, if needed. You will find more important details about this topic in the "Refresh View" button .

See "Update system (recommended)" option for information about selecting update pack­ages.

Note: If an update for the LIS is available, it is imperative to install it. This update package will be selected by default in the list of Software Updates and cannot be deselected.

"The following computers will be updated" (update cards)

The list "The following computers will be updated" shows all computers to be updated according to their selection in the list of update packages in so-called update cards. Requirements for minimum versions and cross dependencies are considered automatically.

The update cards of the servers are first listed in alphabetical order, followed by the update cards of the clients, also in alphabetical order.

Each update detail will be described in its own section below. You can expand or collapse each of these sections separately or all at once by clicking the header of the update card. The phases "Start", "Stop", "Activation" and "Deactivation" control the Prinect Supervisor.

•"Data transmission": This shows all the update packages that will be transferred from the PMC repository to the computer that will be updated.

•"Preparation": Preparation of an installation includes running any actions required and exiting user and service applications.
In addition, the system checks whether the availability of the computer changed during prepa­ration, see also Update inactive computers as well. In this case, you are forced to cancel installation or you decide to continue installation with the changed availability. All ver­sions of the products listed in this section are affected by these preparations.

•"Installation": This is where you can view a detailed list of the update packages that will be installed for each product.

Dividers in the user interface mark the groups of products to update. Provided the update is to be carried out on two or more computers of the update group, the products of the respective groups will always be installed on all concerned computers. Installation will then run simultane­ously on all concerned computers, and the progress depends on the group membership of the products.

•"Postprocessing": Postprocessing of an installation includes running any actions required and starting user and service applications that were exited in the preparation step. All versions of the products listed in this section are affected by these postprocessing steps. Follow-ups are per­formed only after successful installations.

•"Activation", "Deactivation" (Prinect Supervisor): The phases "Activation" and "Deactivation" are present if a Prinect Supervisor is installed on the computer. In the "Deactivation" phase, the Pri­nect Supervisor will not be started if a reboot was necessary, and all the Prinect components remain inactive. In the "Activation" phase, the Prinect Supervisor but none of the Prinect com­ponents will be started. They are only started in the "Start" phase.

•"Start", "Stop" (Prinect Supervisor): The "Start" and "Stop" phases are always scheduled on those computers on which a Prinect Supervisor Master is present. In the "Start" phase, all the Prinect components are started. In the "Stop" phase, only those Prinect components that are affected by a computer update are stopped.

For a description of the icons in the Update Cards, please refer to Other icons.

Update inactive computers as well

Note: At the start of the PMC repository initialization process, the PMC checks for each com­puter when it was last active. If the LIS of a computer has not reported for more than 60 days, the computer is deleted from the repository. If the computer still reports later, it is automatically reentered into the repository. This means that deleting a computer automatically does not cause an issue. Only the manual assignment of a computer to a group or a subsystem to a system must be done again by the PMC user.

Normally, all the computers of a system to be updated should be active to avoid version inconsisten­cies (see also Version and "Select Software Updates" (list of update packages) ). In other words, they should be accessible by the PMC. If this is not the case, a warning is shown next to the button "Start Installation":

There are cases where you want to be able to update a system, although some of the computers in it are inactive.

The following prerequisites must be met to avoid version inconsistencies:

Prerequisites:

•The inactive computer must have been active at an earlier point in time, meaning that the PMC has a product list of this computer, even if it is older now. This is necessary in order to check any interdependencies.

•The following items are applicable concerning interdependencies:

·A product can be updated if it has no interdependency to another product on an inactive computer.

·A product that is located both on active and inactive computers can be updated. This is also the case if the product versions are different on both computers.

When an inactive computer becomes active at a later stage, it is mandatory to subsequently run any available updates. These updates are determined automatically. When active again, the LIS of the computer provides a current product list when an update request is made. This list is then compared with the current version of the update packages. Following this comparison, the list of update pack­ages ("Select Software Updates" (list of update packages) ) automatically shows you all the update packages to be installed that are also selected by default. You now only have to click "Start installation". The versions of the computer that was inactive are then updated.

Send Wake on LAN (WOL) on update and keep computer active

WOL is a method of activating a computer from hibernation through special network access. Software updates generally do not run during the main working hours but at night, at weekends, off-hours, during the midday break, etc. During these periods it is reckoned that computers are not available because they are hibernating. The PMC supports a WOL function to activate computers participating in updates through network access and to integrate them into system updates. A computer must sup­port the WOL function and be set up accordingly to be able to use this functionality. MAC Books must not be closed.

Note: WOL is disabled by default on new systems that are shipped.

Procedure with WOL in the PMC:

•When a computer switches to a hibernation state, it is flagged by the  icon within the PMC. An appropriate message is issued in the status messages panel.

•When a system/computer is displayed in the "Product Update Available" view of the main pane, the PMC tries to activate all involved computers out of their hibernation state. It can take some time to activate a computer. The icon of the computer goes from hibernation  to active  when the computer leaves its hibernation state. Update of the computer is possible only after the computer was fully activated.

•An activated computer remains activated while a software update is running or while the related system/computer is open in the above-named view.

•A computer, depending on its configuration, returns to its hibernation state when no updates are running and the system/computer is not open in the view.

WOL configuration:

WOL configuration is done in BIOS on many computers. WOL can be configured separately for LAN and WLAN on laptops with LAN and WLAN. Start your computer and set the applicable data in BIOS.

In Windows, you will generally find the settings for WOL in the Network Adapter settings in the Device Manager (WOL is a function of the network card).

Prepare product update or system upgrade without installation

"Wait after data transfer" option.

The "Wait after data transfer" option is available above the update cards. When this option is set, the product update or system upgrade is first only prepared. In this context, prepare means that all update packages of the PMC are sent to the computers concerned and all validations (check certifi­cate and memory space) have run. The PMC waits after preparation. No software update is run yet. At this point, no software modifications were made so far on the computers affected by the update.

To start installation, you must explicitly click the "Installation" button.

The benefit of this procedure is that you can continue your work on the computers concerned during the data transfer which can take some time.

Update messages

Update messages and also any update e-mails are sent only after a successful data transfer. If you trigger installation manually, notification is sent after you clicked "Start Installation". See also Start installation.

All the computers in the update group are notified. In addition, notification is sent to all Cockpit cli­ents that are part of a server in the update group. The Cockpit clients are also notified even if they are not located in the affected update group.

Button bar in the main pane / Start installation

"Cancel" button

With this button, you can cancel the actions started with the other two buttons (view refresh and installation). Installers already started will not be canceled.

"Refresh View" button

When you click "Refresh view", the PMC repository is scanned for new update packages and the list of packages in "Select Software Updates" is refreshed.

Note: Since this is a local operation on the PMC, newer update packages in the PSC repos­itory may not be included at this point.

If no update packages are listed, the reason may be as follows:

•There are no current update packages available for downloading in the PSC. The inventory in the PMC Repository is up-to-date.

Note: There are three cases where new update packages could not be downloaded from the PSC to the PMC repository:
a) You have interrupted your Heidelberg Remote Service connection.
b) The disk space calculated as available after the download is less than 5 GB, see also Menu "Program" > "Restart" . In both cases, your computer/system would appear up-to-date when compared to the updates in the PMC repository, but would appear very out-of-date when compared to the updates in the PSC repository.
c) At least one ready-for-operation License Server is required and none is available.

•There are newer update packages in the PMC repository. However, they cannot be presented for installation because they have interdependencies with other update packages that are not yet available in your PMC repository.

If an error dialog appears, refer to Data Transfer.

You can cancel the update by clicking "Cancel".

"Start Installation" button

When you click "Start installation", all the update packages that you selected in the list in "Select Software Updates" are installed.

Note: The message "Configuration has become invalid" indicates to a user that the availabil­ity of a computer has changed during an update. You must then restart the update.

Note: An update can run only if the Heidelberg signature was verified successfully. If the sig­nature is incorrect or cannot be verified, you will see an appropriate error message and can­not run any update.

You can cancel the installation by clicking "Cancel". See below.

Prerequisite: This user account that is used for the installation must have local administra­tor rights and must be set up on all of the computers that are affected by the update.
Installation is not possible if a computer is running in battery operation.

Attention: Follow the instructions in PMC Reboot Mode if "The computer com­puter name must be rebooted" warning displays.

Note: At the beginning and at the end of an installation there will be a message to all clients.

Start installation

1.Select the update packages you want in the "Select Software Updates" list.

2.Click on the "Start Installation" button.

First, the "Pending Operating System Updates and Computer Restarts" dialog appears. (This dia­log does not display if only computers with service tools are included in the job that do not sup­port the operating system update and computer restart functions). Before you can start the installation of a product update, this dialog checks for pending operating system updates and computer restarts. The "Skip" option is offered if the search for Windows Updates has not fin­ished on all affected update computers after 3 minutes. You can cancel the check and continue the installation with the "Skip" option and then clicking "Next". We do not recommend this in most cases. If the process was canceled, the search results are nevertheless displayed for all computers where the search for Windows Updates has already finished. If operating system updates and/or computer restarts are pending, you can run them yourself and then recheck with "Repeat Check". Click "Cancel" to cancel a product update at any time.

A series of consistency checks is run after that. This includes whether the computers concerned are hibernating, active or battery-operated. If there are one or more inconsistencies that make installation impossible, you will see an error message about this and you return to the "Software Update" view. If necessary, restart installation after remedying the error.

If there are any inactive computers, this will be indicated to you at this point and you can decide whether you wish to continue installation nevertheless or prefer to try and activate the comput­ers first of all. (Does not apply to system upgrades.)

After you click "Start Installation", relevant update messages and also any update e-mails will be sent. See also Update messages.

3.Before installation, administrator information about all the update packages to be installed dis­plays.

You return to the "Software Update" view when you click "Cancel". Installation continues if you click "Next".

4.In the subsequent dialog, enter your user name and your password. The installation will start after the authentication. For authentication, please also refer to Checking the User Privileges for a Product Update or System Upgrade.

In "The following computers are being updated" you can see status messages for each computer and a progress bar for the installation.

•Successful installation: When the installation has been completed successfully, you will see the message "The update was successful”. Please complete this operation". The "Start installation" button becomes "Finish process".

•Faulty or canceled installation: The "Start installation" button becomes "Next". If the installation failed, see also Installing the Update Packages.

5.Installation was either successful or failed.

•Successful installation: Your system/computer is operational again. However, not all processes related to installation are finished.

Click the "Finish process" button.

Now, an alignment between the PMC and PSC repositories is performed in order to ensure the latest software version is available in the PMC repository. The installed products display in the "No product update available" view in the main pane.

After you finished the process, the installation details no longer display in the update cards of the computers.

•Faulty or canceled installation: Click "Next". This triggers postprocessing.

Note: If a running installation is canceled, the update packages that have already been installed will remain installed. The update package currently being installed will finish installing. The update will then be canceled.
If you wanted to install a set of update packages, you run the risk that some of the cross dependen­cies will not yet have been handled at the moment of canceling the installation and thus your system may not operate properly. See Installing the Update Packages.

Prinect Cockpit Update

You can request and perform the following product updates when the Prinect Cockpit software starts:

•Prinect Cockpit

•Prinect Digital Engine Manager

•Prinect PDF Toolbox

•Prinect Signa Station

•Service Tools (LIS)

This function is available only if this is a Prinect Client Computer. No Prinect Server component is installed on these computers displayed in orange in the Prinect Maintenance Center Navigation.

The Cockpit client computer name is displayed in red in the PMC navigation pane while updating is in progress. During the process, this computer cannot be updated while other product updates are running.

The procedure of a product update started on the Cockpit client computer looks as follows:

1.The Cockpit user will be notified if there are product updates for a Cockpit client. In this case, the Cockpit user can start the first installation step.

2.Cockpit closes when installation is started and a browser window opens where you can run the installation as such. The browser window contents is generated by PMC.

3.Start installation here with the "Start Installation" button.

4.After installation, you must finish the operation with the "Finish Operation" button. The Cockpit client computer is available for all other product updates and the red highlighting of its name in the navigation pane disappears only after you have finished the operation.

5.The user must restart the Prinect Cockpit after the product update is finished.

Heed the following:

•PMC will not install a Cockpit client version higher than the one of the pertaining Cockpit server.

•The Prinect Cockpit software will display an appropriate message if a software update of a Cock­pit client computer is already taking place in PMC.

•If necessary, the PMC administrator can cancel updating. A message is issued to the Cockpit user in this case.

•The Product Update dialog on the Cockpit client is displayed in the Cockpit language, e. g. Chi­nese while the PMC UI can appear in another language such as German.

Checking the User Privileges for a Product Update or System Upgrade

You have to authenticate yourself by entering your login data immediately before a Product Update or a System Upgrade starts. Installation will start only then.

As a rule, depending on the components to install, the advanced authentication dialog appears that prompts you to specify fundamentally differing login data:

•First authentication: once again, type the login data required for logging in at the PMC here, see also Checking the PMC User Privileges.

•Second authentication: type the login data of the Prinect user of the computer affected by the update. The HD_PRINECT_USER environment variable of the server computers defines the Pri­nect user name. In this case, the "User name" box is already completed and cannot be edited.

It can happen in exceptional cases that the HD_PRINECT_USER environment variable is not present or is empty. In this case, the "User name" box can be edited, and you have to specify the Prinect user here.

If the check for PMC user authorization should fail, you can also use the "Verify Login Data" function for troubleshooting, see Context Menu of a Computer .

Starting a System Upgrade / Product Update at a Specific Time

There are three ways of setting the time of a system upgrade or product update that you can select in the following list box of the main pane:

•"Start installation immediately after data transfer": Click the button "Start Data Transfer" to start the data transfer from the PMC Repository to the target computer. Installation will then start automatically right away.

•"Wait after data transfer". Click the button "Start Data Transfer" to start the data transfer from the PMC Repository to the target computer. When data transfer has finished, the button text changes to "Start installation" and you must click this button to start installation.

•"Start installation automatically at a set time after data transfer": Next to "Time" you can set the desired installation time after data transfer. You can set only one time at a maximum of 5 days ahead. If the time is in the past, it will be tagged with a red cross and an appropriate tooltip appears. In this case, data transfer cannot take place either, and an appropriate error message appears.

Click the button "Start Data Transfer" to start the data transfer from the PMC Repository to the target computer when you have set the time. The button bears the text "Start Installation" and turns operable when data transfer is finished. Next to the button, a text informs you that a time for installation start was set. You can wait for this time, and installation will start automatically. But you can also click the button "Start Installation" at any time to start installation manually.