Requests for installation of discipline-specific specialty software can be made to Systems Labs via use of our request form. Please read the following information and restrictions regarding installation of specialty software. By submitting an installation request to Systems Labs, you agree that you have read and will abide by this policy.

Those planning on acquiring software for use in our labs are urged to contact us before purchasing to ensure feasibility of using the software in the Systems Labs environment. We will be happy to work with you to find the best and most cost-effective solution for your software needs. Although we encourage you to submit a request via this form as early as possible, we will not consider the request to be complete until we are supplied with media.

Deadlines for Requests:

Semester Software Needed	Deadline for Request
Spring	Thanksgiving Break, previous Fall
Summer	Spring Break, previous Spring
Fall	Before last day of classes, previous Spring

Software installation is a lengthy process requiring documentation, testing, and imaging and is done only during semester breaks. During semesters, we focus on correcting problems and maintaining the computers for the students and instructors who use them. Software requests that do not meet the above deadlines will not be honored as we do not install software during semesters.

Licensing, documentation, and media:
Copies of the proof of purchase of the appropriate number of licenses, the installation documentation, and the software media must be provided to Systems Labs before the above deadlines. If the requesting party would like to provide manuals for checkout from the helpdesk in the lab where the software will be installed, those manuals also should be provided at this time.

If the software and licensing is not provided by the deadline, the installation request may not be honored.

Compatibility:
All specialty software should be checked for compatibility with Systems Labs' computing environment prior to purchase. Software packages must be OS X native as the Classic environment is not installed on our computers. Installing software in a networked lab environment involves a number of extra steps that are not required when installing software on a individual computers. The software must then be tested for stability. Software that is otherwise compatible with the operating system we use may not be functional in our lab environment due to software administration issues, licensing, or other restrictions.

Any software that poses a threat to Systems Labs' security or operations, or that interferes with the normal operation of previously existing software will not be installed or may be removed or disabled if such a problem becomes apparent after installation. Software using hardware/software dongles may be refused due to the inability to protect such locks from theft and/or inability to provide lock servers.

Beta and Demonstration versions:
"Beta" version software will only be installed with the understanding that beta means that the software is still in the development stage. Problems usually are unsupported and solutions may not be available or available in a timely manner. Systems Labs staff cannot be responsible for finding solutions for problems with beta software beyond installing updates or patches.

Demonstration software will not be installed without written permission from the developer allowing the software to be used on multiple computers for an extended period of time. Demo software is intended usually for a one time use to see if you would like to purchase the software and is not intended to be a "free license" to continually use the software for a class. If such software is requested for a one-time demonstration use, exceptions may be made.

Testing:
Systems Labs administrators will test specialty software to ensure basic performance in our lab environment. As our administrators may not be experts in the use of all specialty software packages, it is the responsibility of the requesting parties to test the full functionality of the software and report problems to our administrators. We will make every effort to solve problems that result from a conflict with our environment, but solutions may not always be readily available. We encourage instructors to test software prior to the start of their classes to avoid surprises and give our administrators time to research solutions.

Maintenance:
Systems Labs' administrators will apply free updates available from software developers between semesters and on an as-needed basis, when doing so will solve a problem or provide needed functionality. Updates that have been shown to cause problems with the software in our lab environment will not be applied or will be postponed until a solution can be found. Software updates are done automatically and do not require a formal request from the party that requested the software.

Updates are small revisions to software, whereas upgrades refer to new versions. An update that takes software from version 3.0 to 3.1 is likely to be free, while an upgrade from 3.0 to 4.0 typically requires a fee. Most software is licensed by version, but some companies offer a time-limited license that includes free upgrades to new versions during that time period. Software with this latter type of license will also be upgraded automatically if new versions are released within the time period specified in the license and we are provided with the upgraded software.

Upgrades and Financial Responsibility:
It is the responsibility of faculty and/or departments who have purchased specialty software that has been installed on Systems Labs' computers to pay for needed upgrades as necessary. Periodically, as Systems Labs upgrades operating systems or makes other changes, upgrades to software will be necessary. Failure to finance and provide licensing for updates for installed software may result in its removal.

It is also the responsibility of the purchaser to provide proof of current licensing for specialty software. If the original licensing period expires and is not renewed, the software will be removed from the computers.

Software Support:
Primary support for the functionality of specialty software is the responsibility of the requesting party. The student lab consultants are trained to support Systems Labs' standard software packages, but are required to provide only basic support for specialty software. Basic support includes running the program, opening and saving files, and printing. Additional information about known issues may be found on our documentation page. If an instructor finds a common problem that s/he would like addressed on the documentation page, a request to add it can be made to virginia @ uky.edu.