Hi,
I would be grateful for any insight as to what is possible when it comes to pre caching application content and waking machines client side from legacy sleep state S3.
As WOL as wake packet or fast channel is unreliable despite ports being open which is a known fact. We are currently using wake timers deployed via PowerShell.
However to reduce the amount of script runs (for multiple app installs) is there any reliable way to pre-cache application content and use wake timers together to essentially create a maintenance window without having to manually add machines to a nightly power policy?
I looked in to putting ccm.exe in to provisioning mode but the required deployments will not automatically start. I can't think of any other way outside of Modern Standby DO channel that could cater for this.
I would be grateful for any insight as to what is possible when it comes to pre caching application content and waking machines client side from legacy sleep state S3.
As WOL as wake packet or fast channel is unreliable despite ports being open which is a known fact. We are currently using wake timers deployed via PowerShell.
However to reduce the amount of script runs (for multiple app installs) is there any reliable way to pre-cache application content and use wake timers together to essentially create a maintenance window without having to manually add machines to a nightly power policy?
I looked in to putting ccm.exe in to provisioning mode but the required deployments will not automatically start. I can't think of any other way outside of Modern Standby DO channel that could cater for this.
