Software updates for D2L Brightspace will be implemented on a monthly basis, typically on the second Tuesday of the month. If downtime is required it will occur between 5:00 - 7:00 a.m., and users will be notified in advance. Any changes to this schedule will be updated here and communicated to campuses.
|Dates in 2015||Version||Dates in 2016||Version|
|August 11, 2015||10.5.0||
January 19, 2016
September 8, 2015
|10.5.1||February 9, 2016
October 13, 2015
|10.5.2||March 8, 2016
March 10, 2016
November 10, 2015
|10.5.3||April 12, 2016||10.5.7|
|December 29, 2015||10.5.4||May 24, 2016||10.6.0|
These are reserved downtimes that may be used for D2L Brightspace software updates, and routine maintenance to the hardware and server software that support the D2L system. These will only be used if needed, and users will be notified of the downtime in advance.
|Tuesdays||All Tuesdays||5:00 a.m. - 7:00 a.m.||Routine Maintenance|
|Sundays||All Sundays||5:00 a.m. - 9:00 a.m.||Routine Maintenance|
Why Downtime is Required
Throughout the year, downtimes are required to allow for maintenance and upgrades of the system hardware and software that support MnSCU's Instructional Management System (IMS) enterprise, as well as updates and maintenance releases to the IMS software, which is currently Desire2Learn (D2L). Based on broad-based input from people in the academic, administrative and technical areas of the MnSCU system, recommendations were made regarding the optimum times to schedule these downtimes.
We have pro-actively scheduled potential downtimes for maintenance releases and version updates that may be available in the future. Pro-active planning keeps faculty and students informed of times that D2L may not be available. While a potential downtime for D2L software updates is scheduled once a month, we typically do not use more than three or four of these downtimes each year. Scheduling one potential downtime a month gives us more flexibility in taking maintenance releases and updates as they become available, thereby providing more timely fixes to software issues.
There are two basic types of planned downtimes:
- Routine maintenance and upgrades to hardware and server software that support D2L, and another for
- Updates and maintenance releases for the D2L software.
Users will be notified in advance if the downtime will be used. If no work is necessary during a particular period, the downtime will not be used.
Unforeseen emergencies or special circumstances (power outages or hardware failures, for example) that require downtime at other dates and times will be announced as necessary.
Since MnSCU's IMS/D2L Enterprise System is among others hosted at an off-site facility, occasionally, we may also experience downtimes related to the services at that site. Having an established downtime schedule for our own maintenance helps us to coordinate downtimes with our hosting data center, thereby enabling us to minimize the frequency and duration of any disruptions in service related to the IMS/D2L system.