A Note From Bill...
As we head into summer, it's great to see work on some of our most important projects coming to fruition.
The Integrated Email and Calendar Project, which successfully migrated all of IT Services' email history and data last weekend, is a good example. Congratulations to the team, and to all who worked with them, for such a successful start. This project will arguably be our most visible in many years. It will touch the working lives of all faculty, staff, and students on campus. It is critically important that it is a success: that future migrations go smoothly, that the software and hardware work seamlessly, and that the documentation and training be top-notch. Last weekend was an important first step.
On the research computing front, the Faculty Planning Committee will hold its first meeting this week. Funding of a feasibility study has already been obtained, and Stanford's Department of Facilities Project Management has completed phase one of that effort. The Faculty Planning Committee will begin to address the serious issues of operational efficiencies, sustainability, the architectural design, and integration with existing campus resources. In addition, they are charged with developing an effective financial model to cover costs for research computing from central, school, and departmental resources. They are moving quickly and hope to take plans for the research computing facility to the Board of Trustees in late fall or early next year.
In addition, we made significant progress related to our authentication infrastructure with the recent completion of the Guest Accounts System and the Kerberos migration (a.k.a., K4 --> K5). Similarly, the Workgroup and Organization project moved us forward on the middleware front and we also tested and installed an Emergency Mass Notification system for the entire campus.
Work continues on other key projects such as the rollout of VoIP and ACD for the hospitals; extending the security initiative to the desktop; disaster recovery and business continuity; the data center in Livermore; server virtualization; departmental firewalls; support for campus moves, including Porter Drive; implementation of the Access Control Enterprise System; and a host of others.
My thanks go out to all of you for all the hard work you've done to make it such a productive year. It's been doubly rewarding since our clients gave us such great feedback in the recent Client Satisfaction Survey.
This week we celebrate the 4th of July. It marks a time when the pace starts to slow down a bit as folks across campus take vacations, relax a bit, and recharge for the coming year. I hope that you and your families have a wonderful holiday.
- Bill Clebsch
IT Services
Educause Live!
Stanford University's Registrar, Tom Black, and Bruce Vincent from IT Services recently gave a joint online presentation as part of the Educause Live! Spotlight on Identity Management Series. Titled How Today's Registrar Demands More From Identity Management Policy and Infrastructure, the entire one-hour presentation was captured and can be streamed from educause.acrobat.com/p49193821/.
Abstract: Stanford University's Registrar and IT strategist discuss their vision of the future of identity management in higher education. Tom Black and Bruce Vincent will give some progressive perspectives on how their roles complement each other in supporting not only admissions processes but a lifelong relationship between students and universities. For more information see net.educause.edu/SPTIDM086.
Many of the discussion points cover ways in which the evolution of institutional policy and emerging technologies support the Registrar's vision for supporting lifelong learning. Tom and Bruce also address new ways to leverage such technologies to improve data privacy in interactions with online service providers who support Student Administration.
- Bruce Vincent
Chief IT Architect and Strategist
New Anti-Malware Software Selected
Stanford recently selected software provided by Sophos
to serve as the campus site-licensed anti-virus, anti-spam, anti-spyware (collectively known as anti-malware) software solution. The Sophos software will replace the Symantec Anti-Virus software, which Stanford has licensed for several years.
The Sophos selection was made following a Request For Proposal (RFP) process which began in January. The RFP process involved a cross-campus evaluation team with representatives from IT Services, the Information Security Office, the Graduate School of Business, Stanford University Libraries and Academic Information Resources, the Medical School, the Law School, and SLAC.
The primary reasons for selecting Sophos are 1) it has a single code-base for all supported platforms (Windows, Mac, Linux) so that all protection is provided across platforms at the same time; 2) the Sophos "detection engine" is self-updating (so users won't have to download and reinstall the product to get the newest version—it can update itself); and 3) Sophos has a more responsive support organization. In addition, industry benchmarks and reviews were evaluated and considered.
IT Services Software Licensing group is now working with Sophos to finalize license arrangements, and we anticipate that the licenses will be in place by August 1 or sooner. In addition, Software Licensing is working with Symantec to provide a few months' additional licensing beyond our current September 30 expiration date, to allow those groups using the Symantec Management Console to smoothly migrate to the Sophos management console. Stanford plans to execute a three-year agreement to provide cost savings and stability.
Finally, because Sophos includes anti-spyware detection, Stanford is dropping its license with WebRoot Inc.'s SpySweeper, effective July 31, 2008. Information about removing that software will be provided to campus technical staff shortly.
My thanks to the members of the IT Services Desktop Strategy team, and our colleagues across campus, for their invaluable assistance with this evaluation process. Once every three years seems just fine!
- Chris Lundin
Client Support
IT Services Successfully Introduced to Stanford Email
The June 23rd migration to the Zimbra mail servers went well. All IT Services staff have migrated to the new system and most have begun exploring the new version of Webmail. This large-scale production test is uncovering issues that will be resolved or mitigated prior to releasing this to the rest of the campus community, thanks in large part to the HelpSU requests that you've submitted. For your reference, the checklist page has been repurposed to track issues as they're discovered and to provide workarounds for IT Services staff to use.
One big improvement has already been made: the Company Contacts search in the Address Book now searches the Stanford-view of StanfordWho and returns all Stanford-viewable information including names, email addresses, work addresses, and phone numbers.
Now the team turns to focus on the Sundial migration. The integration team is putting the finishing touches on the data migration plan. All meetings in Sundial—past, present, and future—will be migrated to the new Stanford Calendar. A new checklist will be published next week to help guide IT Services staff through this transition. The checklist will also have a list of training times to help prepare you for moving from Sundial to the Stanford Calendar. In the meantime, we encourage you to continue to explore the new system and report any unexpected behaviors that you find.
- Ammy Hill
Campus Readiness
TableTop Tops BC/DR Agenda
IT Services Business Continuity/Disaster Recovery (BC/DR) project recently completed a significant step in IT Services' effort to have an executable recovery plan in the event of an IT disaster. Known as a "TableTop" exercise, the activity was held on June 17th.
Approximately a dozen staff gathered in a conference room in Forsythe to walk through (on paper) the recovery steps needed to bring several key Stanford applications back to an operational state in the event that Forsythe becomes unavailable.
Jay Kohn led this BC/DR exercise through a scenario where all of the equipment in Forsythe became unavailable (or as Jay put it during the exercise, a “smoking black hole”). Although the goal for the exercise was to enable Administrative Systems (AS) to be able to recover the Oracle Financial applications, there is a significant number of supporting systems and applications that have to be brought to life to make it a complete picture.
I was appointed “incident commander,” and to make the exercise more dynamic than sitting around a table reading from scripts, we asked the representatives to requisition equipment (in the form of a picture on a flip chart), and cabling (in the form of rolls of masking tape). The goal of the exercise was to physically establish the environment on the wall of the conference room. This visual gave us a good opportunity to generate an equipment list and verify that we had an environment that would work.
We then proceeded to step through the recovery of the various systems (Network, Servers, SAN, Tape Library, and the foundational support applications) to provide the authentication, minimal web services, AFS, and storage and tape systems needed for the recovery.
The TableTop went very well and helped us find gaps to fill in order to be successful at the real test of the BC/DR plan.
In late July, we will do a three-day live simulation. We will recover tapes from Iron Mountain and actually obtain the necessary equipment and build the environment we created on the walls for the exercise. We'll be working with AS to recover Oracle Financials to an operational state that can support an emergency environment.
It is likely that we will uncover more gaps, but I have high hopes for a successful test, and I’m confident that we will walk out of the test with a strong and executable recovery plan.
- Dan Stillmaker
Backup and Storage