none
CUSTOM WINDOWS 10 ISO RRS feed

  • Întrebare

  • Hello there,

    I have been having challenges of building Windows 10 Images with the latest updates with pre-installed software.

    Hence I would like your assistance on how to have the windows 10 images with pre-installed software, updates, drivers etc 

    Am having Over 100 desktops to build for a Particular project and I would love to just have one master image deployed on to all of them instead of doing individual PC software installations.

    Have tried using WinPE, and DISM to capture images, but am getting huge wim files of over 22Gb. Any other possible alternative?

     Thanks.

    luni, 22 iulie 2019 14:25

Toate mesajele

  • Hi Rayson,

    If you have a WDS server or another operating system deployment tool (like SCCM/MDT), you can prepare a reference image and configure a task sequence to install remotely the desired applications and make also some configuration if you want.

    I don't think if there are another alternative to deploy PC with a prepared image included all drivers and applications with a small size.

    Regards,

    SAAD Youssef

    ______

    Please remember to mark the replies as answer if they help, thank you!

    luni, 22 iulie 2019 14:34
  • There is Windows System Image Manager (SIM) from the ADK that can be used to customize the Windows Installer, but for mass deployment on a network, MDT is a smart way to go.

    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com

    luni, 22 iulie 2019 18:14
  • Do not inlude the software inside of the image. Deploy the software after OS imaging.
    luni, 22 iulie 2019 19:20
  • Hi,

     

    Here is an official article help you to understand the different ways that it can be deployed.

     

    Windows 10 deployment scenarios

     

    In addition, this guide demonstrates how to create customized Windows 10 images that system builders can use to deploy to a line of devices, complete with customizations like apps, drivers, languages, and settings.

     

    https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/system-builder-deployment-of-windows-10-for-desktop-editions

     

    Hope these can help you.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    marți, 23 iulie 2019 02:49
  • Hi,

     

    Was your issue solved?

     

    If the reply helped you, please remember to mark it as an answer.

     

    If no, please reply and tell us the current situation in order to provide further help.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    joi, 25 iulie 2019 07:26
  • Am having Over 100 desktops to build for a Particular project and I would love to just have one master image deployed on to all of them instead of doing individual PC software installations.

    Have tried using WinPE, and DISM to capture images, but am getting huge wim files of over 22Gb. Any other possible alternative?

    Are you using the compression options with DISM? This may help reduce image size and time to apply. /Compress:Fast is usually the best trade-off.

    Another useful trick is doing a component cleanup before taking the image. This can be done using:

    dism /image:C:\ /Cleanup-Image /StartComponentCleanup /ResetBase

    You may also have to specify a ScratchDir location with /ScratchDir. NB, this can take a while, and is best done while booted into PE, rather than from within the running copy of windows.

    On the general question of whether to include software in the image or not, it depends on what you're trying to achieve and what you're most concerned about. We include some core software such as Office in our base image because every PC gets it and it saves time to have it already present in the image. That's because although we can distribute software during post-imaging, this takes longer and we care more about minimising the time taken to go from bare-metal to fully installed and usable with all software present and up to date.

    Keeping the base image to just Windows itself will give you a smaller image and it will be faster to apply, but if the resulting PC then spends ages downloading and installing various packages based on policies or other forced actions that apply to it, it's not actually usable (by someone who needs that software) until that process completes, and it may take a lot longer than it would have done to just apply a larger image in the first place with software included.

    It also means you can guarantee that the software is present and usable before the user is able to log in.

    One factor that pulls in the other direction is software that changes version frequently. For something like Office, we stick to a version for some number of academic years, so it's fairly stable. Software that has frequent releases (e.g. Firefox) is less suitable for inclusion.

    For reference, our Win10 Enterprise 1809 images, including Office and some other core software, comes out to around 10GB using fast compression.

    joi, 25 iulie 2019 12:16