Indiana University Northwest
Campus Image  
Links
Meeting Minutes
Policies/Procedures
Contact Us
Meet our Members
Our Calendar
Computer Committee Home
IU Northwest Home 		 

Computer Committee
red line

Fall 2002 Laboratory Build Schedule

IUN Faculty & Staff:

The Fall 2002 laboratory build (both PC & MAC) will follow the dates below.

*May 29: All "Software Request" forms, licenses and software must be submitted to the Support Center (Help Desk) in Raintree 204 IN PERSON by 5:00 p.m. Note: All software MUST be accompanied by appropriate license for use. This means that if a certain piece of software is to be installed in every lab on campus, a site-license will need to be submitted. If installation is for only one lab, licenses for each machine in that lab must accompany the software. No exceptions whatsoever will be made concerning proper licensing.

June 3-7 The prototype build will be created and internally tested by IT staff.
June 10-14 Test of ghosting procedure and preparation of Savannah/Marram Lab for open testing by faculty and students.
June 17-July 26 Open Savannah/Marram Student Technology Centers for faculty and student prototype testing. Problems to be reported to Support Center (Help Desk at x4357).
July 29-Aug 9 Faculty testing of prototype build, location Raintree 204 from 9 a.m.-5 p.m. Monday through Friday. Problems are to be reported on a "F2002 Build Acceptance Form" to the Help Desk by Aug 9 at 5:00 p.m.
Aug 9 All "F2002 Build Acceptance Forms" due by 5 p.m.
Aug 11-15 Final build created, incorporating fixes to reported problems; internal IT testing.
Aug 17 Final Build completed, 5 p.m.
Aug 19-23 Installation of F2002 Build into Student Technology Centers and Computer Classrooms.
Aug 24 Fall classes begin.

Note:

The build will be frozen August 9 at 5:00 p.m. No changes other than fixes to problems can be made after this date. The next opportunity for new software installation will be for the Spring 2003 semester. Please carefully test the functionality of any software you intend to use in the labs once the build has been opened up for testing. Even changing a setting on a piece of software across the campus is a "big deal" if it means re-ghosting all the labs. Let's find the problems BEFORE they get installed in the labs.

Thank you for you help in creating a "clean" build.

Your Computer Committee