Testing a Windows image

When creating a Windows image, you may want to experiment with it by installing different apps, using different settings, configuring Sysprep, etc. To keep the original image intact (so you can start from scratch if needed), you can use the exported archive as a backup. Here's a typical scenario:

1. Create a clean Windows image and export it to a file. This becomes your original backup copy.
2. Run the original image and configure Windows as desired.
3. To try a different configuration, export the modified image to a file using a different filename, rename the image in Chrome OS (or delete it), and then import the first image (the original backup) back into Chrome OS. See below for the syntax of the import command.
4. Work on the image and export again when done making the changes.
5. Repeat as many times as necessary. As a result, you should have an exported image archive for every configuration you have tried. You can import an image back into Chrome OS at any time, so you can continue working on it.

The import command has the following syntax:

vmc import -p <vm-name> <file-name>

where:

• vm-name is the target Windows image name. To be able to run the image in Chrome OS with full functionality, it must be named PvmDefault. If PvmDefault already exists in Chrome OS, rename it using the adjust command or delete it using the destroy command.
• file-name is the exported archive filename.