|
|||||||||||||||||||||||||
|
|||||||||||||||||||||||||
ABSTRACT
Tired of maintaining multiple Windows 2000 images, the Central Connecticut State University, User Support Services team resolved to build an XP image for all supported computer hardware platforms. The focus of this "All in One" image project was development of one image for deployment to any 3 year old or newer computer, including notebooks, regardless of hardware and drivers. This "All in One" software image is used exclusively for the Faculty and Administrative staff, and was not designed for student labs. Maintaining software images for the faculty/staff computing environment was always a challenge because of the large variety computer hardware.Technical requirements for building the Faculty image were defined as: 1) Software modifications and driver additions completed with relative ease. 2) Ease and speed of deployment for student technicians. 3) Protection of client data through out the image process.This paper outlines advantages and lessons learned thru the CCSU specific methods of imaging faculty computers since the initial XP image project two years prior. Some of the questions and issues discussed are: "How has the process evolved up to the present?", "How is the image maintained?", "Should student workers be entrusted with image modification?", and "How were technical snafu's resolved?". The building and use of an "All in One" hardware independent image has saved time and resources for the CCSU User Support Team and this paper provides the "how to" details. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
General Terms:
|
|||||||||||||||||||||||||