Windows 10 Scheduled update did not run

[fsquires]

I've tried scheduling the Windows 10 update a few times and it doesn't launch. I can push the update manually and it works fine.
My last attempt was last night (Thursday August 16th at 1 AM). There are some log lines around 1 AM but I'm not sure if they're related to the schedule. I have plugin version 1.0.4.33.

Thanks for the help!

Here are are the lines from the log around the time when it should've launched:

LTAgent v110.441 - 8/16/2018 12:26:15 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy thread still running:::
LTAgent v110.441 - 8/16/2018 12:34:09 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy Pre maintenance reboot disabled:::
LTAgent v110.441 - 8/16/2018 12:34:09 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy thread still running:::
LTAgent v110.441 - 8/16/2018 12:48:40 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy Pre maintenance reboot disabled:::
LTAgent v110.441 - 8/16/2018 12:48:40 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy thread still running:::
LTAgent v110.441 - 8/16/2018 1:01:18 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy Pre maintenance reboot disabled:::
LTAgent v110.441 - 8/16/2018 1:01:18 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy thread still running:::
LTAgent v110.441 - 8/16/2018 1:09:58 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy Pre maintenance reboot disabled:::
LTAgent v110.441 - 8/16/2018 1:09:58 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy thread still running:::
LTAgent v110.441 - 8/16/2018 1:11:40 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy Maintenance ISync Failed Hotfixes Checks Executed on (2365) Systems:::
LTAgent v110.441 - 8/16/2018 1:11:40 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy Maintenance Completed:::
LTAgent v110.441 - 8/16/2018 1:18:36 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy Pre maintenance reboot disabled:::
LTAgent v110.441 - 8/16/2018 1:23:37 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy ISync - Current Version is (1.0.4.33) and the available version is (1.0.4.33):::
LTAgent v110.441 - 8/16/2018 1:23:37 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy ISync -Version is current:::
LTAgent v110.441 - 8/16/2018 1:23:37 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy ISync auto upgrade completed:::
LTAgent v110.441 - 8/16/2018 1:28:47 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy Pre maintenance reboot disabled:::
LTAgent v110.441 - 8/16/2018 1:42:48 AM - Plugin PatchRemedy, Version=1.0.4.33, Culture=neutral, PublicKeyToken=null: Patch Remedy Pre maintenance reboot disabled:::

[fsquires]

Any thoughts on this?

[Cubert]

Did your patch remedy update to 1.0.4.34 yet?

[jmaxwell]

We are having the same issue. It may be same thing as in viewtopic.php?f=7&t=5488
We again showed that the upgrades did not push. We are on 1.0.4.34. There were no scripts that ran. Nor logs with in that time frame. If you need additional information let me know.

prupgradelogerror2.PNG (3.12 KiB) Viewed 11263 times

prupgradelogerror1.PNG (6.89 KiB) Viewed 11263 times

prerror1.PNG (974 Bytes) Viewed 11263 times

Also, we initially created the iso before 1803 came out. Do we need to create updated iso for each new version?

[Cubert]

We need to update the text on the log as that is inaccurate. It will launch on the next update schedule set.

As for upgrading from one build to the next, absolutely! Everytime MS releases a new OS version a new ISO will need to be made with the media creation tool and uploaded to your storage area for agents to retrieve.

[jmaxwell]

So our issue of it not starting would stem from not the newest version iso? Or is it a different issue?

[Cubert]

I would make ISO with version numbers attached like

Windows10Pro-1809.iso so you know what versions of Windows is at every ISO. Then yesy if you had 1709 and now want 1803 you will need to replace the 1709 ISO with the 1803 build and update the version number to update to.

[jmaxwell]

We updated the iso to newest version. We are trying the URL instead of the LTShare. We tried to push an automated scheduled upgrade with the url ISO on a few machines. Again it did not push. The upgrade log message did not change, no scripts ran at the time scheduled, no logs in plugin-Patchremedy.txt for the time frame. Not sure if I setup the URL scenario incorrectly? I know the URL scenario disables the LTShare. But what is the process after setting the URL? Do we still need network share in location?? Does it download the full iso to each machine? If so where does it download to?
We are on 1.0.4.34

Inkedprupgradelogerror3.jpg (885.27 KiB) Viewed 11247 times

prupgradelogerror4.PNG (10.72 KiB) Viewed 11247 times

[Cubert]

No plugin logs on LT server?

There should be something in the logs. A run, a failure or a busy log at least every hour at the top of the hour. If you have no logs at all then something is a miss and not letting service run as it should.

Might need a LT host reboot?

[jmaxwell]

These logs?

logs.PNG (6.75 KiB) Viewed 11243 times