1.
No computers in the open lab configured like 522 so that my PC
Operating student can do homework in there.
2.
Instructor O: drive comes and goes without notification or
reason. I keep all my instructional material there and need it in the
classroom.
3.
Servers are down for upgrades/maintenance/whatever during class
times and teachers are not notified in advance.
4.
Security!!
breach!!
We need to be told immediately about any possible
5.
Web page problems sometimes occur because someone has renamed a
server or done something else and not notified teachers, Charles, or
Joe!
6.
Teachers need more permissions in our labs so that we can
check/fix minor problems (like printing problems) without having to
submit a work order.
7.
Connecting to the Public and Personal network drives from home
works only sporadically.
8.
I'm not sure that letting students create their own user names
and passwords is working well, especially for Internet students.
9. The Audio at Taylor (when teaching videoconferencing from Temple to
Taylor) echoes. I have had several complaints from the students at
Taylor. A lot of the time they cannot hear and the devices are
positioned where they are supposed to be.
10.
Passwords and computer security.
11. Better communications between IT and the CIS department.
Upgrades, changes, etc. Keep us informed as to what is/needs to be
done.
12. IT department does not warn anyone prior to making changes that effect our
department. Even though we have come to you on a number of occasions to
resolve resulting problems, IT continues to do the same things which disrupt
classes, and degrade classroom learning.
13.Access to LAN resources such as the O Drive, and assessment server are
unreasonably restricted from student access.
14. Issues such as passwords being lost are not addressed quickly and resolved in an
expeditious matter allowing unauthorized access to grades, and test materials.
15. Not having capability to save on C drive during class causes significant reduction
in classroom productivity. These are significant problems that could have been
resolved with some active coordination between you and the head of the IT
Department. You have not done this.
16. Provide our department with our own "CIS" server. Our
department functioned successfully for years and without many
problems when no other users were on the server except
the CIS students. The "CIS" server would not have
to be upgraded or modified as often as the "universal" server.
If step 1 above is implemented there will be no need to address
all the concerns listed below.
17. Notify instructors when passwords to their "O" drives
could be in the hands of unauthorized people. Two months
after-the-fact is a little late.
18. Do not allow IS Technicians to have access to instructors
passwords if the technician(s) are taking courses at TC.
19. The IS Server should not be randomly rebooted without notification
to the instructors and the students currently logged in.
20. Eliminate the installation of new servers just days
before classes start. This practice has caused instructors
several problems at the beginning of the semester.
21. Installing new software in the classrooms without notifying
the instructors.
22. Provide a checks-and-balances system the allows communications
between IS and the CIS department.
23. Continual unconcern from tech people about immediate problems when teaching
a class.
24. Being given a smart remark when asking for assistance with a problem and then
promptly being ignored by the person leaving without answering the question. (I’m
sure it was an attempt at being funny, but I needed a serious answer.)
25. Problems with software that is loaded on the computer and instructors being
locked out of student machines by security. There are some problems that we
could fix, if we could get into the system.
26. Such strict security in our labs. We cannot even make minor changes and at times
it interferes with students being able to accomplish a task. We have to work
around the security and do things in a roundabout way to get them accomplished,
if we can get them done at all.
27. Not being able to find someone to solve an immediate problem that interferes
with teaching. This sometimes means the dismissal of class because of hardware
or software malfunction.
28. Instructor’s machine not having the same software as the student machines, or
current software. Either the instructor’s machine has been updated and has
features that the students do not have, or the students have a different version of
the software and cannot complete the class requirements. Having to teach without
PowerPoint, or notes or examples because the instructor’s machine is
malfunctioning.
29. Network changes without notification and these changes taking place on the first
day of classes or some other inconvenient time. The network is taken down at
any time without any warning and without consideration to those of us who
depend on it for our classes.
30. Network difficulties and no one seems to know about them or care if they are
fixed or not.
31. Wizards and clip art not being loaded with software.
32. Superior attitude of techs to instructors. They cannot do anything without a work
order. They also now have their own little room that is locked that we cannot
even get to them to ask questions or have them correct problems, although they
probably wouldn’t correct it if they could.
33. Inability to have complete control over our web sites, especially for our Internet
classes when changes may need to be made immediately, but must wait for the
transfer overnight.
34. No one knowing anything when you ask a question. Being shuffled from one
person to another, and still not getting a complete and accurate answer to your
question. Different people being in charge of different things, and we don’t know
what anyone is in charge of.
35. E-mail problems and no one knows why, or even that they exist.
36. Inability to effectively do my job because of software or hardware malfunction.
Looking like a fool when teaching class because there is a problem with the
software or hardware, and I can’t do anything about it except say “blame the tech
people. They don’t let me make those changes.”
37. Complete and total lack of communication. If there is communication, it is
delivered in a condescending way like we couldn’t possibly understand. I think
they don’t understand, so they are attempting to hide their lack of knowledge.
38. Most of the time when I ask a question about a problem or a system, I get the
impression that the person that I am talking to has no idea of what I’m talking
about or how to solve it. They always have to “get back to you.” By then, it is
generally too late for the answer to do any good. The next time the same thing
occurs, changes have been made and the original answer is no longer valid.
39. Instructors do not know what software is available in each lab and changes are
made without notification. Example is changing the student machines to
Windows XP, and leaving the instructor’s machine with Windows 2000. It is
difficult to show students how something works if it is different
40. Instructors do not know what hardware is available and where it is located.
41. Breach of security with faculty passwords, and no notification about the potential
problem.
42. Cumbersome process of getting students set up on the system at the beginning of
the semester.
43. “O:” drive data disappearing without warning causing student to lose work.
44. Email problems with students trying to send in their assignments. Outlook
Security blocks all “.mdb” files which are Access files and necessary for class.