Administrator Guide

Figure 43. Scheduling
• Maximum Simultaneous Updates: The maximum number of device updates you can perform at the same time in the subnet.
• Scheduled updates by timezone of: Select the WDM Time Zone that will be in eect when you schedule device updates. Options
include:
• DB Update Server : The time zone dened by the physical location of the WDM Database.
• Console: The time zone dened by the physical location of the WDM Console.
• Device: The time zone dened by the physical location of the device that will undergo the actual update.
• Update notice to end-users: This is the setting to bring up the User Notication Query Window on the client device whenever an
update package is scheduled for the client.
• Maximum retry attempts rescheduling failed updates: The Max. Retry Count specify the number of retries you want if package
deployment fails.
• Auto-sync Remote Repositories: Select to enable WDM (Enterprise Edition only) to determine if Remote Repositories should be
synchronized before performing an update to devices served by a Remote Repository.
Peer Assisted Deployment
Peer Assisted Deployment (PAD) is a mechanism that provides imaging updates to thin client devices that are managed through the
WDMVXC-M server. This mechanism works best in an environment where the devices are spread across multiple subnets. In peer assisted
deployment, the WDMVXC-M server chooses a set of devices that act as the repository servers for other devices within their respective
subnets. Therefore, updates are delivered from peer nodes to other devices and hence the term peer assisted deployment.
The PAD feature is applicable to the following platforms:
• SUSE Linux
• ThinLinux
• Windows Embedded Standard 2009
• Windows Embedded Standard 7 (WES7)
• Windows Embedded Standard 8 (WE8S)
• Windows 10 IoT Enterprise
The following diagram and workows best describe the working of the PAD functionality.
System
61