Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Tbug 2011


Published on

  • Be the first to comment

  • Be the first to like this

Tbug 2011

  1. 1. When Upgrades go Bad(Terribly, Horribly Wrong)Jean Mankoff, M.S.Director, Instructional Technology Delivery SystemsVicky JohnsonInstructional Operations Systems AdministratorCertified Blackboard System AdministratorCatherine Dutton, Ph.D.Manager, Instructional Technology Software Applications
  2. 2. Texas Womans University• Approximately 14,000 students• 3 campuses• Denton (Main Campus)• Dallas• Houston• Non- traditional studentenrollmentDemographics
  3. 3. Blackboard at TWU• 2,500 live courses a semester• Current version 9.1 – Service Pack 5• Started with Course Info 1 in 1999• Vendor Building Blocks• Wimba (Collaborate)• Turnitin• Learning Objects• McGraw Hill• Tegrity
  4. 4. Overview• Why We Made the Move• Project Plan for the Upgrade• The Big Delay• Communication with Faculty and Support Staff• Working with Blackboard to prepare for Upgrade• Upgrading to 9.0• The Decision to Move to 9.1• Upgrade Results• Consequences and Repercussions• The Clean-up• Current Situation• Future Upgrades
  5. 5. Upgrade Project Plan• March ‘09 Started Project Plan for Spring ’10Upgrade• April ‘09 Managed Hosting Notification• Support on 7.3 would end in October• All managed hosting clients needed to upgrade assoon as possible• Moved upgrade date to August ’09• May ‘09 Upgraded Staging Server to 9.0
  6. 6. Upgrade Project Plan (cont…)• June ‘09 Through listserv information and localtesting, postponed upgrade to December ’09• Informed upgrade must occur by December sincesupport ended in October• Training for 9 would occur during Fall Semester onstaging server• December• Bring Production Down After Finals• Upgrade on Current Production Server• Go Live in January ‘10 with 9
  7. 7. The Big Delay• So Many Bugs – So Little Time• Testing Showed Platform Very Unstable• Listserv Ripe With Issues• Trip to DC in October – My 3 Demands• Would Support Current Version Until Dec. ’10• Would Provide New 9.0 Production Server– Run Concurrently with 7.3 Server– No Cost to University• Would Maintain our 7.3 Server Running Concurrentlyuntil November ’10
  8. 8. Communication with Faculty &Support Staff• Campus Wide Announcement of Delay• Met with Every Department on Campus During ScheduledFall Faculty Meetings• Shared Delay Reasons• Introduced Upgrade Campaign – Change the Control Panel– Change the World• Provided Schedule of Training
  9. 9. Working with Blackboardto Prepare for Upgrade• Consultations• CHM• Managed Hosting• Global Services (Snapshots)• Testing on staging• Testing on new production server
  10. 10. Upgrade to 9.0• Began live training in March• All courses moved from 7.3 server to new server• Began Snapshots April 1 to create shells forSummer and Fall• All Tips of the Week centered on upgrade• Attended faculty meetings to conduct training• Went live for summer sessions on 9.0• Monitored listservs for current issues
  11. 11. Decision to Move to 9.1• Although 9.0 seemed fairly stable - issues reportedappeared fixed in 9.1• Initial results showed it to be more stable• Recommendations from Managed Hosting• Major concerns of stability on 9.0 with more load• Limited testing time line for 9.1
  12. 12. Upgrade Results• Major issues with downtime• Bugs we didn’t see on Staging, appeared on Production• Course copy didn’t work• Banners gone• System slowdowns• Changes to course files from 9.0 to 9.1 had a significantimpact on course copy
  13. 13. Consequences & Repercussions• Faculty revolt – demanded to go back to 7.3• Faculty removed content and used otherresources• MoodleRooms• Google Docs• PBWiki• Faculty meetings turned into heatedaccusations• Credibility questioned• Demands of no more upgrades• Demands to look at other LMS options
  14. 14. The Clean-up• Increased training options• Continued faculty meetings• Applied as many patches as possible• Helped faculty with work-arounds
  15. 15. Current Situation &Future of Upgrades• Stayed on 9.1 Service Pack 1 until August ‘11• Upgraded to Service Pack 5 August ‘11• Evaluating Service Pack 7• Will upgrade once a year on odd Service Packs• Will stay at least 2 Service Packs behind• Will apply patches as needed
  16. 16. Conclusion• Shared responsibility – Blackboard and our campus• No matter how well you think you planned…• Consider staying 2 Service Packs behind• No matter how it feels – It’s not personal!!!