How do I decommission the 3.12 services after updating to BlueDB?

When you update from 3.12 to a newer 4.0/4.2/4.4 version of Chronicall/ACR, the 3.12 services will run concurrently in order to migrate databases. Once that is complete, those services can be decommissioned in order to recoup the memory and CPU usage.

Answer

Use the steps provided below in order to properly decommission those old services.  You can check the status of the Migration in the bell on the home screen

Steps

1. Log into Chronicall/ACR with Admin privileges
2. Click on the bell icon on the top right
3. Verify that the database migration is at 100%
   
   
   
   
4. Navigate to Admin (System) > Manage Backups
5. Select "Decommission old (3.12) version of Chronicall"
   
   
   
   
6. It will then pop up a series of windows asking if you would like to continue, and whether you would like to create a database backup of the old 3.12
   • It is always recommended to create a backup, just as a precaution
     
     
     
     
7. Once this is completed you will no longer have the 3.12 services taking up resources.
   • You can verify this by opening up the Services program in Windows to see if they are missing.  Ensure you refresh up top to see a fresh list of services
     
     
   • The services listed below should now be gone