locked
Custom ISOs with integrated updates RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi folks!

    I managed to add the June Cumulative (Rollup) update to a Windows Server 2012R2 ISO with

    dism /Add-Package

    This apparently worked since, in an installed System,

    dism /Get-Packages

    lists that update. However, when I run Windows Update now, still over 1G of updates are fetched and installed, and the one already integrated is listed as "superseded". How can I make the integrated update be *really* installed?

    Tuesday, July 21, 2020 6:13 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    The most effective way is to create a sysprep image.  Built a 2012 R2 image, configure it to how you want it, apply all the patches you want, and then create a sysprep image.  Then distribute the bootable image.  Much faster as then installing a new 2012 R2 image just has to run through the mini-setup instead of the whole installation process.

    tim

    Tuesday, July 21, 2020 1:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you so much for answering!

    Won't there be problems with the system's SID? I've tried something similar (as far as I understand you) using VMware templates instanciation with SID regeneration, which almost broke everything. How does Sysprep deal with that?

    Tuesday, July 21, 2020 2:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No problem, sysprep(generalize) is just used for removing computer-specific information such as installed drivers and the computer security identifier (SID).

    Steps:

    1.Install Windows Server 2012 in a test machine.

    2. Customize the operating system as required. Install all you need KB packages

    3.Open CMD as administrator

    4. Change the working directory to System32 by typing cd c:\windows\system32\sysprep and pressing Enter.

    5. Type sysprep.exe /oobe /generalize /shutdown

    6. Once the computer has shutdown, boot into winpe and capture image with DISM command.

    All of above can used on VM too.

    Reference:

    https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--generalize--a-windows-installation

    Regards

    "Windows 10 Installation, Setup, and Deployment" forum will be migrating to a new home on Microsoft Q&A (Preview)!
    We invite you to post new questions in the "Windows 10 Installation, Setup, and Deployment" forum’s new home on Microsoft Q&A (Preview)!
    For more information, please refer to the sticky post.

    Wednesday, July 22, 2020 6:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    SID is properly changed when an image is sysprepped.  In fact, sysprep is the only method Microsoft supports for properly changing the SID.  Sysprep, written by Microsoft engineers who understand all items in the OS that need to be changed, runs through a mini-installation that regenerates the SID in the same manner as is done during an initial installation.  Many third parties try to develop a process that simply changes the SID in some of the places that it exists or is used.  Microsoft regenerates it properly.

    My understanding with VMware was that they used sysprep 'under the covers' for their cloning process.  I am not aware of what they do for 'SID regeneration'.  If it doesn't use sysprep, it isn't supported by Microsoft.

    tim

    Wednesday, July 22, 2020 10:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This case has been moved to https://docs.microsoft.com/en-us/answers/questions/60577/custom-isos-with-integrated-updates.html

    If you have any update, please post on the Microsoft Q&A. After August 10, 2020, all cases on TechNet can only read.

    Please mark the reply as an answer if you find it is helpful.

    Friday, August 7, 2020 7:24 AM