Allscripts Enterprise EHR Reboot Process

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
(Redirected from TouchWorks Reboot Process)
Jump to: navigation, search

Allscripts TouchWorks EHR Server Reboot Process

Stop Interfaces

  1. RDP into Allscripts Enterprise EHR Interface Server
  2. Log into ConnectR Application
  3. Stop ConnectR System Service and ensure all interfaces go to a stopped status
  4. Stop or ensure the following Windows System Services are stopped:
   *	IDXConnectR System Service4.0
   *	MSSQLSERVER

Reboot Database Server (Clustered)

  1. RDP into Active Allscripts TouchWorks EHR Database Node (Node 1)
  2. Open Cluster Administrator- Start > Administrative Tools > Cluster Administrator
  3. In Cluster Administrator- Expand "Groups"
  4. Right click on each group and select "Move Group" to move to the Passive Node
  5. Verify that all cluster resources successfully moved by looking at "Active Groups" under each node

Cluster.jpg


  1. If needed, apply patches to Node 1
  2. Reboot Node 1
  3. Once Node 1 comes back online, Move Cluster resources back to Node 1, making it the Active Node
  4. Confirm SQL is running and database is Active and functioning correctly on Node 1

Do not update Node 2 until you have completed the rest of the process and are sure Node 1 is responding to changes properly.

Reboot Interface Server

  1. RDP into Allscripts Enterprise EHR Interface Server (if not connected)
  2. Verify that services in step 'Stop Services' are still stopped
  3. Apply updates/patches to Allscripts Enterprise EHR Interface Server
  4. Reboot Server
  5. Once server comes back online, please verify following services are running
   *  IDXConnectR System Service4.0
   *  MSSQLSERVER

Reboot Scan Server (Clustered)

  1. RDP into Scan Active Node (Node 1)
  2. Move Cluster Resources to Passive Node (Node 2)
  3. Verify that all Cluster Resources successfully moved to Node 2
  4. If needed, apply patches to Node 1
  5. Reboot Current Node 1
  6. Once Node 1 has completed the reboot cycle, move Cluster Resources back to Node 1, making it the Active Node
  7. Confirm That all shared directories are still available (ex. Application and Image Folders)
  8. Verify ImpactMD Folder is shared to group ‘Everyone’ (Diagram 2)

Reboot Allscripts Enterprise EHR Web Servers

  1. RDP into Web Server
  2. If needed, apply updates/patches
  3. Reboot server
  4. Once reboot process completes, confirm following services are running:
   *	AhsVoeService
   *	IIS Admin Service
   *	Medcin
   *	World Wide Web Publishing Service
   *	XtendDataService (Optional, only for GE Flowcast Clients)

Repeat this process for the remaining web servers

Reboot Allscripts Enterprise EHR Print Servers

  1. RDP into Print/Fax Server
  2. If needed, apply updates/patches
  3. Reboot server
  4. When reboot process completes, confirm the following services are running:
   *	TWCSSSpooler
   *	Print Spooler

Repeat process for remaining print servers


Reboot SupportOne Server

  1. RDP into SupportOne Server
  2. If needed, apply updates/patches
  3. Reboot server
  4. Confirm the following services are running:
   *	NextNine Site Server
   *	NextNine Site Server Watchdog
   *	IIS Admin Service
   *	World Wide Web Publishing Service

Reboot Miscellaneous Allscripts Enterprise EHR Servers

  1. RDP into miscellaneous Allscripts Enterprise EHR Server
  2. If needed, apply updates/patches
  3. Stop any application specific services
  4. Reboot server
  5. Confirm reboot process completes successfully and that application specific services are running
  6. Repeat process for any remaining servers

Test Application

  1. Complete any functional tests necessary to ensure all servers and application components are functioning properly. If changes or updates were made to specific servers, be sure to focus extra attention on those resources.

If issues are found with the updates, all passive servers should be in its original configuration since we have not rebooted or updated them to this point. Try rolling resources to the passive cluster nodes to see if that solves any found issues. If this does not resolve the issue, contact support or rollback changes on all updated servers.

Start Interfaces

  1. RDP into Interface Server
  2. Log into ConnectR Application
  3. Start all interfaces that should be running
  4. Verify that all interface go to a connected or waiting status. Some interfaces such as an interface monitoring a folder, while only be connected when it is actually retrieving a file. All interfaces connected to a port should typically connect.
  5. Review the message log to ensure that transactions are filing and not erroring(if any activity exists). If necessary complete some test such as editing a test patients registration in your practice management system to ensure proper functionality.

Complete Passive Node Reboots for Allscripts Enterprise EHR Database

  1. RDP into Allscripts Enterprise EHR Database Node 2 (Currently passive)
  2. If needed, apply updates/patches to Node 2
  3. Reboot Node 2
  4. Verify that Node 2 comes back online

Complete Passive Node Reboots for Allscripts Enterprise EHR Database

  1. RDP into Allscripts Enterprise EHR Scan Node 2 (Currently passive)
  2. If needed, apply updates/patches to Node 2
  3. Reboot Node 2
  4. Verify that Node 2 comes back online


Links

Back to Application Troubleshooting