Institutional Migration to Google Apps – Joe Moore, Dr - AIKCU.org
19
Institutional Migration to Google Apps Joe Moore, Dr. Jeffrey Parsons, Dr. Bettie Starr Lindsey Wilson College
Transcript of Institutional Migration to Google Apps – Joe Moore, Dr - AIKCU.org
Institutional Migration to Google Apps
Joe Moore, Dr. Jeffrey Parsons, Dr. Bettie StarrLindsey Wilson College
About Lindsey Wilson College
115 Full Time Faculty2600 Students
Until 2011, LWC utilized the Microsoft Exchange Server for mail services. Outlook was utilized as the primary mail client for the Columbia campus. Off campus faculty and students relied on web-based exchange access.
Why Move to Google Apps?
● Inbox storage limitations forced faculty to purge mail on a weekly basis. ○ Faculty accounts were limited to 70 mb.○ Student accounts were limited to 20 mb.
● LWC student accounts were not retained after graduation and thus were often never used.
● Off campus faculty had limited mail options. ● Expanding student enrollment created
increased exchange licensing fees
Google Apps Launches - 2007
Google launched Google Apps for Education, including 2 gb of storage per user.
Initial discussions identified several questions:● Was there appropriate migration and integration tools
available? ● Was an external mail system secure?● What about privacy?● Was this a fad?● Was there a catch?
SPC Migration 2009
Google expanded integration and migration support tools, including support for Outlook integration and LDAP integration. Storage space extended to 7 gb.
The institution determined there was enough infrastructure in place for a limited launch for School of Professional Counseling faculty and students.
Institutional Migration 2011
After continued concerns over limitations of mail services for the Columbia campus and a successful implementation of Google Apps with the School of Professional Counseling, LWC decided to move forward with the launch of Google Apps for the institution.
Google expanded storage to 25 gb.
Institutional Migration Cont.
Students were moved over to Google Apps in the summer of 2011.
Faculty and staff participated in demonstration sessions in August of 2011.
Feedback was overwhelmingly positive.
Institutional Migration Cont.
Faculty and staff were allowed to opt into Google Apps throughout the fall 2011 semester.
Faculty and staff migration was expedited after a failure of the Exchange server in late fall.
What Went Well?
● Integration with LDAP● Integration with Outlook● Student and Faculty training● Overall student and faculty adoption
What didn't go so well?
● Disconnects between Exchange and Google users
● Unanticipating missing Outlook functionality○ mail notifications○ mail merge○ sort column
What Might We Do Differently?
● Rollout all faculty, staff, and students onto Google Apps at the same time
● Limit the number of simultaneous system changes○ changing student username format○ implementing Blackboard○ changing elements of the Blue Raider Portal
Current Challenges
● Reports of "missing" mail● Irregular use of the calendar and other
features● Group management refinement● Integration of Google Apps with Blackboard
Institutional Benefits
● Increased storage space● Easier on and off campus mail access● Elimination of the need to purge mail● Ability to retain student accounts after
graduation● Increased utilization of student mail system● Elimination of MS Exchange licensing fees
Current System Use
Other Institutional Benefits
● Integrated calendar and document systems● Easy access to information across multiple
platforms (i.e. computer, tablet, phone)● Integrated communication and social
networking tools● Integration with other 3rd party tools (i.e.
AnyMeeting)● Unanticipated uptime when other systems
go down
Questions
