It is recommended to test Windows Updates on a Development system before any updates are applied to Production systems. Consult your organization's policy on Windows server updates.
Server Type | Action Performed | Temporary User Impact During Restart | Next Step |
---|---|---|---|
External MS SQL Database Server (if used) | Restart the external Microsoft SQL Server. | Dispatcher Paragon Management Service will be unavailable as the database is inaccessible. | Restart Dispatcher Paragon Management Servers |
Dispatcher Paragon Management Server | Restart the Windows server. See "Management Server Restart Guidelines" | Restarting all Management Servers:
Restarting one Management Server at a time:
| Restart Dispatcher Paragon Site Servers |
Dispatcher Paragon Site Server | Restart the Windows server. See "Site Server Restart Guidelines" | Devices installed to a specific Site Server:
Devices installed to a load balancer:
| Test authentication, print, and scan functionality at devices. |
Management Server Restart Guidelines
- If one Management Server is installed:
- Restart the Management Server.
- If multiple Management Servers are installed:
- Restart one Management Server at a time.
- In environments with 1000+ devices wait 30 minutes before restarting the next Management Server.
- Wait until the Management Server dashboard is accessible before restarting the next Management Server.
- Restart one Management Server at a time.
Site Server Restart Guidelines
- If the Site Server is not part of a Spooler Controller group:
- Multiple Site Servers can be restarted.
- If the Site Servers are in a Spooler Controller group (any size):
- Only one member (server) of a Spooler Controller group can be restarted at a time. Once the server restarts and the Spooler Controller is visible online on Management Server (Dispatcher Paragon management interface> Devices > Spooler Controller Groups), wait circa 5-10 minutes. If you wish, you may then proceed with the restart of the next Spooler Controller in the group.
- If you restarted multiple members of a SPOC group in parallel, follow the section How to safely restart a Spooler Controller group with cache deletion on all members of a Spooler Controller group.
How to Safely Restart a Spooler Controller Group with Cache Deletion
- Perform these steps on all SPOC group members:
- Stop following services:
Dispatcher Paragon Spooler Controller
Dispatcher Paragon Spooler Controller Group Service
Dispatcher Paragon Terminal Server - Stop all other Konica Minolta services except following:
Dispatcher Paragon Management Service (if present)
Dispatcher Paragon Bundled PostgreSQL <version> (if present) - Delete the folder <install_dir>\SPOC\SpoolCache .
- Stop following services:
- Perform these steps on one SPOC group member:
- Start the Dispatcher Paragon Spooler Controller service.
- Wait for Dispatcher Paragon Spooler Controller Group Service to start automatically within two minutes.
- Start all the remaining Konica Minolta services configured with a startup type other than Manual.
- Wait until SPOC shows ONLINE status on Management interface or until <install_dir>\SPOC\logs\spoc_lifecycle.log shows last status "ONLINE".
- Wait for the message "End of processing of GetNewJobsByUsersResponseMessage" to appear in the <install_dir>\SPOC\logs\spoc.log. This process may take 5 to 30 minutes, depending on the size of the environment and the volume of print jobs.
Repeat the step 2 on all SPOCs in the SPOC group, always one server at a time.
Previously printed jobs may not be visible in the terminal job list for until spooler job recovery has completed.