Computer Lab and Technology Classrooms

Software Installation Procedures

Each semester, the Penn State Scranton IT department reviews the software packages installed in the academic computer labs and technology classrooms.  As program needs change, new software may be required in our computer labs and classrooms.  The following contains information on the policies for requesting the installation or upgrade of software in our academic computing labs.

These guidelines are designed to facilitate a stable and user friendly computer lab environment at Penn State Scranton. 

The following procedural steps take place when requesting new or upgraded software:

Make the Software Request

Submit a written request to [email protected] no later than eight (8) weeks prior to the semester requested for.  This lead time ensures that minimal disruption occurs in our computer environment.  Requests for software should be made prior to every semester you will be using the software.  Do not assume software will be available just because it was in the past.

  • The request should contain the following information.
  • The name of the instructor using the software.
  • The name of the course(s) using the software.
  • Where you want the software installed.  Please keep in mind that a license will be needed for EVERY computer in the room you are requesting.
  • The start date and time of the course using the software.
  • The budget number to charge, if applicable.  You should obtain approval for the software funding and provide proof of approval and funding with your request. Please consult with the IT department for current licensing fees.
  • Complete information regarding the software.   This information should include suggested vendor, software title, requested version and any links to web support pages.

After the written request is made, the IT department will evaluate the software for suitability in our computer labs based on the software compatibility criteria in the next sections of this document.   You will receive a written approval or denial from the IT department regarding your request.

Software Compatibility Issues

We make every effort to fulfill all software installation requests, however, some requests may be denied based on the following.   Below are some common issues that may cause a software request to be denied. 

  • software is alpha or beta release
  • use violates existing laws, copyrights, or University policy 
  • is not of an academic nature 
  • is outdated or requires a back-version of another application 
  • has a malicious effect on the computing environment 
  • software requires elevated privileges to operate 
  • requires hardware copy protection or uses invasive copy protection schemes

Should any of these issues prevent us from installing the requested software, the IT department will notify you.

Software Support

The IT department will do everything possible to ensure the software application is fully functional.  Please note that we cannot guarantee the functional operation of software that is no longer supported by the vendor.

Software will be upgraded with critical patches during the semester as necessary.   Please note that this is the only time during the semester that software will be installed or modified.  Software cannot be installed by the user under any circumstances.

You are a critical part of the support of our computing environment.  Please take the time to test your software before classes start and report any problems to the IT department.  Report any errors that you may have during the semester promptly to the IT department using the online forms, calling the help desk or submitting a paper trouble report sheet found in each lab.

Software Purchasing & Licensing

All software requested will be purchased by the IT department.   The IT department maintains all licensing and documentation for all software titles installed in the academic computing labs.  All license agreements will be strictly enforced.

The IT department is also available for consultation as needed to determine the appropriate locations for installation.

Effective Date: July 1, 2006