CLC regularly evaluates and installs software packages requested by instructors. Please review these policies and procedures before making a request.
- Requests must be received at least 8 weeks prior to the beginning of the semester in which you wish the software to be used.
- More time may be needed for applications that require a license service, are difficult to install on public shared systems, or have compatibility problems with the existing application suite (see below).
- 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.
- When different incompatible versions of the same software are requested, the earliest request will be selected.
- New versions of existing applications are generally not updated after the start of a semester.
- 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.
- Students using courseware installed via an instructor request are to be supported by the instructor. That is, instructors should provide usage instructions and help with the software to the students in their class. CLC and the ITS service desk cannot be expected to answer questions about how to use such applications.
- General purpose applications installed in all locations are supported a number of ways: see our Support page.
Occasionally we can not install an application because of incompatibilitywith our systems. 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:
- Application is outdated or requires back-level version of another application.
- Concurrent usage limits are required by the license but cannot be controlled.
- Requires hardware copy protection or uses invasive copy detection methods.
- Application has no "silent install" option . . . that is, it requires a user be present to click on a dialog box such as a license agreement.
- Requires users have write access to servers or the local operating system.
- Has a malicious effect on other production software.
- Violates existing laws, such as copyrights.
- Violates University policy or conflicts with the University’s mission.
- Is to be used for human research and lacks an Office of Regulatory Compliance IRB number.
Last Updated December 2, 2015