Requirements

  • Imaging Toolkit 11.0.9 or greater is installed and integrated with your management solutions imaging environment

  • Windows 10 business VL (Volume License) x64 ISO media and Product key


ENGL Reference Image Creation Service

ENGL Imaging Toolkit includes the ability to create a hardware agnostic Windows 10 base image that can be restored on both BIOS and UEFI machines. The base image preparation process included with Imaging Toolkit allows optional Windows updates to be applied from the cloud or WSUS. 


The optional Reference Image Creation Service allows organisations to download the latest Imaging Toolkit compatible Windows 10 base reference image (Bronze) or request a custom image (Silver) in one of the following imaging formats: Linux/ZMG, WinPE/WIM or WinPE/ZMG. All WIM images are captures using the latest version of Windows ADK/WinPE and ZMG images are captured using the latest version of ZENworks (with Tuxera driver for Linux imaging).


For further details including service features and pricing, please visit the Imaging Toolkit product page.



Procedure


  1. Reference Image Creation Service

    1. Open a new support ticket entitled "Reference Image Creation Service request"

    2. Once your service level has been confirmed, a support agent will ask you to confirm which image media version/edition and image format you would like. For customers with Silver service level, a form detailing any customisations you would like in your base reference image will need to be completed.

    3. Once the image is ready and tested, you will be sent a download link and instructions on what to name the saved file (e.g. "win10-ent-x64-19041-postsp.wim"). Save the image file to the server images\os\win10-<edition>-x64 folder.

  2. Build Console

    1. Import the Windows 10 VL x64 media 
      The imported media must be VL (Volume License) media and match the same version (e.g. 2004) and contain the same edition (e.g. Enterprise) you wish to deploy. However, the media does not have to be the latest month update (e.g. "July 2020"). The media is required to ensure you own the media you wish to deploy.
      Note: Build Console will display the Windows 10 version build number (e.g. 19041) stored in the media.

    2. Edit project settings
      Ensure the Windows version, edition and platform is selected that you wish to deploy. Customise the project with any management clients and agents as normal. Save the project with a description that identifies the Windows version, edition, platform and update (e.g. "Windows 10 Enterprise version 2004 (July 2020) x64").

    3. Deployment Wizard

      Select Build process creation, click Next, select the components image (e.g. Novell components "novcomp"), select Build process, and if available select UEFI boot image, click Next, click Next again then follow the on-screen instructions. 
      Once the wizard reaches the Finish page, select Open images folder, then click Finish. Copy the projects\<myproject> folder to the server images folder (e.g. content-repo\images for ZENworks or \\<server>\<share>\images\projects for other solutions. Also, copy the os\win10-<edition>-x64 folder to the server images folder.

    4. Integration Wizard
      Select Configure Zim, click Next, select Create project lookup file (projects.ini), click Next, select the appropriate project, click Next, select Open integration folder, click Finish. Once File Explorer opens, navigate to the tftp\zimfiles folder, and copy projects.ini to your TFTP server zimfiles folder.
      Note: Always make a backup of the server TFTP folder before updating it.

  3. Testing

    1. Boot into the imaging environment (e.g. using PXE) on a VM or physical machine - it's useful to test using a VM as there are less issues with drivers.

    2. At the Imaging Toolkit "Zim" main menu, select Restore images, then select the appropriate project and test the deployment.
      Note: When you first perform a restore of a new image, always deselect Auto Restart After Imaging. This will allow you to easily copy log files in the event you need assistance from ENGL support.

    3. If the image / deployment fails, check the zim.log to ensure the images have been located correctly. If you are unable to fix the issue, please respond to the support ticket that was used to request the image, remembering to attach the zim.cfg, zim.log and projects.ini.