Chrome Extension and Student Devices

CHROME-EXTENSIONS

We’ve made some changes this year with how students access and use Chrome extensions.  We discovered last year that many students were using certain Chrome extensions to circumvent our internet filtering and logging.  The extensions in question were various VPN and proxy extensions.  Many of these extensions have legitimate uses outside of the education realm.  We tried blacklisting the ones we knew about, but, there are new ones published all the time.  So, the only way to ensure that students could not access these was to block all extensions and allow only whitelisted extensions to run on student devices.  This is a change we really need to make to ensure that we are complying with CIPA.

This does not mean that students cannot use Chrome extensions, however. But, they must now get them approved before they can use them.  Here’s the processes we’ll be using — depending on device and scope.

For students using Macbooks, the request for the extension must be approved by a teacher.  Teachers should email any member of the technology department with the name of the of the extension — a link to it from the Chrome Store would be great, too — , who needs it, and the date when needed.  Assuming the extension in question is not one used to circumvent filtering/logging, etc… we will whitelist the extension in the Google Management Console.   If the request is for all students, we can push the extension out via Casper.   If the extension is for a small number of students (less than a grade level), we will create a Self Service package that students can use to install the extension.  My team will need at least two days notice to complete these tasks.

For students using Chromebooks, again the request must be approved by a teacher. Teachers should email any member of the technology department with the name of the of the extension — a link to it from the Chrome Store would be great, too — , who needs it, and the date when needed.  Assuming the extension in question is not one used to circumvent filtering/logging, etc… we will whitelist the extension in the Google Management Console. If the request is for all students, we can push the extension out via the Google Management Console.  If the extension is for a small number of students (less than a grade level), it will be available for students to manually install from the Chrome Store.  As with the Macbooks, my team will need at least two days notice to complete these tasks.

Posted in For Students, For Teachers, Tech Tips | Leave a comment

Minor Change to Campus Messenger

campus1

Based upon teacher feedback and some changes we’ve made over time, we’ve tweaked how Campus Messenger now works.  It is now set so that the default “from” address or sender address is the email address of the person logged into Campus.  This means that when you create a new Campus Messenger email, it will automatically put in your email address as the “from” or sender.  This is a change.  Previously, the default “from” or sender address was “messenger@crprairie.org”.  This should make life a little more convenient for teachers when sending class emails to students and parents.  If teachers left in the “messenger@crprairie.org address, parents and students could not reply to these notes and reach the teacher.  This should make personalized communication to students and parents a little easier.

We are keeping the “messenger@crprairie.org account around, however.  There may be times when staff feel the need to broadcast a message that does not need to be responded/replied to.  In these cases,  staff will need to manually change the “from” or sender address back to “messenger@crprairie.org.  

Posted in Tech Tips | Leave a comment

First Responders and Digital Literacy Trainers for 2016-17

DLT 2016

It was great to see all the new Prairie teachers yesterday!  What a great group!  For their reference and everyone else’s, below is a list of the Digital Literacy Trainers and Technology First responders for the 2016-17 school year.

Digital Literacy Trainers (DLT)

Prairie Crest:
Becky Sammons
Courtney Coughlin

Prairie Heights:
Kelly Rudd
Courtney Templeton

Prairie Hill:
Brad Koch
Tricia Ward

Prairie Ridge:
Tara Tolly
Laura Hahlen

Prairie View:
Mark Ganzeveld
Shalyn Huerter

Prairie Creek:
Marija Musselman
Patrice Becicka
Ernie Cox

Prairie Point:
Martha Wilding
Emily Nash
Megan Hanson

Aric Folden

Prairie High School:
Sarah Oldenkamp
Kim Hynek
Kent Noska
Amy Jabens

While our DLT team certainly does know the “nuts and bolts” of fixing tech problems, we have another team that we rely upon to help us for more “techie” problems – our Technology First Responders. These are great folks to turn to for help when you have a technical problem. They can either fix it themselves or get a ticket started for you if the job is a bit more complex. Here is the list of First Responders for for all buildings:

Technology First Responders

Prairie Crest
Andrea Hora
Faith Curtis

Prairie Heights:
Judy Janssen
Kelly Rudd

Prairie Hill:
Dona Howe
Brad Koch

Prairie Ridge:
Lori Pleiness
Lindsey Shaull

Prairie View:
Audrey Kossayian
Mark Ganzeveld

Prairie Creek:
Stephanie Johnson
Marija Musselman

Prairie Point:
Jesse Gearheart
Michelle Walter

Prairie High School:
Sarah Oldenkamp
Kim Hynek

Prairie Edge:
Leah Gass

 

 

Posted in For Teachers, Tech Tips | Comments Off on First Responders and Digital Literacy Trainers for 2016-17

Start the New Year Grieving

Honeycutt 2016

On Monday, I saw something remarkable.  We hosted Kevin Honeycutt to present digital literacy PL to our staff.  During the keynote, he produced a headband that wirelessly monitored his brain’s activity in real time via a smartphone app.  The Melon app tracked his level of focus and showed graphs that displayed the distribution of his brainwave frequencies.  The core idea is that higher frequencies indicate higher cognitive load and engagement.  This device can give immediate, easily understandable, and measurable data on physiology of student engagement.  It’s a little like a Fitbit for the mind.  Kevin posed the question, “How would your teaching or instructional design change if you could view this type of student data?”  He then challenged everyone in the room to act as if they did have a tool like this all the time.  In other words, make engagement core to the work of teaching.  This was a great message — a powerful message.  And, while I agreed and appreciated what he was saying, all I could think about was Koan.

My youngest child, Koan, was born eight years ago.  If you don’t know, a “koan” is an answerless riddle that Zen-Buddhist monks meditate upon (and try to answer) in order to reach enlightenment. A well known koan is “What is the sound of one hand clapping?”  We named Koan before he was born.  

Just a few days after bringing him home from the hospital after he was born, he began to have grand mal seizures.  He spent the next month in the NICU while various medical professionals looked for a diagnosis.  When he was around four months old, the seizures stopped.  But, we were already starting to notice that he was missing developmental milestones.  As time went on, it was pretty clear that Koan was going to face some significant challenges.  Our worry was compounded by the fact that there was never a formal diagnosis or label to describe what had happened to him. He was a true riddle; his own namesake.   The uncertainty in those first few weeks and months was almost unbearable.  Koan continued to grow and develop but at age eight, he does not walk or talk.

Koan

When I saw Kevin’s headband, I wondered about the type of data we would see if we put this on Koan.  With Koan, I’ve always believed that he was processing more of the world than he can show.  This headband might be tool to see into his mind: it might just give us another way to get to know him.  When I shared this idea with Kevin, he could not have been more kind and generous.  He insisted on meeting Koan.   He shared his perspective and his expertise on what might be happening inside Koan’s world.  He also loaned us the headband.  So, over the next few days, we’ll be gathering baseline data on ourselves and Koan to help us understand what is happening with Koan.  I’ll keep you posted on what we find.

While this is a great story and remarkable all on it’s own, a more powerful idea emerged out of a conversation Kevin and I had as I was driving him back to the hotel.  Earlier in the evening, Jeri had related some powerful advice she got from a close friend when it became clear that Koan would face some challenges our that other kids would not.  “Take time and grieve for the child you thought you were going to have.  Let that go. And, then love the child you have.”

It’s become clear to me that there’s is an important distinction between preconceptions and expectations.   My preconceptions about who Koan should have been were the root of my negative emotions: worry and fear.  I don’t mean that these preconceptions were wrong, bad, or somehow unhealthy.  They’re a byproduct of hope — the best of things — to quote Andy Dufresne.  Preconceptions are normal, understandable, and reasonable.   But, when the train goes off the track, they become inherently empty.  The anxiety I experienced due to missed milestones were not helpful to Koan.  So, they were not only making me unhappy, but worse, they were getting in the way of me being at my best to help Koan.  

By embracing the available  joy,  the small successes, and even the short falls Koan experiences each day — each moment — I am able to see and sometimes find my best self.  I started to rely upon more global expectations rather than specific preconceptions.  Jeri and I developed three big expectations we share with anyone working for Koan:  happiness, good health, and independence.   These three ideas guide everything we do with him from planning his trust, setting IEP goals, or working with therapists or respite workers.  When we see growth or progress on any of these expectations, no matter how small, it brings us great joy.  And, this is an incredible gift that Koan has given us.

As I was articulating this idea to Kevin, he something remarkable — “What if each year teachers took time to grieve for the kids they hoped to have,  acknowledged that grief, then put it aside to embrace and love kids that are there?”  What a powerful idea!  As funny as it sounds, I had never until that moment translated this personal understanding to a professional one.  Put aside the preconceptions that naturally appear with hope and excitement, and accept the reality of the present.  This doesn’t mean abandoning high expectations or the belief that all kids can do great things:  Success for All!  But, acknowledge that our preconceptions of how things “should be” can be a significant obstacle to doing our work well.  

I encourage all of you to relish the anticipation of the start of the school year.  There are few things in life that are better than hope and anticipation.  But, when you hit that first big bump in road, take some time to grieve for your preconceptions. Let them go, maintain your high expectations, and embrace the gifts your students are offering to you right now.

Posted in Digital Literacy, Features | 2 Comments

New iPad App Purchase Process

iPads

As I wrote last spring, we spent a lot of time working on iPads this summer.  Apple has redesigned a lot of the management tools, so we also redesigned our local app purchase process.  We believe it’s simpler for everyone.  

Here’s a PDF that shows how the whole process works.  However, there are really only two things you to do to make a purchase:

  1. Complete a requisition form and send it to Lisa Smith in the business office.  Of course, to complete the form you will also need to know the account code that will be used to pay for the purchase.
  2. You will also need to complete a Google Form that Angela Sleeper will send directly to you once she gets the requisition from Lisa.  In order for us to automatically deliver the new app, we’ll need to know the asset tag number, serial number, and Apple ID associated with the iPad.  The Google Form gives instructions on how to find all three.

Here are a few additional things to keep in mind when purchasing apps going forward.

  • This new procedure is the only way we will be purchasing apps.  There are no alternative methods.  We worked with the business office to develop a streamlined process that still meets all of the Iowa DE and federal legal rules for the use of public funds.  These are the rules that prevent us from being able to use iTunes gift cards.
  • There are no redemption codes or anything you need to do to install the apps.  Once you complete the Google Form, we will push the app(s) to your iPad(s) automatically.  App updates will also be automatically applied.
  • The new process will allow us to seamlessly give and take back apps from devices.  We could not do this before.  So, for example, an iPad goes missing or is stolen, we can revoke the apps on that device and automatically redeploy them to a new device.  
  • Again, we will be using this new purchase system exclusively, and as I indicated in the spring, it only works with newer iPad hardware.  It will not work work with anything that does not use a “lightning” sync cable — the thinner one.  The older 30 pin (larger) sync cable iPads won’t run this new system.  So, this means that you can still use older hardware, but you cannot purchase new apps for these devices.
  • Apple’s new management system will only work with iPads that have been purchased directly from Apple.  We cannot manage iPads that were purchased from resellers like Target or Walmart.  So, if a device was not purchased directly from Apple, we can’t manage it, and, therefore, we can’t purchase apps for it.  For the last three or four years, we’ve had a policy that requires all iPad purchases to be done this way.  Now, it is essential  that all iPad purchases come through the district technology office.  This would include iPads that are purchased by PTOs, the booster club, from grants, etc…
Posted in For Teachers, Tech Tips | Comments Off on New iPad App Purchase Process

Kevin Honeycutt at Prairie on August 8th

Kevin Honeycutt

Save the date if you’ve not already done so, August 8th.  Kevin Honeycutt will be here at Prairie again to provide world-class PL on digital learning.  If you are looking to strengthen your digital tool kit, please attend.    Here are the details:

Date: Monday, August 8th

Time: 8:30AM to 10:30AM

Where: The CCSD Concert Hall

As we’ve done in the past, we will provide door prized to attending staff — including two iPad minis for classroom use. Drop me a a note if you have questions.

Posted in Digital Literacy, For Teachers, General | Comments Off on Kevin Honeycutt at Prairie on August 8th

2016-17 Technician Assignments

Prairie Disater3

Here are the 2016-17 technician role assignments.

  • Sam Ketchum.  Hours: 8:00 AM to 4:30 PM,  Location: Prairie High School Library.
  • Chris Ketchum. Hours: 7:30 AM to 4:00 PM, Location: Prairie Creek Library AM (7:30 AM to 11:00 AM)/District Technology Office PM.
  • Collin Knoll.  Hours: 7:00 AM to 3:00 PM, Location: District Technology Office
  • Charlie Braun. Hours: 7:30 AM to 4:00 PM, Location: Prairie Point Library.

Sam, Chris, and Charlie will start working in their building locations on the first student day on August 23rd.  If you have a question or problem before then, feel free to reach out to Angela (848 5240 if you don’t have access to email) to get a ticket started.

We periodically switch roles to cross-train and grow our collective department knowledge.  We are keeping Sam at Prairie High School since he did such in-depth (and great) work over the summer to construct the student MacBook software load.  We are excited to get the year started!

Posted in For Teachers, Tech Tips | Comments Off on 2016-17 Technician Assignments

NWEA Teacher Logins

NWEA

 

One of the questions we’ve gotten quite a bit regards how our change to @CRPrairie.org email will impact teacher logins to NWEA’s MAP site.  Last year (15-16) the answer was not at all — nothing changed since we were forwarding email from @PrairiePride.org accounts to @CRPrairie.org addresses.  However, since we have stopped forwarding email from @PrairiePride.org addresses, we will now need to update virtually all logins to the NWEA MAP site.  Here’s some Q and A on how this process will work.  Let me know if you have additional questions.

Q: What will my new username to the MAP site be?

A:  It will be your full @CRPrairie.org email address.

Q: What will my new password be?

A: When you account is updated, you will receive an email from NWEA requesting you to reset your password.  Just follow the onscreen instructions.  If you lose the reset email, you can go to https://teach.mapnwea.org  and click the “forgot password” link to force the process manually.

Q: When will my new account be ready?

A: New accounts should be ready in early August.  So, look for the password reset email sometime on or after 8/1/16.

Q: Will have access to the same historical reports and information I had with my old account?

A: Yes.

 

Posted in For Teachers | Comments Off on NWEA Teacher Logins

Meet Our New Web Content Filter — Securly

This summer CCSD changed web content filters and went with Securly.  While no product in this space is perfect, I believe that Securly provides some really interesting, (and hopefully useful) features.  Below is a a Q and A on how it will work.

Q:  Why did we change filters?  

A:  While we liked iBoss for the most part, the way they filter off site (take home) devices was causing a bottleneck.  There was a noticeable negative performance hit when devices went off site.  This was the main problem we were looking to solve.  In our evaluation of new products, we liked Securly’s model to address this type of problem.  Securly is totally cloud-based with no hardware located at CCSD.   So, there’s no performance slow down for taking a device off the CCSD network.  However, once we looked at the full set of features, we really liked the other things Securly had to offer.  Here’s a quick list:

  • Seamless integration with Google Apps for Education.  Student and staff will use Google account information to login to Securly.
  • Clear reporting.  We can now see — in an easy to understand format – an account’s web history, search history, video history, and social media posts (Facebook, Twitter, and Google+).Securly Video log
  • Teacher Whitelists.  Teachers will be able to whitelist sites on the fly for the day.  If you need a site whitelisted permanently, please contact the technology office.
  • Active content flagging — Tracks and reports activity on social media (Facebook, Twitter, and Google+) with negative sentiments like grief, self harm, or bullying.
  • Coming Soon — Securly Parental Portal.  Before the end of the calendar year, Securly will rollout their version of the Parental Portal.  Parents will be able to login and see all of the browsing history, search history, and social media history for their children when they are using school devices.  There will be the option for these reports to be emailed weekly to parents.  Parents will also be able to make filtering more restrictive for their children when browsing at home.

 

Q: How will Securly work differently from iBoss?

A:  There are several key differences, and we are implementing these changes in different ways based upon building grade level.  For our 5th grade through 12th grade buildings (including Prairie Edge and Prairie Delta), All users will be forced to login to Google when they open a web-browser each day.  While this sounds a bit cumbersome, it should not be too troublesome as this login will also work to open Gmail or the other Google Apps for Education tools which is probably something we all do each day anyway.  This will be true for both students and staff.  The reason for forced login is that it let’s Securly know who you are.  That way we can give students the proper filtering policy and we can also give staff the appropriate policy (which in addition to being more permissive allows for whitelisting).  This forced login also makes reports and logs much more accurate.

In out K-4 buildings, we felt that a forced login would be too difficult for our youngest learners.  This would mean that kindergarteners would need to remember and type in their Google email address and password before doing anything online.  The trade-off with doing things this way is that we will lose almost all ability to log or track what’s happening with specific accounts while online.  In other words, we won’t be able to run user history reports.  But, this seems like a necessary trade.

 

Q: How will this work with personal devices?

A:  Securly requires that we install a security certificate on every device that connects to our network. While this sounds scary and very technical, it’s actually a very simple, one-time process.  This summer we installed this certificate on all office computers, all student Macbooks, all iPads  that we updated as part of our summer work, and we pushed it out to all student Chromebooks.  We did not get it on any staff MacBooks (unless you got an updated computer this summer) and, of course, it’s not on any personal devices.

Again, the certificate is really easy to install.  We’ve put a link to it on our district website  and a lot of you will be able to do this independently.  Just download the certificate and follow the on-screen instructions for installation.  On MacBooks, it does need to be double-clicked to start the process.   If you don’t install the certificate, you will not be able to access any secure site — such as Gmail, YouTube, etc…  On the website, behind the “Securly” button we have screencasts on how to install the certificate on various devices.  Of course, if you get stuck or have questions, don’t hesitate to contact Angela to setup a time for one of the techs to have a look at it.

 

Q:  When will we start using Securly?

A:  UPDATE —We are already using it with student take-home Chromebooks.  We implemented Securly for all onsite devices on 7/20/16.

Q: UPDATE –Why doesn’t my personal Gmail account work here at school with Securly?

A:  Personal Gmail accounts will now work for both staff and students on the Prairie network.  We were never happy  restricting it.  So, we kept working on a new solution to solve the particular problem with student use.  We came at this problem from a different angel and this  new approach allows us to remove this restriction.  I’m sorry for any inconvenience this restriction may have caused.

Posted in Features, For Students, For Teachers, Tech Tips | Comments Off on Meet Our New Web Content Filter — Securly

Summer iPad Updates

iPads

It’s been an interesting spring in terms of Apple and iPads. It’s pretty clear that they are feeling the pressure from Google and the expansion of Chromebooks into schools. Apple has released a bunch of really interesting features in the iOS 9.3 update — the software that runs iPads. It’s basically Apple’s answer to Google Classroom and then some. Many of theses features we’ll use, others are not practical for us. Here’s Apple’s full description of all the features in the update. This new software will have a direct impact on the technology office summer work.  Here a few of the changes and how they will impact day to day use of iPads.

New App Purchasing Process on the Way:
Hallelujah! Apple has completely re-invented their app purchasing process for schools. Here are the relevant changes in their new system:

  • Apps no longer need to be tied to an Apple ID!
  • Apps can be moved from device to device. So, we can deploy and app. Take it back. And, move it to another device with or without an Apple ID.

These new features make it much easier to institutionally manage a software catalog. So, we have redesigned and simplified our internal app purchasing process.  More information that will be coming before school starts. However, all apps purchase for the 16-17 school year (after 7/1/16) will use this new system exclusively.  Here are some highlights from the process:

In this new model, there will be a strict 1 license to 1 device limit. In the old model it was possible to purchase an app (which was tied to a single Apple ID) and then to put that Apple ID on many devices. I’ve heard that we had cases where we’ve had one app license on forty devices. This won’t work in the new model. If you plan to have the app on 10 devices, you now will need to purchase 10 licenses.

The iOS 9.3 update has hardware requirements. Basically, it will only run on iPads that have been purchased after 2012. The simple way to tell if a device is supported is that it will have the newer “lightning” (smaller/thinner) charging sync cable. iPads that have the old 30 pin (larger) sync cable cannot take the update. This means that we will not be able to purchase apps for these older iPad models or iPads that have not been updated to OS 9.3 or higher.   We will continue to support the older hardware, but we will be recommending updating/upgrading if you need to purchase apps for them.    Since the vast majority of older iPads were purchased with foundation, grant, building, or department dollars, it will be up to buildings to locate funding sources to replace/update this hardware.

One other interesting feature is that apps purchased and deployed in this new way should automatically update with out intervention from users. So, you won’t need to enter an Apple ID to update apps.
Classroom Management Tools in iOS 9.3
While there are some really cool tools in the update for managing and monitoring devices in iOS 9.3, unfortunately we can’t use these. The vast majority of our current iPad fleet — including the new iPads we’ll be purchasing this summer — will not meet the minimum hardware requirements to run these features. It appears that Apple is incenting schools to purchase more robust (and expensive) hardware. So, again, unfortunately, we won’t be using these features.

Posted in Features, Tech Tips | Comments Off on Summer iPad Updates