2 Replies Latest reply on Aug 4, 2010 5:23 PM by AspenSkier

    Handling the Default User Profile and Computer Classroom/Lab Environments

    Apprentice

       

      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?

       

       

       

       

       

      Thanks,

       

       

      Dan

       

       

        • 1. Re: Handling the Default User Profile and Computer Classroom/Lab Environments
          zman Master

          We've been told by our LANDesk trainer that during the package building

          process using the Package Builder, we should never reboot

          Not sure why, we do it all the time. How else would you capture pending files?  Also, just my opinion, if you are using snapshots, I would only use them as a last resort. Use the native package installer. We have found very few packages that can't be scripted.  Not sure of your environment (number of packages per image,bandwidth, etc..) but you basically have two options - include everything in the image or user LANDesk Provisioning or schedule tasks to post install the applications after imaging.  You have to figure out what is the best.  We currently bake our core applications (apps that exist on over 95% of our machines) into our images and post install business unit applications.

          1 of 1 people found this helpful
          • 2. Re: Handling the Default User Profile and Computer Classroom/Lab Environments
            Specialist

            I work in a school environment and we have been deploying WinXP images with very similar application-specific customizations controlled by employing the DEFAULT USER PROFILE.

             

            Traditionally we have deployed NON-SYSPREP'd XP images with Ghost and our students have adopted the default user profile upon login; their experiences have been positive and consistent.

             

            Moving forward with Landesk and Win7 we are forced into SYSPREP and having to learn how to maintain our default user profiles.  We are seeing that SYSPREP blows them out and microsoft tells us to use the local admin account to rebuild them.  We found a description of this process here:

             

            The problem we see with it is that we can ONLY use the local admin account, but many of our customizations make specific use of DOMAIN resources that the local administrator can't see.
            I am trying to find a way out of this and reaching out to the community to see what folks are doing today with Win7.  I believe the OP's questions remain relevant today, does anyone have any answers?