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:

    • User authentication using username and password is not available. New users may not authenticate at the Site Server. Far roaming print jobs may not be available. 

Restarting one Management Server at a time:

    • No user impact expected.

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:

    • All authentication and printing is unavailable until the Site Server has completed restarting and is online.

Devices installed to a load balancer:

    • Jobs spooled to a restarting Site Server may not be available for printing.


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.

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

  1. Stop the Dispatcher Paragon Spooler Controller service and Dispatcher Paragon Spooler Controller Group Service service.
  2. Stop the Dispatcher Paragon Terminal Server service.
  3. Stop all other YSoft services except those:
    1. Dispatcher Paragon Management Service service (if present)
    2. Dispatcher Paragon Bundled PostgreSQL 9.4 service (if present)
    3. Dispatcher Paragon Bundled Etcd service (if present)
  4. Repeat previous steps 1-3 on all Site Servers in the Spooler Controller group.
  5. Delete the cache folder <install_dir\SPOC\SpoolCache on all Site Servers in the group.
  6. Start the Dispatcher Paragon Spooler Controller service and verify that the Dispatcher Paragon Spooler Controller Group Service service starts automatically within 1-2 minutes.
  7. Start the Dispatcher Paragon Terminal Server service.
  8. Wait until the Dispatcher Paragon Spooler Controller service starts and is online. Check that <install_dir\SPOC\logs\spoc_lifecycle.log last status is "ONLINE".
  9. Start all the other YSoft services stopped in step 3.

  10. Repeat the previous steps 6-9 on all Site Servers in the Spooler Controller group. Depending on the count of not-deleted jobs, wait 3-10 minutes between the start of each Site Server services.

    Previously printed jobs may not be visible in the terminal job list for 15 to 30 minutes until spooler job recovery has completed.