Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Apply all Microsoft recommended Windows service packs and critical updates from Windows Update 
  2. Download the latest release of Argos 7 from
  3. Run UnpackArgos7xx.exe to unpack the latest version of Argos
  4. Follow the standard installation steps to install all desired components on the new server
  5. Open the Argos Manager to verify that the installation was successful. Note that any changes you make in the Manager will be erased.
  6. Open the Communication Service health page on Server B to verify that the installation was successful. Make sure that "Last jobs synchronization result" is set to "Success": http://SERVERB:7080/cs/health
    Image RemovedImage Added
  7. Download and install SQL Server Management Studio Express on Server B


  1. Use SSMSE to connect to Server B with the following credentials:
    1. Server type: Database Engine
    2. Server name: ServerB\Argos (replace "ServerB" with the name of your new server)
    3. Authentication: SQL Server Authentication
    4. Login: sa
    5. Password: s3p14_lin3
  2. Click "Connect"
  3. Expand "Databases" to display the Argos7 database
  4. Right-click Argos7 and choose "Delete"
  5. The Delete Object screen will appear. Check the "Close existing connections" box and click "OK".
  6. Your Argos7 database will disappear from SSMSE
  7. Right-click "Databases" and choose "Restore Database"
  8. Type "Argos7" in the "To Database" field
  9. Select "From device" radio button and click the Ellipsis (...) button
  10. The "Specify Backup" dialog appears. Click "Add" and locate your Argos.bak file created during Phase 1

  11. Click "OK"
  12. A list of available backup sets will appear. Choose the most recent "Full" backup from the list and click "OK"
  13. You will receive a message confirming that your database restoration was successful
  14. Open the Argos Manager to confirm that it successfully communicates with the new database.
  15. Click View>Settings and click "Database Connection..."
  16. Verify that the Server field is pointing to the database on your new server

Upgrading from a previous version

If you upgraded to a newer version of Argos while migrating, you'll receive the following error when you launch Manager:

Image Added

To upgrade the restored database to the current Argos version, run SetupLauncher.exe from the Argos7Installers folder on the new server. Follow the prompts to upgrade the database to match the other components on the server:

Image Added

Phase 4 - Redirect other servers and workstations to


use the Argos Communication Service on the new server

Any workstations that connected to the Communication Service on Server A will need to point to Server B. We recommend redeploying the client using whichever tool was initially used to deploy the client, such as SMS, Active Directory Group Policy, Sepialine Deployment Center, etc.


At this point, all Argos components should be pointing to the new server. Send test prints from all print servers and verify that users continue to receive the Argos Desktop Client when printing, and new print jobs appear in the Manager on the new server.


Phase 5 - Retire old Argos Integration Services

The final step in the migration is to make sure that the task executor from Server A is retired. Task executors (AKA integration services) handle tasks like device-based tracking and project imports, so it's very important these tasks are mapped to an active server. 
  1. Open Argos Manager on the new server
  2. Go to View>Settings>Task Executors
  3. Select the old server (in this case shown as last seen 2 hours ago)
  4. Click the "Retire..." button
    Image Added 
  5. If any Integration tasks (project import, user import, HP Designjet integration, etc) are still using the old integration server, you will be prompted to reassign them to the new server. 
    Image Added 


A Task Executor cannot be removed until it has been inactive for 15 minutes.