1/18 KIC Meeting Agenda and Notes
presenters - Karl Brown, Susan Herder, Doug Erickson
Mounds View transition to Google Apps and the Google Apps for Education Certification program.
-Mounds View is moving to apps as their primary email service in fall, 2011.
Mounds View’s presentation
Contact information is on the last slide.
presenters - Christopher Kane, Bernard Gulacheck, and Ellen Puffe
U of M transition to Google Apps, specifically addressing issues/concerns about privacy/security
File Sharing survey follow-up. Find survey here.
Survey results - please feel free to highlight items you would like to discuss or follow up on
KIC agenda planning for Feb-May 2011
Lunch and Learn Post Meeting with FirstTech. We will be discussing Promethean's recent announcement of their next-generation ActivBoard 500 which combines pen and touch inputs. We will also discuss ActivInspire 1.5.
Moundsview moving from Groupwise--is it possible to get the link or info to the presentation?
Why did Mounds View decide to drop Groupwise? What issues did Google Apps specifically solve?
Mail migration - what are other districts doing / what have you done?
SSO - Anyone using OpenDirectory?
Edina has stuck with Outlook and we forward Gmail to Outlook as Gmail is not archived for us
Interested in a Google Apps for Education Users Group? Molly, Ben and Sean are organizing a Regional Users group in collaboration with Google. Sign up on this form to find out more information when it is available.
U of MN presentation:
Initiative started in 2008 seeking to outsource student email solution and Google Apps was seen as viable. Once the students got there, the staff (summer 2010) wanted to be there for collaboration, calendar and communication purposes. Now supporting 43K+
Concerns: Risk-related issues re:security. Also, the University is more conservative in deciding when to update new features or “turn on” Google’s commercial applications. Increased bandwidth usage has not seemed to be affected, except concerns on Google’s end (Osseo has seen this).
Advantages: Cost-saving, collaborative, periodic updates in latest features. Efficiency with ONE simple system (thus, not offering Microsoft 365, for example).
Stage 1 = Talk about it. Say it is coming. Keep private information OUT of Google Apps (i.e. grades). Privacy and Acceptable Use policies as living documents communicated to students and staff.
Stage 2 = Initial implementation on an “opt in” basis with sign in page and Google agreement. Training a group sessions across campus. Weekly communications with IT support. Co-ordinate campuses across the state are included, Duluth, Morris, etc. (each has its own domain, but is managed by TC campus IT).
Stage 3 = Final push with everyone included in the system by June 2011. Refer questions and needs to Google Help as much as possible, ex. individuals connecting their mobile devices to the system. **Distinguish use of Google spaces vs. secured University systems. Have IT point people (leaders) in each college, each department, etc. as specialized support people.
IT issues: using the Google SAS70 II. Worked with Google and the University’s internal auditor and compliance teams. Districts can piggyback on the U of M due diligence in their implementation.
For all who are interested here is a link to information on retention schedules. I am not totally certain that this answers are here but it appears to be a useful resource: State Retention Schedules