I am able to manually run upgrades for Windows 10.
I have cleared the patch remedy tables from the database and let it rebuild itself, then set everything back up.
I also removed the plugin and installed the latest from scratch.
To test functionality, I am testing upgrades on some of our internal computers.
Upgrades should have run this morning between 3 and 5 AM.
As an example, I see the following during the patch remedy script running on one of the computers BEFORE the 3 AM window. The script doesn't appear to be running at 3 AM.
The Script(7197) was successful in the Then section.
Script: S7197 - Starting at Server Time: Wednesday, October 3, 2018 1:04:01 AM
IF F5 ValueOne (P1): MYCMD Comparer (P2): 8 ValueTwo (P3): SCANWUA T: 0.8470736
L2 F235 T: 0.874077
L3 F21 Seconds (P1): 3 T: 8.156774
L4 F235 T: 11.1580764
L5 F21 Seconds (P1): 3 T: 26.0735104
L6 F235 T: 29.0748001
L7 F70 Value (P1): WUA Comparer (P2): 4 To (P3): 10.0.16299.15
Jump (P4): 1 T: 39.0787661
L8 F70 Value (P1): WUA Comparer (P2): 7 To (P3): 10.0.16299.15
Jump (P4): 1 T: 39.0797675
L10 F20 SetType(P1):1 Parameter(P2):'Microsoft Windows 10 Enterpris...' VariableName(P3):OSTYPE T: 39.0867671
L12 F20 SetType(P1):0 Parameter(P2):'HKEY_LOCAL_MACHINE\SOFTWARE\Mi...' VariableName(P3):OPTMICRO T: 39.0877226
L13 F70 Value (P1): OPTMICRO Comparer (P2): 0 To (P3): Jump (P4): :EXISTS T: 57.6865475
L16 F139 Note (P1): :EXISTS T: 57.6865475
L17 F20 SetType(P1):1 Parameter(P2):1 VariableName(P3):OPTMICRO T: 57.6865475
L18 F70 Value (P1): WUA Comparer (P2): 1 To (P3): Jump (P4): T: 57.6865475
L19 F70 Value (P1): OSTYPE Comparer (P2): 1 To (P3): Jump (P4): T: 57.6875487
L20 F70 Value (P1): WUA Comparer (P2): 2 To (P3): OK Jump (P4): T: 57.6875487
L21 F70 Value (P1): OSTYPE Comparer (P2): 2 To (P3): OK Jump (P4): T: 57.6875487
L22 F70 Value (P1): OSTYPE Comparer (P2): 8 To (P3): script failed Jump (P4): T: 57.6875487
L23 F70 Value (P1): WUA Comparer (P2): 2 To (P3): Jump (P4): T: 57.6875487
L24 F70 Value (P1): WUA Comparer (P2): 8 To (P3): script failed Jump (P4): T: 57.6875487
L25 F70 Value (P1): OSTYPE Comparer (P2): 8 To (P3): error Jump (P4): T: 57.6875487
L26 F70 Value (P1): OSTYPE Comparer (P2): 2 To (P3): Jump (P4): T: 57.6875487
L27 F70 Value (P1): VERSIONNUMBER Comparer (P2): 8 To (P3): Get-Item Jump (P4): 2 T: 57.6875487
L28 F70 Value (P1): VERSIONNUMBER Comparer (P2): 8 To (P3): error Jump (P4): 1 T: 57.6875487
L29 F20 SetType(P1):1 Parameter(P2):'Microsoft Windows 10 Enterpris...' VariableName(P3):OSTYPE T: 57.6885538
L30 F139 Note (P1): :RUNSQL T: 57.6885538
L32 F20 SetType(P1):1 Parameter(P2):'INSERT INTO plugin_sw_patch_re...' VariableName(P3):SQLCMD T: 57.6885538
L33 F29 Message (P1): 'INSERT INTO plugin_sw_patch_remedy_wua (ComputerID,ClientID,WUAVersion,OS,MicrosoftUpdates...' T: 57.6885538
L34 F67 Sql (P1): 'INSERT INTO plugin_sw_patch_remedy_wua (ComputerID,ClientID,WUAVersion,OS,MicrosoftUpdates...' T: 57.7255242
L35 F21 Seconds (P1): 5 T: 57.7265079
L36 F67 Sql (P1): 'UPDATE plugin_sw_patch_remedy_wua SET WUAVersion = REPLACE(WUAVersion, '\n', ''),OS = REP...' T: 62.7290375
L37 F172 SqlStatement (P1): 'SELECT count(*) from properties where `Name` = 'PatchRemedyFix80240025Error' and `Value` ...' T: 62.7530363
L38 F70 Value (P1): sqlresult Comparer (P2): 2 To (P3): 0 Jump (P4): 4 T: 62.7530363
L43 F20 SetType(P1):0 Parameter(P2):'HKEY_LOCAL_MACHINE\SOFTWARE\Mi...' VariableName(P3):MyKeyValue T: 62.7530363
L45 F70 Value (P1): MyKeyValue Comparer (P2): 2 To (P3): 1 Jump (P4): :UPDATEDEFERRED T: 69.9367371
L46 F139 Note (P1): :RUNUPDATEDEFERREDSQL T: 69.9367371
L47 F67 Sql (P1): 'REPLACE INTO `plugin_sw_patch_remedy_win10deferred` (ComputerID,ComputerName,ClientID,Clie...' T: 69.9367371
L48 F129 Jump (P1): T: 69.9817424
I checked the Windows10Deferred table and computer is set to false.
The logs on the LabTech server for PR don't give many clues as to what's going on during this period. Plugin_PatchRemedy.txt shows the scan requests going out around 1 AM. The error log contains no entries from this morning.
Anyone have any ideas what's going wrong?
