ECMS - Patching Update Schedule
The purpose of this document is to provide a patching update schedule for Departmental Leads.
Imaging System Patch Maintenance
Please also reference the Imaging Service's visual guide for what follows in text form: ECMS - Imaging 12-Month Patch/Upgrade Cycle.
- Stay within 6 months of the current vendor patch level.
- 6-month cycle with occasional patches if no client upgrade required and patch features warrant deployment.
- Avoid more than two client updates per year:
- Emergency Patch: First available time.
- Critical Patch: Minimum 10 business days after Hyland releases a patch on the 10th of the month (schedule below indicates the second Thursday after a patch release should a Critical Patch be necessary.
Standard Operating Procedure
- User's pre-testing report due: Friday, end of day, week prior to potential start time.
- Go/No Go Deadline: Monday at Noon.
- Decision made by ECM/Imaging Team will be based on factors including user's pre-testing results.
- Start time: Thursday, 6:00 pm
- User post-patch testing: Friday at 8:00 am with feedback due to Imaging service team by 11am.
- Decision on patch roll-back: Friday as soon after 11:00 am as possible
- If needed, roll-back should begin as soon as possible
- Otherwise, make client update available via PEDS as soon after 11am as possible
- The following regularly scheduled refresh will include a full refresh of DEV/DEV2 and TEST
Schedule for TEST environment refresh
- Typically scheduled for the first Wednesday of each month at 10:00 am, however other needs may alter this.
- Major releases twice per year with monthly patches.
- Patch/deployments occur on the Thursday of the first or second full week of February/August.
- Document Transfer/Conversion Server: Bi-annual software updates, April and September or as needed.
Emergency and Critical Patches Process
The vendor may modify the intervals that follow. The Imaging Team will update this document as we become aware of changes when changes are communicated to the Imaging Team.
- Patch typically released on the 10th of the month
- EMC/Imaging Team evaluates
- Communications will be sent to Department Leads with recommendations for deployment.
- Recommendation will be based on emergency or critical status of patch.
Security/Critical Monthly Patches
The Imaging Service Team will schedule emergency critical patch as soon as possible following deployment and user acceptance testing on non production environment(s) as needed.
Document Transfer and Conversion
The Imaging Team also manages several hosts used for bulk file conversion and importing. Those hosts, like the primary hosts for the Imaging System, also require routine maintenance and patching/updating as exploits and/or security patches are identified by system administrators or when applications that are used for file transfer and document conversion are updated by the vendors of the software. These systems are also on a 6-month patch cycle the month following the primary Imaging System patching. Thus when the primary Imaging System is patched in February of the year, the file transfer and conversion host will be patched in March. When the primary Imaging System is patched in August of the year, the file transfer and conversion host will be patched in September. This is reflected in the 12-month visual guide KB document referenced above.
Note that one difference between these two patch cycles is that this cycle does not take the Imaging System offline. Patching the document transfer and conversion applications will only delay document transfer and conversion while the processes are put on hold pending successful patch completion. Processing will queue and once patching is completed, file transfer and conversion will resume and catch-up any documents that queued during the patching.