Support Forum

Yes, the logic is, if you don't want the user to cancel the upgrade then no notice is better than some notice. In my years as Help Desk tech guy I seen some crazy actions to stop what they think was done in error. Users start jamming buttons and pulling power cables in attempts to stop some automat...

Thanks for the quick reply. So the message overall won't appear unless the cancel option is checked in the policy. Good to know. I've done quite a few upgrades, but we always coordinate with the users so they're aware and just let them run. I did one today on a test system and checked the option to ...

Should the upgrade message we set in a policy be presented to the end-user regardless of whether or not we enable the ability for them to cancel the update?

Also, is it normal for it to use all of the reboot policy prompts that we use for patching when deploying feature updates?

Sorry for the delay. I added in the two empty .iso fields and it worked. Just wanted to close the loop on this. Thanks for your help!

I've tried with both the ENT iso listed or the 32/64 bit iso's, same result either way.

Downloading the iso in question directly from the client machine takes about 3-5 minutes, give or take, but only about 30 seconds seems to pass between downloading and failure. see below: Habitat - OS Upgrade Service Information 5/4/2021 9:19:52 AM -04:00 We have completed the ISO Download Habitat -...

'The Windows 10 ISO failed to download the [%ltsvcdir%\Habitat\Windows10UG\2004.iso]. Pleas...' T: 118.0305656

getting this error/failure trying to upgade a machine.

The machine can pull the ISO directly using the URL in the policy setup and above folder structure is there.

I'm getting the above error when trying to push Windows 10 feature updates to some systems. Last night, I pushed feature updates to three systems. All three received the .ISO (via web URL, though I have since tried both methods with the same error) and the update started on all three. One of the sys...