Skip to main content

Windows Image

As dissussed here, all computers are configured with a base image to keep updates and available software consistent across the board. The base software included and process for imaging is outlined below, however this list can quickly become out of date, so ask around on Slack if you have any specific questions.

Software​

High level Process​

The following process is subject to change (and very likely will in the near future), so keeping things general.

  1. Create base image in a VM

    • Currently, Carson has the base image in a VMware Workstation VM with incremental snapshots as software is installed and updates are applied
    • The base image should be as generic as possible, meaning:
      • Do not activate Windows
      • Set the hostname to something like SC2-WIN-00
      • Do not configure network settings or install VM tools
    • The VM's disk size should be 100GB or less to ensure image will fit on most laptops/desktops

  2. Capture VM image with Clonezilla

    • Capture the entire virtual disk (not just select partitions)
    • Store image on external drive or network Storage

  3. Boot target machine to UEFI. Ensure the following settings/features are enabled:

    • TPM 2.0
    • Secure Boot
    • Virtualization
    • Hyperthreading

  4. Boot target machine to Clonezilla and overwrite the drive with the previously captured image. Again, this should be taking the image of a device and writing it to the local device - not just single partitions.

  5. After imaging is finished, boot target machine to GParted Live, Hiren's BootCD, or similar to re-partition the target disk

    • Move the recovery partition to the end of the drive. This should leave unallocated space between the main Windows (C) partition and the recovery partition.
    • Expand the Windows (C) partition to fill the unallocated space.

  6. Boot to Windows. The system should activate on it's own with the key stored in UEFI and after some initial loading, should boot normally.

  7. Install Windows Updates. This may attempt to install drivers but many will likely fail. Necessary model-specific drivers are stored in the "SC2: Technology" shared drive.

  8. Done!