/
Time and Attendance Server Reboot Recommendation

Time and Attendance Server Reboot Recommendation



Description of Issue

How often should we reboot our Time and Attendance servers and in what order should it be done?



Context
  • Time and Attendance 

  • Server

  • Reboot



Cause

Seeking recommendations on Time and Attendance Server reboot policy



Resolution

It is recommended that all Time and Attendance Servers for On Premise Clients are rebooted every 30 days as well as applying Microsoft Windows Updates. The order that they should be rebooted in is as follows:

  1. Database Server(s)

  2. Application Server(s)

  3. Infrastructure Server(s)



Additional Information

For EERP customers, Tyler Workflow could potentially be installed on an existing Infrastructure server that also houses other EERP products, if not, Tyler Workflow is sharing the same Application server as Time and Attendance











Related content

Reboot Server with Scheduled Task
Reboot Server with Scheduled Task
More like this
Munis Server Reboot Recommendation
Munis Server Reboot Recommendation
More like this
Preparing for Time and Attendance Upgrade
Preparing for Time and Attendance Upgrade
More like this
Time and Attendance System Requirements
Time and Attendance System Requirements
More like this
Decommissioning a Time & Attendance Server
Decommissioning a Time & Attendance Server
More like this
Receiving 404 Not Found for Time and Attendance after applying Windows Updates
Receiving 404 Not Found for Time and Attendance after applying Windows Updates
More like this