/build/static/layout/Breadcrumb_cap_w.png

Update Existing Source Media or Add New One?

I currently have Windows 7 for my source media but I would like to keep it up-to-date for new scripted installs and updating of images.  So, I'm wondering if it's easier to add Windows 7 SP1 and relink my sysprep files to point to the new one then delete the older source media or update the existing one using another method?  I'm in a small environment so I don't mind recreating scripted installs or images.

Based on what I've read so far in the forums, I'm leaning towards uploading a new source media and deleting the old one rather than making it more complicated by trying to update the existing source media, but would like to hear from the community on this.

Thanks!


0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Posted by: dugullett 12 years ago
Red Belt
1

I upload new.

I use a VM for system images that I've taken a snapshot of right before I sysprep. When it's time to update, I power on the VM and load updates. I then sysprep, and upload to the K2.

I would also think you would want to vote on this if you do update a lot. 

http://kace.uservoice.com/forums/82717-k2000/suggestions/1759629-add-the-ability-to-change-the-install-media-for-sc


Comments:
  • Thanks, I voted - ACAST 12 years ago
Posted by: philologist 12 years ago
Red Belt
0

I would just import new source media.  If nothing else, it will have the minimum size rather than including the leftovers from upgrading.


Comments:
  • Thanks, that's what I'll do. - ACAST 12 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ