You can use the WinPE image to provision a device that does not have a Mirage client installed or to provision a device that does not have an operating system installed.
About this task
The image that you create with WinPE runs on memory, not on the hard disk.
On the WinPE image you can only perform provisioning procedures and generate sysreports.
Mirage supports provisioning into legacy systems and EFI systems. In some cases, such as when the disk is not Windows ready, or when there is insufficient space on the existing volumes, Mirage might re-partition the disks. Re-partitioning creates a single partition for the whole disk that is selected by Mirage. Re-partitioning only succeeds on EFI machines if they are configured to boot in legacy mode.
If WinPE reboots during a provisioning procedure, the device reconnects and is identified as a new pending device. Previous provisioning orders on the device are not applied and you must restart the provisioning process.
When the image boots, two command prompt windows appear. One command prompt window is for troubleshooting. The other command prompt window runs Mirage in the WinPE environment.
WinPE stops running the shell and restarts after 72 hours of continuous use.
You can provision a device with Mirage by using a base layer with the following operating systems.
- Boot the device using the appropriate WinPE image.
The .wim file.
The .iso file.
- When the Mirage status window appears, note the host name of the device.
A host name is generated during each reboot.
- Provision the device using the WinPE image.
Mirage Web management
Navigate to the Mirage Web console and click the Pending Devices tab.
Select the device with the host name that you noted and click Provision Endpoint.
Mirage Management console
Navigate to the Mirage Management console and select .
Right-click the WinPE device and select Device Provisioning.
After you provision the device, the device boots with the provisioned operating system.