View - Imaging (Windows)
- View - Imaging Overview
- Imaging Association Deletion, Enable and Disable
- Imaging Association Properties
- Create Imaging Association
View - Imaging Overview
What
The Imaging View shows us information for Windows imaging related associations, and allows us to create new.
When/Why
We are going to use this view whenever we want to check that a device has an imaging assignment, if we want to assign an image to a device for future imaging purposes, or if we want to change current association settings.
How
Creating, deleting and editing associations are available in this view and are covered further in the articles linked below. Having an image associated is the only way the IVS (Imaging appliance) knows what Windows image to assign to a device.
Imaging Association Deletion, Enable and Disable
What
Previously created image associations can have three actions taken on them, depending on their current state. They can be deleted, enabled or disabled.
When/Why
Deletion is always the same...it removes the association between an image and a device. We'll use this when we no longer want the association (it removes the potential for accidental imaging). Enable/Disable toggles the association between being enabled or disabled. This toggle is used primarily to avoid re-imaging a device that was just imaged and is toggled automatically by the IVS during imaging. It can be changed manually as well though...usually for re-enabling.
How
With one or more devices selected in the view, you can delete, or enable/disable from the bottom bar prompt:
Imaging Association Properties
What
Image Associations are how we assign a captured Windows Image to a device for re-imaging. Every association has three basic properties: the image, driver packs (if used), and what devices are assigned.
When/Why
We will edit the properties when we initially create an association, and whenever we edit one.
How
The image selected is limited by the images that have been previously created (creation can only be done in FileWave Central), but most organizations have one image per Windows version, and per bios type (MBR or UEFI), depending on devices.
Driver packs don’t always have to be used, but best practice would be to do so. In practice that means that you would have an imaging association for every combo of image/device type. The below example shows assignment of a driver pack for a specific device type.
Multiple devices can be assigned in one association addition so that you don’t have to repeat the process individually…conceptually you’ll see these are handled very much like Deployments, although after creation they are stored as individual associations.
Create Imaging Association
What
By clicking the 
button in the upper right-hand corner of the imaging association view, we can create a new association.
When/Why
We'll create a new association every time we want to assign an image/driver pack to a device that doesn’t have one. Each device can have one and only one imaging association.
How
We'll choose the image to use from the "Choose Image" button shown above, the driver pack (optional) in the center, and the device(s) at the bottom. The process is shown in brief below:
Note: If you add an association for a device that already has one, you will be prompted for overwite/cancel as follows:
