Home » DA » Scripting Win10 Image

My background is more on server technologies and hence inbox tools like PowerShell is more natural than using tools like MDT. For the script to prepare windows 10 image, here are my key objectives

  • It has to be smaller
    • install.esd instead of install.wim
    • ESD file of 64-bit windows 10, with May CU comes to 2.53 GB as compared to 3.18GB of default WIM of TH2.
  • It has to incorporate latest cumulative update
    • Component Clean-up with Base reset to ensure image size is optimal
  • Direct Access (DA) settings to be part of the installation so that if the system is outside corporate network it can still activated through KMS
    • On a DA configured system Windows, WindowsNT and WindowsFirewall hives under HKLM\SOFTWARE\Policies are exported and kept on the image to be applied post OS installation.
    • Root CA of internal PKI infra included as otherwise systems upgraded inside corporate network would not trust DA NLS server certificate and result in “Outside corporate network”. That would prevent them to access corporate resources except the ones part of DA exclusion list
    • SetupComplete.cmd to get these files and certificate installed through script on an un-customized OS image.
  • Prepare the ZIP file of the image apart from ISO file, windows 7 doesn’t have native capability to mount ISO file

Content of the SetupComplete.cmd script

 

2 thoughts on “Scripting Win10 Image

  1. Jeevan Bisht says:

    This is a great article to read, i was not even aware of this until i read this.

    1. Prasanta Kumar Panda says:

      Glad to hear a comment like this from an expert like you Jeevan, certainly encouraging

Leave a Reply

Your email address will not be published. Required fields are marked *

*
*