Skip to main content

1E 23.7 (SaaS)


The minimum size of content (in megabytes) that will cause a request for a wakeup. See Integrating Nomad with WakeUp for more details.


Nomad integration with WakeUp enables Nomad to share content from its devices that are holding particular content, even if those devices are offline. One reason why peers in the local subnet may not respond to the request even though they have content in their caches is that they are offline (shutdown, in hibernate or sleep mode). However, if WakeUp is integrated, the Nomad client would know which offline device has the content and can wake it up when it queried Content Distribution.

The wake up list is maintained by Content Distribution and is the same list that Single Site Download (SSD) uses. Separate lists of peers are returned for subnet and site. This feature requires Nomad SSD to be enabled, Content Distribution and a NightWatchman infrastructure. The feature is enabled during installation of NightWatchman Management Center. Please refer to Nomad Preparation for requirements.

Registry value

Default value


Installer property



Any content below this size is downloaded from the DP as downloads from the DP for files this size will likely complete before any wakeups will have had a chance to finish. The value can be 0, in which case wakeups will always be attempted.

For example, if it is set to 512 and size of the content downloaded is 500 MB, a wake-up request (to site or subnet) is not be sent. Similarly, if size of the content is 600 MB, then wake-up requests (to site and subnet, determined by WakeupEnabled) is be sent.


For standalone downloads (using SMSNomad.exe) and under WinPE, there has no effect as the size of the content cannot easily be determined. Wake-up requests are always sent in these instances.