OSIM Images Using ImageX and Ghost32 › Steps to Create an ImageX OSIM OS Image Using an OSIM Support OS Image › (Optional) Backup your model PC (Step 3)

(Optional) Backup your model PC (Step 3)

The process of prepare (sysprep Step4) modifies the OS installation on the model computer such that it cannot reboot into the operating system anymore. You can back up the model computer so that you can restore the same and boot into the operating system after you have captured the image.

To backup an image, you must run an OSIM backup job that captures the OS image using the specified imaging tool.

To create OSIM install jobs to back up an image:

1. Create an OS installation job for the model computer in DSM Explorer.
2. Set the value of following OS installation parameters:

1. Activate the job (use Wake-On-LAN for automatic boot).

   The following events occur:

   • The model computer boots WinPE20 again and executes the getimage.cmd script from the camenu share.
   • The getimage.cmd command shares the getimage-11 or getimage-wepos-11 share, depending on the OS type you selected. The images subdirectory is prepared to hold all images. The getimage.cmd command looks for a subdirectory with the name of the model computer under the images folder. If the subdirectory does not exists, getimage.cmd creates the directory. All images from a model computer are stored in the subdirectory with the model computer name.
   • Further on, getimage.cmd looks for a subdirectory with the name of the image ($ImageXImage$) under the model computer subdirectory. If this directory exists, it extents the name to $ImageXImage$n (n=1-5) and tries to create a new subdirectory again. If the directory creation is successful, getimage.cmd stores the new image in the subdirectory.

     Note: The success of directory creation depends on the BackupPolicy that you have set. If the BackupPolicy is set to write images and wrap around, getimage.cmd overwrites the oldest image when the defined number of images already exists. If the BackupPolicy is set to write images and not wrap around, getimage.cmd aborts with an error message that the directory name already exists.

   • getimage.cmd copies the ImageX client to the new image directory, executes ImageX to capture c: partition of the model computer, and stores the images as a .wim file in the following path:

     \\<OSIM-image store>\<imagename>\<imagename>\images\<computername>\
     

     <$ImageXImage$n>\<$ImageXImage$n>.wim
     

   The following screenshot shows the location of the new image:

   Note: If the C: partition does not exist on the model computer, the getimage.cmd command terminates after writing to the error to the log file.

   For Ghost32, the directory contains the ghost.exe file and the file <$imageXImage$>.gho will be created by getimage.cmd.

2. Finally the model computer shuts down and the OSIM job status in DSM Explorer is set to Stop.