Office of Information Technology will be performing routine systems maintenance which includes but is not limited to rebooting Windows servers as deemed necessary, installing critical patches and other health checks on Thursday, 01\/19\/2016 from 3:00 AM to 7:00 AM during OIT maintenance window. In addition, the following systems will be specifically impacted:<\/p>\n
***************************************************
\nUCS firmware upgrade
\nWhen: 3:00AM – 6:00AM
\nAffected services: Blackboard, ADFS, Malware Bytes, 365 Dirsync, PaperCut, SharePoint, College of Education Websites, Chessboard, College of Mediciine application site, Labs Remote Apps, Labs Camera Servers, Undergrad App, CAS\/Shib, NetReg, Boca DNS, Boca DHCP, Networking Servers, SCCM, Exchange POP and IMAP
\nAffected systems: boc22hv[01-07], boc22hv[20-33], boc22sas[1-4], boc22sast[1-4], bbloracle, bbloraclealt, appadmin, as4, as5, bba[1 – 10], bbm1, boc22adfs, boc22adfsp, boc22aptven, boc22asmt, boc22bedework, boc22canvascli, boc22cm102srv1, boc22cm102srv10, boc22cm102srv9, boc22cm102vrt101mrtg, boc22dellome, boc22dirsync, boc22kofaxcap, boc22mbes, boc22mssql11, boc22mssql12, boc22mssql21, boc22mssql22, boc22mssql31,boc22mssql32, boc22mssqldev1, boc22mssqldev2, boc22mssqltald1, boc22mssqltald2, boc22mssqltalp1, boc22mssqltalp2, boc22nasmvi, boc22oimccp1, boc22ora09, boc22payaradp, boc22payaranp01, boc22pcapp01, boc22pcapp01dev, boc22pcapp02, boc22pcapp02, devboc22pclyprt01, boc22pcoffice01, boc22pcprt01, boc22reports1, boc22sccm, boc22snapc, boc22spapp1, boc22spwfe1, boc22talweb2, boc22vcenter1, boc22whatsup, cardaccess, cas1, chessboard, comvmadi01, comvmpsql1, comvmsql01, comvmweb01, comvmweb1, comvmwebdev1, controller, cosweb1, cuttlefish, dhcpboc1, dnsboc1, dsr[1 – 6], duo, eprint2, exchangeca03, fauappsrv2, filelocker[1 – 2], freeze, frevvo1, frevvot, gitlab, hpc, idm2, idm4p-oel6, iss, issdev, jenkins2, ldapboc1, ldapboc1-el6, lintalon0, mlintalon1, lists, ls-matlab, ls-medmodel, ls-osd, ls-snap, madcat1p, mcclient, migrate365, napalm, OracleEM, pinky, piwik1, r25-webservice, remotecon, s164n14, s165n113, s165n15, sacs, sepiidae, shibboleth2, shoutcast, starfish, talonx2, tuna2p, ugapp[1 – 5], visualsvn, wildflymc[1 – 2], XenAPP[00 – 02], XenAPP-Office, XenLIC, XenSF[1 – 2], XenZDC1-2, yakko
\nDescription of maintenance: OIT will be upgrading the components of several systems to resolve bugs and add support for newer hardware.
\nUser impact: No end-user impact is expected<\/p>\n
***************************************************
\nMigration of talisma from old bigip to the new bigip
\nWhen: 6:00am – 7:00am
\nAffected services: Talisma(CampusNexus)
\nAffected systems: Talisma(CampusNexus)
\nDescription of maintenance: We are continuing the move of servers from older bigip load balancer hardware to the new ones. This move will be for the backend servers that support talisma
\nUser impact: There should be no end user impact as we are not changing the IP for talisma just the load balancer it will be on during off business hours. The only users that might be effected are those that are trying to connect to the web client during maintenance.
\n***************************************************
\nMain Incoming\/Outgoing Email Gateway Changes (Ironport)
\nWhen: 5:00am – 6:00am
\nAffected services: email
\nAffected systems: bertx, berty, boc22esa02, nwesa02\u200b
\nDescription of maintenance: \u200bWe are making changes to the main incoming\/outgoing email servers in an effort to increase efficiency and to control some of the outgoing spam.
\nUser impact: Perhaps some individuals who legitimately send over 100 messages within an hour that is not using lists.fau.edu or some other established means of mass communication will notice the new restriction.<\/p>\n","protected":false},"excerpt":{"rendered":"
Office of Information Technology will be performing routine systems maintenance which includes but is not limited to rebooting Windows servers as deemed necessary, installing critical patches and other health checks on Thursday, 01\/19\/2016 from 3:00 AM to 7:00 AM during…<\/span><\/p>\n