• Present: William Dougherty-NI&S, scribe and chair; Mike Moyer-NI&S; Susan Brooker-Gross-IT Management; Russ Fenn-DBAA; Bill deWindt-LT; Kimberley Homer-SETI; Karen Herrington-IMS; Joyce Landreth-UCS

• DBAA-to be scheduled: 5am to 4pm Sunday, Nov 20.
   
  Banner releases will be installed on the banner and banner foundation databases:
   
  Databases included:
   
  Banner (prod)
  vtfbanner (FRPD)
   
  Web Services impacted are:
   
  Budget Tuition
  Banner forms (both INB and WebLogic)
  Self-Service Banner (Hokie Spa, Hokie Plus, Hokie Team)
  Leave Entry And Reporting System
  Some functionality of MyVT
  AIS Application Promotion (AAP)
  Automated Request Process (ARP)
  IMS Password Change Application
  Make A Gift Today (University Development)  
  Timetable Of Classes
  Web Job
  Web Dist
  There may be other services partially impacted.
   
  * There may be additional services administered outside of ES impacted as well.

• SETI: SETI is proposing the following dates for deployments:

ED 3.2 deployment to production: November 29 (Tuesday)

The most notable change will be that student PIDs and email addresses created via PIDGen after the deployment will be suppressed by default.  Also, the DAT view for the Call Center and 4Help staff will now display a user's account recovery options. Impact on end of month/first of month activity should be minimal as these processes are mainly financial.

CAS deployment to production: December 8; Guest will be able to log in via CAS.

• LT: Tentatively in December we will be migrating Scholar to CAS authentication, but I do not have a firm date yet as we are still in the final testing stages on our development systems before rolling the changes out to preprod. Still working on timeout and guest access issues. Once I have additional information I will pass it along to this group. Also still tentative at this point is a migration of the production Scholar Oracle database from the current hardware onto a redundant pair of Oracle servers, which we are hoping to perform sometime during the break between the Fall and Spring semesters. We are still in the early stages of this migration, working closely with UAS and DBAA, and I am hopeful that as we enter December a more concrete timeline will be established which I can share. At this point I can only confirm that plans are to have this change completed before the Spring semester begins, but not performed during the week of "Winter Break" when staffing could present a support issue.

• SS: NAS Upgrade is now scheduled for Sunday, January 8th, 2012. All NetApp services will be affected (see following list). Will probably post something to VT News.
  • Exchange
  • Junk Mail Manager
  • www.computing.vt.edu
  • Mystore and Mystore2
  • Departmental shares on the NAS
  • Banner Genform
  • Internet Native Banner
  • VT Confluence
  • JIRA
  • Nolij
  • Banner Document Management System/Application Xtender Learning Technologies Applications
  • Scholar
  • Blackboard
  • FDI Registration
  • Online Course Evaluation System
  • Software Skills Gateway
  • iTunesU
    

Ensemble Content Management System

• Publishing only

Web Hosting

• All hosted websites
• MySQL Databases associated with hosted websites
• VT Calendar (calendar.vt.edu)
• VT Survey (survey.vt.edu)
  

Filebox

• All fileboxes

• IMS: Tentatively scheduled for December 17th and 18th; BEIS project. New travel and expense (T&E) module to be integrated with Banner production. Dependency is single sign-on through Banner Enterprise Identity Services. Lots of services will go behind CAS (INB, etc.) to make this work, but not required for anything but the T&E module. No major impact known as this will be a "soft opening" of the module. Enterprise Systems will be working with pilot groups. Provisioning/deprovisioning piece will come later. How will this affect users who are logged in to one service and attempt to access another service? Will they be prompted for a password or not? (Users may be prompted for recovery options if they haven't set them up already.) Will this confuse them? More info as it becomes available.
  • Further clarification: First of all, there is nothing significant about the December 18 date at this point in time. Some of the pieces are already “in production” and the others will be there before December 18. But none of it is “turned on” and according to the technical teams that are working on this, it may not even be enabled before the end of the year. I’m not sure who all sees the minutes from our SAMS meetings, but I don’t want this to get out to a wider audience yet because it might cause a lot of unnecessary panic and questions. The actual rollout is going to be very controlled and limited and the communication about it should come from the Enterprise Systems area. In response to someone’s question about folks accidentally stumbling on the CAS-enabled versions of the applications, I was told that that would be virtually impossible. They would have to know the exact URL to go to and it is not easily guessable. All the links will still point to the versions of the applications that exist as they do today.

• UCS: Emergency contact information will be requested from all of the IT units so the VTOC can reach groups in emergencies.

• CNS: Chicken Hill outage will take out network in Parking Services and other buildings in that area.

• Possibility of moving Listserv to Google: Wanda wants feedback.

• Maintenance Schedules: