| Text Only | |
|
| |
|
| |
|
| |
|
| |
| | |
|
| |
|
| |
|
| |
| | |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
| | |
|
| |
|
| |
|
| |
|
| |
|
| |
![]() | |
|
|
|
![]() | |
|
|
|
|
Those requesting software be installed in campus labs need to meet
the following requirements:
Software must be used for a University approved function, such as class work, research or training. First time Lab Software Installation Request applications require a meeting with a Network Manager. This meeting is required to assist in determining the memory, disk storage, and other resource requirements the software application has, and whether or not a facility is available which will accommodate the software. It will also allow for sufficient time to resolve any software or hardware issues not anticipated. The time required to properly install, troubleshoot, and test software requires the following installation schedule:
Software must come with proof of ownership and license. The license must allow for the software to be used in a lab environment. Software submitted must be compatible with SoftTrack (software monitoring program), Fortress, Norton Anti-Virus and lab hardware configurations. Software must be thoroughly tested by someone completely familiar with its operation. Testing must be prior to the scheduled release date for activation in the computer lab(s). Academic Computing will make a cursory test to insure that the software runs simultaneously on all machines requested for network access. Software specifically used by a faculty or staff member for a class, research or training will remain on the server (in the lab) until the end of the academic school year. Notification of removal of software will be forwarded to the responsible faculty member and the chair person the week of Spring Break (usually mid-March). If the software is to remain on the server longer, a written notification must be received prior to the end of the academic school year. All software will be removed, unless notification is received, at the end of the academic school year. Problems, which arise from installed software, should be carefully documented. This information should be forwarded to the network manager or Lab Manager immediately. Requests for upgrades, patches, plugins, additional licenses, etc. must be submitted in the same manner as a request for new software installation and according to the installation schedule shown above. Lab Software Installation requests are processed in the order in which they are received and when required for class, research or training. Installation will only begin after the initial meeting. No software will be released for campus lab network access until all license information has been received and is on file. Copies of the original software diskettes will also be kept on file. UW Oshkosh Webmaster URL: http://www.acs.uwosh.edu/acslabs/lsftinst.shtml Last updated: Monday, December 18, 2000 - 03:22 PM |