1 of 1 people found this helpful
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.
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?