Skip to main content
All CollectionsReference GuidesSupport
Server Rebooting Order
Server Rebooting Order
William Pelino avatar
Written by William Pelino
Updated over 5 months ago

Capacity Management Suite®

If you have to reboot one of your servers, you will want to reboot in the following order. Rebooting out of this order can cause issues with your services, and applications.

  1. SQL Server

    1. This needs to be fully backup before rebooting any other server

  2. Application server

    1. This needs to be fully backup before rebooting any web servers

  3. Web Server(s)

Once the servers are back up in the proper order make sure all Teletracking services are running, and either not started or stuck in a starting status.

If the startup type is Manual, the services will need to be manually started.
​

Note - All servers and services should have approval from the necessary parties before any reboots are preformed.

Real-Time Locating System

When needing to reboot the Real-Time Locating System server you will need to reboot the servers in the following order:

  1. SQL Server

    1. This needs to be fully backup before rebooting any other server

  2. Real-Time Locating System Hardware server

    1. This needs to be fully backup before rebooting any app servers

  3. Real-Time Locating System App Server

    1. This needs to be fully backup before rebooting any Capacity Management Suite® servers

  4. Capacity Management Suite® App Server

    1. This needs to be fully backup before rebooting any Clinical Workflow Suite® servers

  5. Clinical Workflow Suite® App Server

  6. Any Web servers would need to be rebooted after everything else is back up and running.

Clinical Workflow Suite®

After the SQL, Capacity Management and Real-Time Locating System servers have been rebooted in their correct order the Clinical Workflow Suite® order is

  1. Application Server

    1. Once this is fully up, check TTserviceViewer to make sure the Manager is running along with the necessary services and if the client uses a dedicated web server.

  2. Web server

    1. Once the app server is up use TTserviceViewer on the web server to ensure the UIVM service is running. Then on the app server ensure the UIVM service has established a connection to the manager.

Note - All servers and services should have approval from the necessary parties before any reboots are preformed.

Related Articles
Technical Information Reference - Capacity Management Suite®
IVR Reference - Capacity Management Suite®
Web Server Reference - Info - Capacity Management Suite®
OnPremise Applications Server Admin Guide
SQL Server Recommendations
Did this answer your question?