Warning for all Windows Embedded Devices
Before using a device for extracting its image and use it for cloning be sure:
To enable the write filter on the device (see Using the Write Filter). Otherwise, the image conducts to failure and problems when use to restore new devices.
The device is not joined to a domain (because it could receive policies that could affect its behavior). Otherwise, when applying this image to other devices, these could join the domain.
Cloning and model devices
Note that the clone operation can be executed only on a device with the same hardware model of the device from where the image was taken.Only the factory images downloaded from MyPraim can be applied to different hardware models.
¶ Using the ThinMan Server
¶ Prepare the image
¶ Factory Image
In order to restore a thin client as it were out-of-the-box, download the Factory Firmware Image from MyPraim(see image below). Then, on the ThinMan server, upload the image file on the Package Repository
¶ Captured Image
If you want to capture an image and be applied exclusively on the device from where it was captured, use the Capture Device Backup Image command.
If you want to apply the device image on other devices, use the Capture Device Image command.
Remember that the captured image can only be applied to devices with the same hardware model.
¶ Apply the image
Use the Apply Device Image command to apply either the image obtained through the Capture Device Image or the Factory Firmware Image.
Use the Apply Device Backup Image command to apply the image obtained through the Capture Device Backup Image.
This operation can be executed simultaneously using the multiple device selection in the Console. It is also possible to automatize this operation by using an scheduled activity or an Event Activity
¶ Using the Praim Toolkit
Read How to create a USB Key and Cloning a Windows Enbedded Device Using a USB key.
When ready, the USB Key inserted in the thin client will rewrite down the entire DOM (Disk on Module) with a new firmware.
¶ General Notes
Microsoft Activation issues
When a device is restored using a clone image, it executes a Sysprep command to recreate it as a new device. The Microsoft License is preserved and reassigned but the new device has to be Activated. To do that, after the new device is restored, let it contact the Microsoft servers on the Internet. This will Activate the new operating systems and will not display the annoying messages on the lower right part of the desktop. Having the message displayed will not influence the features of the device.
Praim License issues
Before starting the cloning process, make sure the device has been correctly configured to contact the ThinMan server. Whether the image is corrupted, the device will get the license from ThinMan; otherwise, it will be necessary to provide the correct license on the thin client (download the .csv file from MyPraim, section: Products - Devices).
All these operations (backup, restore and cloning) will involve a lot of data. The DOM (Disk on Module) mounted on the device may vary from 16 GB to 64 GB of data. Fortunately, this operation will transfer only the effective amount of data used by the operating system and the installed software. Even so, the operation could require a lot of minutes to finish.
Depending on these factors you may decide:
- To prepare and configure a single thin client and then copy all its DOM to others thin clients; or
- To prepare a single installation file and then install it into other thin clients using the ThinMan functionaly Third party software installation. It depends on many parameters like network speed, the possibility of physical access to the thin client, the number of devices to update, the complexity of the installation files and so on.
Cloning the device does not clone the Write Filter Exceptions
When a device is restored using a clone image it executes a Sysprep command to recreate it as a new device. This operation will not preserve the write filter exceptions that are created by the user. Be sure to define your write filter exception again on the new device after restoring it using a clone image.
¶ How long does it take to prepare a thin client using the ThinMan Server?
The time necessary to complete the Capture Image and Apply Image will vary depending on many factors like network speed, amount of devices that are concurrently executing the same operation, real occupation on the DoM (Disk on Module) and so on.
In a controlled environment with Giga LAN, 1 device executing the operation, standard Windows 10 IoT firmware image (model M9321, 26.6GB wim image) the measured time are:
- 35 minutes for the Capture Device Image
- 28 minutes for the Apply Device Image