Get The Scoop On What's New
Want to know what Plugins4Automate is doing for ConnectWise Automate? Come check out our blog and find out about new products and updates that we are working on! https://www.plugins4labtech.com/blogs/blog

windowsupdate field is 01/01/1901

Support and question forum for Patch Remedy WUA plugin for LabTech
Post Reply
raybonesny
Posts: 1
Joined: Fri Feb 15, 2019 2:16 pm

windowsupdate field is 01/01/1901

Post by raybonesny » Tue Mar 05, 2019 6:59 pm

Hello, I have been having trouble with the computers.windowsupdate field showing 01/01/1901 01:01:01 after Patch Remedy runs. I contacted ConnectWise support who told me to write a script to attach to the monitor to autofix it. This is fine and good but the process of Patch Remedy running, windowsupdate field changing, and my autofix fixing the field, is essentially running in perpetuity. We have about 4000 agents. Any suggestions would be greatly appreciated.

User avatar
Cubert
Posts: 1286
Joined: Tue Dec 29, 2015 7:57 pm
Contact:

Re: windowsupdate field is 01/01/1901

Post by Cubert » Thu Mar 07, 2019 7:17 pm

Turn off the clear pushed button in patch remedy and that should stop.

Moza
Posts: 7
Joined: Wed Aug 14, 2019 11:42 am

Re: windowsupdate field is 01/01/1901

Post by Moza » Wed Aug 14, 2019 9:20 pm

Hi Cubert,

I have the same issue which creates hundreds of these tickets a week.

UPDATES - Out of Date:175 - *computername* 689 01/01/1901 01:01:01

What will we lose by turning off the clear pushed button?

How long should it take to fix this issue after turning it off?

I turned it off 10 hours ago but still receive the tickets.

Thanks,

User avatar
Cubert
Posts: 1286
Joined: Tue Dec 29, 2015 7:57 pm
Contact:

Re: windowsupdate field is 01/01/1901

Post by Cubert » Thu Aug 15, 2019 12:20 pm

When you turn this off, it stops changing the values in the database to 0 at the time you turn it off.

All agents already set to 0 may need to reprocess updates before this flag is changed by the agent. This could vary depending on your patch cycles.

But as for any changes from plugin, they stop at the point of setting change.

Moza
Posts: 7
Joined: Wed Aug 14, 2019 11:42 am

Re: windowsupdate field is 01/01/1901

Post by Moza » Thu Aug 15, 2019 1:21 pm

Thanks Cubert,

What will we lose by turning off the clear pushed button?

User avatar
Cubert
Posts: 1286
Joined: Tue Dec 29, 2015 7:57 pm
Contact:

Re: windowsupdate field is 01/01/1901

Post by Cubert » Mon Aug 19, 2019 12:58 pm

Clear pushed is a falg used by Automate to determine if a patch was pushed to agent. If so it would not reattempt the install . By clearing this flag it forced Automate to reattempt a update.

Moza
Posts: 7
Joined: Wed Aug 14, 2019 11:42 am

Re: windowsupdate field is 01/01/1901

Post by Moza » Mon Aug 19, 2019 7:45 pm

Thanks Cubert,

I have had this off for a while now and I still seem to be getting the same issue.

UPDATES - Out of Date:175 - LAPTOP-NAME 01/01/1901 01:01:01

Have other people had success or is there anything I am missing?

Thanks,

Moza
Posts: 7
Joined: Wed Aug 14, 2019 11:42 am

Re: windowsupdate field is 01/01/1901

Post by Moza » Mon Sep 02, 2019 6:32 pm

Hi Cubert,

This is still creating hundreds of tickets a week, if not more.

Anything else I can try?

Thanks,

User avatar
Cubert
Posts: 1286
Joined: Tue Dec 29, 2015 7:57 pm
Contact:

Re: windowsupdate field is 01/01/1901

Post by Cubert » Thu Sep 05, 2019 1:52 pm

Keep in mind that patch remedy only updates its own tables and data and does not change or update data fields anywhere else in Automate.

So... If your seeing data inside Patch Remedy that is off then that maybe us. If your seeing data outside Patch Remedy then this is not us doing that at all... We do not update or change any Automate controlled data. This includes any data in the Patch Manager for Automate.

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests