How to create a Windows 10 product (image)

Rate this post

Introduction

Before you begin, read this first, “How to deploy new laptop with OPSI” to understand OPSI.

In order to accomplish the link page above we will first need to create an OS image could be deployed via PXE to our clients using our OPSI server as a boot server. To do this, you must first generate a WinPE preinstallation environment for our 64-bit architecture.

Why 64 ? Because it’s the most used one and in order to do this we will use Windows ADK

Follow the installation steps in the purpose of creating a fresh image of windows 10 from scratch in my example.
 
This page can also be used in order to install windows 8.1.

Download the ADK

First of all, generate a new self-installation image need the Assessment and Deployment Kit (ADK) in the Microsoft official website for free here.

  1. Run the adksetup.exe
  2. Accept the licensing from Microsoft
  3. Let all features checked
  4. After several minutes, closed button will show up then click on it
  5. Once ADK is installed go to :
    Menu -> All programs -> Windows Kits -> Windows ADK -> Deployment environment and imaging tools
  6. A command prompt will show up in the directory : C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools
The following steps will be in the command prompt above

Define the architecture

The main difference for our end users in the choice of architecture is the level of memory supported. The x86 architecture for 32-bit systems will not see more than 4 GB of RAM installed, which means that if you have 8 GB but your computer was installed in 32 bits, it will not detect the 4 GB additional and therefore will act as if it has 4 GB (More exactly 3.3 GB).
This is why some software that only works with powerful machines can only be installed in 64 bit, otherwise the power of this one would be too small.

As mention above our example is in the purpose of a windows 10 installation with a x64 common knowm as amd64 architecture.

  • copype.cmd amd64 C:\winpe
  • dism /Mount-Wim /WimFile:C:\winpe\media\sources\boot.wim /index:1 /MountDir:C:\winpe\mount
  • echo C:\opsi\startnet.cmd > “C:\winpe\mount\Windows\System32\startnet.cmd”
  • dism /Unmount-Wim /MountDir:C:\winpe\mount /Commit

WinPE to OPSI

Before sending our result to the OPSi server we need to check it from the folder “media” in the path C:\winpe\ then we will copy all the media folder in the directory /var/lib/opsi/depot/win10-x64/winpe/.

After each change in this folder of OPSi we need to give the right access to the folder we copied :

  • opsi-setup –set-rights /var/lib/opsi/depot/win10-x64/winpe/
    A green line will appear that the rights have been given
  • ls -lA /var/lib/opsi/depot/win10-x64/winpe/

    total 1760
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:32 bg-bg
    drwxrwx--- 40 opsiconfd pcpatch    4096 Augu. 1 19:32 Boot
    -rwxrwx---  1 opsiconfd pcpatch  386976 Augu. 1  2017 bootmgr
    -rwxrwx---  1 opsiconfd pcpatch 1168736 Augu. 1  2017 bootmgr.efi
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:32 cs-cz
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:32 da-dk
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:32 de-de
    drwxrwx---  4 opsiconfd pcpatch    4096 Augu. 1 19:32 EFI
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 el-gr
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 en-gb
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 en-us
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 es-es
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 es-mx
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 et-ee
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 fi-fi
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 fr-ca
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 fr-fr
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 hr-hr
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 hu-hu
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 it-it
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 ja-jp
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 ko-kr
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 lt-lt
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 lv-lv
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 nb-no
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 nl-nl
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 pl-pl
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 pt-br
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 pt-pt
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 ro-ro
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 ru-ru
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 sk-sk
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 sl-si
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 sources
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 sr-latn-rs
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 sv-se
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 tr-tr
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 uk-ua
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 zh-cn
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 zh-hk
    drwxrwx---  2 opsiconfd pcpatch    4096 Augu. 1 19:33 zh-tw
  • Now copy the content of your Windows 10 ISO in the directory /var/lib/opsi/depot/win10-x64/installfiles/
  • Once finished we have to give the rights to this new content with the command line below :
  • opsi-setup –set-rights q
    A green line will appear that the rights have been given
  • ls -lA /var/lib/opsi/depot/win10-x64/installfiles/

    total 1712
    -rwxrwx---  1 opsiconfd pcpatch     128 Augu  1  2017 autorun.inf
    drwxrwx---  5 opsiconfd pcpatch    4096 Augu. 1 19:38 boot
    -rwxrwx---  1 opsiconfd pcpatch  395268 Augu. 1  2017 bootmgr
    -rwxrwx---  1 opsiconfd pcpatch 1152864 Augu. 1  2017 bootmgr.efi
    drwxrwx---  4 opsiconfd pcpatch    4096 Augu. 1 19:38 efi
    -rwxrwx---  1 opsiconfd pcpatch     152 Augu. 1  2017 MediaMeta.xml
    -rwxrwx---  1 opsiconfd pcpatch   80576 Augu. 1  2017 setup.exe
    drwxrwx--- 11 opsiconfd pcpatch   12288 Augu. 1 19:39 sources
    drwxrwx---  3 opsiconfd pcpatch    4096 Augu. 1 19:39 support

OPSI, WinPE, Dell

In order to have an automated deployment we have seen in previous articles the importance of being rigorous on the whole process of automation.

The choice of laptop DELL allows us to have the CAB files for the integration of our drivers but that’s not all. Back to the dell website at the page of all the drivers, we will also find a CAB file of automatize driver call WinPE.

This gives us a second way to integrate the drivers into our automated solution, you can choose the first method written in another of my articles on this website like to directly integrate your drivers in this image which will link the image to the driver.

However OPSI is well done and then allows you the integration of additional driver compared to those linked in the image we created.

Best practices

OPSI advises you not to use the winpe driver unless you have a type of post on all your park for at least 1 year.

As most IT assets in the same company are heterogeneous, it is advisable to make a file per driver pack per architecture tin order to have a better visibility in your administration process.
In addition, this will allow you to understand the driver deployment logic in the OPSI documentation easier.