We are a college with around 2000 computers in labs and classrooms. Many of the computer labs and classrooms that we maintain have a wide varation in software between them. The wide variation is due to software licensing mostly. Before our migration to LANDesk, we used Ghost Console to maintain an image of each classroom and lab configuration.
We are also in an AD environment, using Deepfreeze. With Deepfreeze, every time the computers are rebooted, their hard drives return to their original state; not a single file on the system can be altered permanately by students or faculty. We rely heavily on the Default User profile to create a clean, easy to use, computer lab and classroom environment for our students and faculty. For example, it is not acceptable to have Office 2007 configure itself for each new user that logs onto the system, and starts Word. During our old process of image creation with Ghost, we installed and configured all of the software using a temporary user on a prototype machine, and lastly we copied the profile of that temporary user to the Default User profile. We've been told by our LANDesk trainer that during the package building process using the Package Builder, we should never reboot, but a reboot is required in order to copy the profile to the Default User profile. How can we continue to handle profile specific application configurations in a lab and classroom environment using SWD? Our goal is to get way from having different images for every lab and classroom, to have only one ore two base images, and to maintain the wide differences in software between labs and classrooms completely with LANDesk's SWD. Is there anyone managing large computerized lab and classroom environments in this manner?