|
|
| Line 1: |
Line 1: |
| <!-- table for the whole page -->
| | #REDIRECT [[TechUpdates]] |
| {| style="width:100%; vertical-align:top; "
| |
| | |
| <!-- include the TOC as a template in the first column -->
| |
| | style="width:250px; vertical-align:top; padding:2px 15px 2px 2px;" | {{NewsTOC}}
| |
| | |
| <!-- here is the second column of the full wiki page - will contain content -->
| |
| | style="vertical-align:top; padding:20px 20px 20px 2px;" |
| |
| | |
| <!-- here is a table for the content of the page -->
| |
| {| style="width:100%; vertical-align:top; "
| |
| | |
| | style="vertical-align:top; font-size:160%; color:#7c1911; " | '''The Importance of Maintenance Tools and System Updates''' <HR>
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:120%; " |
| |
| | |
| How do I know if my system needs to be updated?
| |
| | |
| You can find this out as a SysAdmin. Once logged into your system, click on the Trac Man icon, then "Utilities and Prefs".
| |
| | |
| Once the "Batch Utilities" window opens, click on the "Custom Utility" tab.
| |
| | |
| In the top left, you will see the engine date formatted as YYYYMMDD (2018/12/03).
| |
| | |
| [[File:34gwge4eh6e.png|border|600px]] | |
| | |
| | |
| Here is some information on why you should schedule downtime for your system every 12-18 months for updates.
| |
| | |
| ::*1. It will help correct any errors that may be occurring.
| |
| | |
| ::*2. It can help pinpoint the source of an issue when troubleshooting isn't enough.
| |
| | |
| ::*3. Updates will help ensure that your system is as secure as possible.
| |
| | |
| | |
| As a front-end user, will the updates change the way I see or use the Trac System?
| |
| | |
| As a front-end user, the updates should affect the way you see your system. If you are being updated from 4.2 to 4.2B, the only changes you might notice are a few additional reports. However, the way you record visits, set up appointments, and run reports will stay the same.
| |
| | |
| | |
| What is needed for this to happen?
| |
| | |
| ::*1. We will need 2 hours of downtime. During this time, the system will be offline and no one will be able to access the Trac System.
| |
| | |
| ::*2. During this time a Redrock Tech will connect with someone in your IT department that has admin access to the server with Trac System access via screenshare. The screenshare will need to allow mouse and keyboard control.
| |
| | |
| ::*3. These are the server requirements for the Trac System. Hosting the Trac System on a server that meets or exceeds the recommended specs will allow for the best possible performance.
| |
| | |
| {{ServerReq}}
| |
| | |
| | |
| After the System has been updated, your Redrock Tech will bring the system back online and test with you to make sure everything is accessible and functioning correctly.
| |
| | |
| If you need to schedule time for updates, you can do so by going to: https://helpdesk.go-redrock.com/index.php?/Tickets/Submit/RenderForm/1
| |
| | |
| Please provide a few days, dates, and times that will work best for you and your school. Also provide the name and contact information of the IT person we will be working with.
| |
| | |
| | |
| '''More Questions?'''
| |
| | |
| We hope that you find this newsletter helpful and as always if you have any questions on this or any other features, please feel free to let us by emailing Helpdesk@go-redrock.com or submitting a ticket.
| |
| | |
| '''Thank you for your continued support!'''
| |
| | |
| |-
| |
| | style="width:100%;" |
| |
| |}
| |