The PMC functions as a server in the customer's network, and only one PMC application may run. It is recommended to install the PMC on a dedicated server that does not have any other Prinect products to be updated. The reason for this is that some update installations may require a restart and the PMC must not be shut down while it is running. If it cannot run on a dedicated server, some precautionary measures must be taken in the event of a restart.
This section describes a potential situation for the case that software components are also installed on the PMC server which are to be updated using Prinect Remote Update.
In this event, the situation may arise that the installer of an update package expects a restart. If the PMC cannot stop right away because other software updates are in progress, the PMC server must wait to be restarted until these operations have finished. You should perform the required restart afterwards to ensure that the update concerned and all of the other updates associated with cross dependencies continue to function together and, future updates can be applied to a functional version.
If this event occurs, you will see the following on the user interface:
•In the "Software Update" view, the header "Software Update not possible!" appears in the main window of a computer or an update group, with a request to close the view.
•To the right of "Software Update", the button "Maintenance" appears in the view bar.
•In the "Maintenance" view, a message appears which computer must be restarted.
Cause: The computer must be restarted, but other software updates are still running.
Measure: Wait until all software updates have been completed and then restart the computer.