Administrator Guide
Workow from theWDMVXC-M Server to the Repository Device
The image update process for the repository device congured for PAD consists of three basic steps:
• Self-imaging of the device.
• Making the device Repository-capable.
• Switching o the repository when the PAD schedule is completed.
The workow can be dened in the following steps:
1 The device that rst checks in to the WDMVXC-M server, has the lowest ash size, and can accommodate the selected pad image
becomes the repository device(s) for that subnet. The device should have the values for Peer Capable and Repository Capable
properties set to True. For more information, see Prerequisites for PAD.
2 The repository device reboots and images itself from the WDMVXC-M repository.
3 The repository device completes the imaging, boots up, and downloads the BIOS and becomes Repository Capable. The device then
sends back the package completion (V02) status to the WDMVXC-M server.
4 After the schedule range elapses, the WDMVXC-M server sends an instruction to switch o the repository when the repository
device checks in. It then switches o the application responsible for enabling repository capabilities on the device.
Workow from the Repository Device to the Peer Devices
The image update process from the repository devices to the peer devices using PAD consists of the following steps:
1 WDMVXC-M schedules the imaging job to peer devices with the repository device location and image download access credentials.
2 The peer devices download the images from the repository device.
3 After imaging is complete, the peer devices boot up with the new image.
For more information on the PAD functionality see:
• Prerequisites for PAD
• Conguring PAD
• Deploying a Package Using PAD
• Viewing PAD Details
• Editing and Deleting PAD Schedules
62
System