| Event | Description | Exchange Mail System Maintenance Date: Jun 20, 2018 5:30 PM
Services:This maintenance will only impact the DePaul Exchange Email system.
User Impact:No user or system impact is expected. | Information Services Engineers will be making updates to the Exchange system, changing the Unified Messaging to Exchange 2016. This work will be done on Wednesday, June 20, beginning at ~5:30PM. |
Database Server Upgrades and Maintenance Date: Jun 20, 2018 7:00 PM
Services:The servers being updated inlucde those for the following (production) systems: MobiusImageNowConfluence (Knowledge.depaul.edu)CampusGuide (iDePaul)
User Impact:During the time these DB servers are being worked on, the systems/services that they serve will be unavailable. | IS System engineers will be performing maintenance, including upgrading the OS, updating the VM version and migrating to new VMWare clusters on several production database servers. This work will be done on Wednesday, June 20, beginning at 7PM, with work expected to complete by 10PM. |
Windows Production Server Patching Date: Jun 21, 2018 1:00 AM
Services:This will affect all Windows Production environment servers.
User Impact:No reboot is required for this special patch, so there should be no downtime. | Information Services will be applying a special Microsoft Windows update required for June patches to all Production servers on Thursday, June 21, 2018, between 1am - 4am. This is a special patch, and does not require a reboot. |
Exchange Mail System Maintenance Date: Jun 23, 2018 9:00 PM
Services:This maintenance will only impact the DePaul Exchange Email system.
User Impact:No user or system impact is expected. | Information Services Engineers will be making updates to the Exchange system, changing the mail flow to route through Exchange 2016. This work will be done on Saturday, June 23, beginning at ~9PM. |
Database Server Upgrades and Maintenance Date: Jun 24, 2018 12:05 AM
Services:The servers being updated inlucde those for the following (production) systems: BBTSPeopleSoft CRM, and OLMPeopleSoft HR
User Impact:During the time these DB servers are being worked on, the systems/services that they serve will be unavailable. | IS System engineers will be performing maintenance, including upgrading the OS, patching Oracle, updating the VM version and migrating to new VMWare clusters on several production database servers. This work will be done on Sunday, June 24, beginning at 12:01AM, with work expected to complete by 3AM. |
Windows Production Server Patching Date: Jun 24, 2018 1:00 AM
Services:This will affect all Windows Production environment servers.
User Impact:All servers will be rebooted after updates are applied successfully, so some systems may experience a brief (10-20 minute) period of downtime. Servers will also be donw for a short period at 5AM to upgrade the VM hardware version. | Information Services will be applying Microsoft Windows updates to all Production servers on Sunday, June 24, 2018, between 1am - 4am. All servers will be rebooted after updates are applied successfully. Engineers will also be upgrading Windows servers in the Loop CST data centers to newer hardware versions of VM. This work will be done at ~5AM, and will require servers be shut down for this upgrade to be completed. |
SharePoint Farm Maintenance Date: Jun 29, 2018 10:00 AM
Services:This maintenance will affect all sites on the SharePoint production farm. This includes www.depaul.edu, college and department websites, teamsites, etc.
User Impact:During this work, we will be switching over content delivery to our front-end caching system. During this period, some portions of the sites on the SharePoint farm will not function as normal. This includes: • Editor Login and content updates• Team Sites• Web parts that use lists• Forms • Archived course catalog pages Additionally, any updates made from the time cached copies were taken will not display that new content. | On Friday, June 29, beginning at ~10AM, Information Services will be patching the SharePoint farm. . The estimated time of completion is approximately 10 hours. During this time, we will use NGINX to serve up copies of all SharePoint sites so that any loss of functionality is minimized for the users viewing site content. |