Skip to main content
Matrix42 Self-Service Help Center

Disk Imaging

If you have already installed and configured a Windows 10 operating system as described in WindowsInstallation Package, there is now the possibility to save this complete operating system configuration via Disk Imaging with the package - DiskImageCreate - and deploy it to other computers via the package - DiskImageDeploy.

Disk Imaging with WinPE behaves analogous to Disk Imaging with EPE4. Both share the same Disk Imaging variables. See Disk Imaging - HowTo and Creating a VHD Offline - HowTo.

It is very helpful if you first configure the required PreOS packages for the respective action via Configuration > View Designer. Then you can assign them to a group simply by Drag & Drop.

clipboard_ed03bfc43a24b59af8fc2e5a765f9bba9.png

Requirements

  • Currently, the WinRE partition must be specified with a size of 0.
  • No UEM Agent or Advanced Agent must be installed on the client. If the VHD contains a running UEM agent, the PE agent cannot be started in the early Windows phase in the later deployment and the deployment cannot be completed.
  • The EmpirumServer system environment variable must be removed. If the variable is still set before the VHD is removed and the corresponding created VHD is used during deployment, the UEM agent will try to connect to the Empirum server defined in the system environment variable during its installation. This can lead to problems if a different depot is to be used during deployment.
  • Sysprep must currently be run manually.

The following PreOS Packages are required for the creation and deployment of disk images. These packages must be available in the Empirum Management Console (EMC) under Configuration > Software Management > Depot > Register Matrix42 PreOS Packages in this order:

clipboard_e5221ec81d7957653244d0938f1df5bd2.png

DiskImageCreate

The starting point is a newly installed and configured Windows 10 (1803 from August 2018 - called 1808) operating system. This may have been installed via EPE 4 or via WinPE. In versions before Windows 10 (1803) there were always problems running Sysprep (several apps had to be uninstalled first), we could not find this with version 1803 of July 2018, but with version 1809 of February 2019. The login to Windows should generally only be done with ONE user (installation user). If several users were logged in, the apps to be uninstalled must be uninstalled for each user logged in!

It is a good idea to create a snapshot of this fully configured OS, so you can start from scratch at that point. Once Microsoft Sysprep has been executed, this configuration is no longer usable!

  1. Create any configuration group according to the following example:

clipboard_ef4f5e52502854ea04e7248e65bbbf36d.png

  1. At the group or computer level, enter your preferred values in the following variables (the example contains default or demo values).
M42_INTERNAL_OS_IMAGING_CREATION.USERNAME = LAB\Test
M42_INTERNAL_OS_IMAGING_CREATION.PASSWORD = Mx42
M42_INTERNAL_OS_IMAGING_CREATION.SHARE = \\10.0.55.2\EmpInst$
M42_INTERNAL_OS_IMAGING_CREATION.SOURCE = disk:0
M42_INTERNAL_OS_IMAGING_CREATION.DESTINATION = \\10.0.55.2\EmpInst$\DiskImages\Win_10_2004-07_PRO_x64_DE_WinPE.vhd
M42_INTERNAL_OS_IMAGING_CREATION.DOSYSPREP = Yes

The software package "Empirum VHD Create" was set to Uninstall via distribution commands to prevent the package from being installed unintentionally.

  1. Activate the options "PULL via DDS/DDC (Software packages only)" and "Activate PXE (Reinstall Computer)" for the group or the computer and then start the assigned computer.

If the variable M42_INTERNAL_OS_IMAGING_CREATION.DOSYSPREP = Yes is set, the software package "Empirum VHD Create" has been changed to Install, Update via distribution commands, then the package is now executed. This prepares the activated client via Sysprep - there is no reboot.

clipboard_e510c6d578c53a2e8de2a13e1a8bd5af0.png

 

The software package "Empirum VHD Create" does currently not initiate an automatic reboot. If an automatic reboot is to take place directly after executing Sysprep, you can change the call of Sysprep.exe from "quit" to "reboot" in the Setup.inf of the software package "Empirum VHD Create" (located under: 

.\Empirum\Configurator\Packages\Matrix42\Empirum VHD Create\18.0\Install).

  1. Restart the computer.
  2. The procedure after the reboot corresponds to the Disk Imaging - VHD Offline description from point 5 in the online documentation.
    In difference to the EPE4 no WinPE ISO and from it a boot CD / DVD, or a bootable USB stick must be created here.
  3. After the reboot, the PreOS package DiskImageCreate starts the WinPE and prepares the client.

clipboard_e14734c9e50afd8207c730f3a08bff0c2.png

  1. After the client is prepared, the creation of the image starts via the package Empirum - Create VHD.

clipboard_e26ed8de2342a56516089876300368e02.png

When this process is completed, the image - in this example on the specified Empirum server - is in the directory you specified:

.\EmpInst$\DiskImages\Win_10_1809-1902_PRO_x64_DE_WinPE.vhd

This image can now be distributed to other clients - see next chapter.

DiskImageDeploy

After you have created a disc image as described in the previous chapter, you can distribute it to other computers as described below.

  1. Create any configuration group according to the following example:

clipboard_ea2080502279fd741793395b924915674.png

  1. At the group or computer level, enter your preferred values in the following variables (the example contains default or demo values).

Variables with default values - no changes necessary:

M42_INTERNAL_OS_IMAGING_SETTINGS.ADDRESS = 239.42.42.42
M42_INTERNAL_OS_IMAGING_SETTINGS.PORT = 9000
M42_INTERNAL_OS_IMAGING_SETTINGS.CLIENTTHRESHOLD = 0
M42_INTERNAL_OS_IMAGING_SETTINGS.STARTTIMEOUT = 300
GIN M42_INTERNAL_OS_IMAG_SETTINGS.JOINTIMEOUT = 180
M42_INTERNAL_OS_IMAGING_SETTINGS.TTL = 2
M42_INTERNAL_OS_IMAGING_SETTINGS.CLIENTTIMEOUT = 120
M42_INTERNAL_OS_IMAGING_SETTINGS.PACKAGESIZE = 65200
M42_INTERNAL_OS_IMAGING_SETTINGS.PAGESIZE = 1024

Variables with demo values - changes necessary:

DiskImageDiploy.LocalUserName = Admin
DiskImageDiploy.LocalUserPassword = Mx42
DiskImageDiploy.LocalUserDisplayName = Admin
DiskImageDiploy.SetupUILanguage = en-US
DiskImageDiploy.InputLocale = de-DE
DiskImageDiploy.SystemLocale = en-US
DiskImageDiploy.UILanguage = de-DE
DiskImageDiploy.UserLocale = de-DE
M42_INTERNAL_OS_IMAGING_SETTINGS.IMAGEFILE_MBR = Win_10_2004-07_ENT_x64_EN_MBR_WinPE.vhd
M42_INTERNAL_OS_IMAGING_SETTINGS.IMAGEFILE_GPT = Win_10_2004-07_PRO_x64_DE_GPT_WinPE.vhd
M42_INTERNAL_OS_IMAGING_SETTINGS.DISKIMAGING_PASSWORD = Mx42
DiskPartitioning.SizeSystemPartition = 40
DiskPartitioning.SizeDataPartition = 60
DiskPartitioning.InterpretSizeInputAsPercentage = 1
DiskPartitioning.MinimumSystemPartitionSizeInGB = 28
DiskPartitioning.SizeWinREPartitionInMB = 350
If the client was installed via WinPE, the size must be entered here when it is created - in this example this is 350.
If the client was installed via EPE4, 0 must be entered here.
DiskPartitioning.PreferFastDisk = 0
If you want to install on a NVME or SSD hard disk, enter 1.
DiskPartitioning.ClearAllDisks = 0
If all hard disks are to be completely deleted first, then enter 1 here.
DomainJoin.DomainJoinCredentialsUser = LAB\Test
DomainJoin.DomainJoinCredentialsPassword = Mx42
DriverIntegration.DriverArchiveFileName = VMware.zip
MX42_AGENT_PUSH_PACKAGE_FOLDER.Windows = UEM Agent Windows\2006.4
  1. Activate the options "PULL via DDS/DDC (Software packages only)" and "Activate PXE (Reinstall Computer)" for the group or the computer and then start the assigned computer.

When WinPE starts, the hard disk is prepared via the PreOS Package DiskPartitioning, followed by the PreOS Package DiskImageDeploy.

In this figure, using the WADK 10 (1803).

clipboard_e82030fc9764f4d020e8716f5c57aa37a.png

In this figure, using the WADK 10 (1809).

clipboard_e59b7f399718d3516e1670ea0fe517a4d.png

After the disk image has been transferred, a reboot takes place.

  1. Then the PreOS packages DriverIntegration, DomainJoin and EmpirumAgentSetup are executed.

If these packages have been successfully executed, the computer is ready for further use.

 

  • Was this article helpful?