Virtualization allows multiple operating systems to run on a single machine. WCU piloted virtualization in 35 classrooms to make more efficient use of resources and streamline support. However, the pilot encountered issues like stuttering video and trouble with USB devices, impairing some professors' ability to teach. Faculty reaction ranged from quiet to opposed. WCU learned that virtualization is not ideal for all use cases and greater education is needed. Changes were made, like dedicated training sessions, and the following semester ran more smoothly as WCU continued pursuing effective application of virtualization.

1. Wrestling with Shadows:
The Tragedy and Triumph of Classroom Virtualization
John Nickel
Colby Deitz

2. What is Virtualization?
The process of running several operating systems on a single
piece of hardware
Numerous virtualized computers, servers, and applications
“live” in one location

3. What is Virtualization?
Traditional Architecture
Virtual Architecture

4. One Machine, Many
Parts
Make VM’s
VM vSphere 5.1
Connect to VM’s
VMware View Client
Gather VM’s
VMware Horizon
View Administrator

5. Spring 2013 Pilot
Distributed to 35 classrooms in 2 buildings

Were specifically chosen
Goals:

Make more effective use of limited resources

Streamline support of classroom spaces

6. Spring 2013 Setup

7. Counting down…
What did we know?
What did we expect to happen?
Successfully implemented in our
Technology Commons
Hard to anticipate the results – this
had never been done before
Would be most visible test of
virtualization at WCU
Knew that some would take to it,
some wouldn’t

8. What was the result?

9. Where did it fall short?
Video playback
Stuttering, choppy video
Effected all multimedia
What is “acceptable” is subjective
USB Redirection
Trouble using USB drive on VM
Mostly an education issue, as
opposed to a hardware/software
issue
Impaired professor’s ability to conduct class the way they were expecting to

10. Faculty Reaction
Ranged from quiet and apathetic to loud and opposed

Both individuals and departments
Overall attitude of discontent

11. Numbers don’t lie, but
they’re not everything

12. How did we react?
Utilized the “full” partition
Stopped work on projects to focus on tickets
Assembled a team from all areas of IT

Tested every part of our virtual environment

13. What did we learn?
Virtualization is not the be-all-end-all for everyone
Need to be aware of our clients and their different use-cases
There needs to be a tangible benefit to IT (if not, then why do it?)
Software/curriculum needs
Student’s don’t react the same as faculty

14. Students
Don’t provide much feedback
Accept something is the way and
adapt
More fluid – accepting of change
If they can do their work, they’re
happy
Faculty
Quick to say when something
isn’t working the way they
want/need it
Greater need for technology to
work a certain way

If not, then it can stop class
in it’s tracks

Can be harder to workaround things

15. A new day dawns…

16. Shining brighter with
vCat

17. Shedding light
Greater emphasis on educating our clients
Scheduled several drop-in sessions over 2 weeks for training
and questions
Sent email notifications to all faculty, deans, and department
heads

18. Illumination
Found our professors have a greater need for multimedia, and not the
programs found on vCAT

Not a failure, showed us something we never realized before

Can leverage virtualization where it should be used
Not mandating they give up traditional methods, presented as a tool

19. Onwards and Upwards
Spring 2013 wasn’t fun or flattering for us
Listened, made changes, and acted appropriately

Beginning of Spring, it seemed like everything exploded

Beginning of Fall, everything just worked
Starting to pursue application virtualization
Don’t win every fight, but with perseverance and planning you can win the
war

20. Thank you for your time!
https://joind.in/9898
John Nickel:
johnnickel@wcu.edu
Colby Deitz:
deitz@wcu.edu