Learning Applications and Technologies regularly evaluates and installs software packages requested by instructors. The following policy applies to any request for software to be installed in TLT computer labs and classrooms. Please review these policies and procedures before making a request.
- Requests must be submitted at least 8 weeks prior to the time you need the software.
- Requests received with less lead time will be processed on a “best effort” basis and applications may not be available for use at the start of the semester.
- New versions of existing applications are generally not updated after the start of a semester.
- More time may be needed for applications that require a license server, are difficult to install on public shared systems, or have compatibility problems with the existing application suite (see below).
- Software specific for a particular course and not beneficial to the general student population is usually purchased by the requesting instructor’s department.
- Sufficient documentation for proof of purchase must be provided before the software can be installed.
- If the software will be using a department license server, please provide a technical contact who we should work with.
- Students seeking support for courseware should contact their instructor. Instructors should provide usage instructions and help with the software to the students in their class.
- Any problems or issues with the installed software (i.e. error message, missing, etc.) can be reported on our Support page.
- Support for general purpose applications install in all locations can be found on our Support page.
Occasionally we cannot install an application because of incompatibility with our systems. The challenges with installing applications on numerous shared, locked-down public systems are much greater than installing the same thing on your own private system. Common issues include:
- The application is outdated or conflicts with software already installed on the system.
- Software Licensing prevents installation in a multi-user environment or cannot be properly controlled.
- Violates University Information Assurance and IT Security policy (AD 95).
- Violates existing laws (i.e. copyrights), university policy (AD 96), or conflicts with the University’s Mission.
- Used for human research and lacks an Office of Regulatory Compliance IRB number.