none
Installing Windows Updates, Updating Windows 7 wim files.

    Question

  • Hi All,

    I`m pretty new to Windows 7 custom images so would just like a little information if that`s possible.

    I`ve created a few custom images for Lenovo laptops and desktops (T520\T530 and M92\M93). These images contain a few installed applications like AV, Adobe, Flash, Java, Office 2010, Free PDF to name a few.

    I`m now being asked to make changes to these images, such as, stop Java and Adobe from updating automatically and install new Windows updates when they are released from the WSUS.

    Is there any harm in making these changes to an existing custom image then sysprep and re-capture? Or is there a better Microsoft application to do this? Or would you recommend installing the O/S, appliactions on a clean HDD and sysprep and capture? (Hopefully not the last).

    Any information would be appreciated.

    Thank you in advance

    Scott Evans

    Monday, October 21, 2013 4:42 PM

All replies

  • It comes down to personal preferences.  Yes, you could deploy, make the changes and recapture, or make a brand new image.

    I prefer to make a clean base image that is fully patched and then have the applicatoins run via the Task Sequnce since it should be the same program that you use in the enviroment.  This way you can make changes on the fly (Dynamically) and you don't have to keep recapturing and pushing out 5 to 9GB of WIM files.  I have a very large enviroment to the less we need to repush the better it is for the network. 


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

    Monday, October 21, 2013 7:11 PM
  • The best practice is create one gold image (base image) with OS and updates only. Then use the task sequence to deploy the base image then add all other apps to deploy through the task sequence.

    This way you have full control on what you want to give your users, if you want to stop any piece of software, you can disable it on the task sequence.

    Monday, October 21, 2013 9:55 PM
  • Thank you for the quick response regarding this.

    I also have a quite large enviroment, I`m currently installing the custom image as part of a windows 7 installation USB. I`m in the process of having all our PC`s and Laptops imaged by a company before they arrive onsite.

    I`ve created a custome image as previously explained, I have one Lenovo T530 and one M92 (Golden Image) I update this then sysprep and recapture. My only concern is, can this process cause issues to the stability of the O/S and image?

    Going forward the only changes I need to make should be windows updates when they are released by the WSUS. Is there a simpler process to add these to the image?

    Thank you

    Scott.

    Tuesday, October 22, 2013 8:50 AM
  • Not really as, long as you get rid of the GUIDs and SCCM GUIDs and other items SYSprep will clear the rest and you can update date.

    We keep our WIM clean so we basically deploy the WIM in a deploy/capture state, pause it and use Windows update to install the updates and then capture it back up. 


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

    Tuesday, October 22, 2013 1:29 PM
  • Yes I have been doing this.

    Thank you.

    Scott.

    Tuesday, October 22, 2013 1:34 PM
  • The best practice is create one gold image (base image) with OS and updates only. Then use the task sequence to deploy the base image then add all other apps to deploy through the task sequence.

    I completely disagree that this is any kind of "best" practice at all. This is simply a personal preference.

    The great thing about OSD though is that it will accommodate these personal preferences without locking you in allowing you to put whatever fits your needs and requirements into the image and statically or dynamically layering on what you need after the image but still part of the process.

    My guiding rule is that the image should contain the greatest common denominator of software in your org. Thus, if everyone gets Office, putting it in the image will save you lots of time -- this is the primary reason to put things in the image: time. Security is another one as you don't want to deploy an insecure OS image.


    Jason | http://blog.configmgrftw.com

    Wednesday, October 23, 2013 1:36 PM