tvarvais

@BlueToast Care to share the script? I am about done with the Disk Cleanup process. It may be a native tool but it is a pain to work through the quirks.

We move(Retire) any agent older than 90 days then truncate the table. If the agent comes back online it will recreate it's ID. Also, as part of the process, we email the customer at the 30 and 60 day mark to let them know that the system(and the user ID that last logged into it) has not been calling into our management software. In that message we indicate to have the system online or reboot it to make sure that it is communicating properly. At the 90 day mark we send out an email and let them know that we have retired it. Since the ownership is on them to have the system online/available

Scalepad - previously known as Warranty Master: https://www.scalepad.com/

Warranty Master/ Scalepad here also.

I am not sure why you would essentially want to create a 'table' in a database from a script. I believe that most people would create the table then populate from a script. Perhaps if you explained what you are trying to accomplish so that we could have a better understanding we may have some insight on a solution.

I just checked ours and they (all of the ones that we have added) are still present. note: last week we install patch 2020.9.308 and this week we did the .310 patch. So far the only adverse effects that we have is the "LabTech Solution Center Service Monitor" will not start - which we have found out is a known issue and support is working on...

Looks pretty good. One item though "Step 2: Enable the new Group Policy (Domain controller: Allow vulnerable Netlogon secure channel connections) on the domain Controller OU " < Only needs to be done if you have a system(s) that are identified by the 5829 Event and cannot be remediated.

We created a OS Groups for each of the Windows 10 builds so that we have insight into what is out there along with better control over upgrading them. We further narrowed the search to exclude systems not under contract.

Agree with @blckpythn - If you are looking for assistance go to the Slack group - One thing that Connectwise Automate has....is an AWESOME usergroup! Just wish their tech support was better...

Taskkill should work but.....Have you tried 'Process Kill' in the Script? (After an "IF Process Exists")

(Please not that this is the WORKAROUND not the actual patch) KB4569509: Guidance for DNS Server Vulnerability CVE-2020-1350 - seems to be the talk of the net this afternoon. I wrote a quick script to check for the registry key and set it if the key is not present or set it if the key has the default value. (Microsoft's article does not clarify the type of value to create....had to verify it via another post) For those that prefer batch'n it: reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters" /v "TcpReceivePacketSize" /t REG_DWORD /d 0xFF00 /f net s

MySQL? I am just running a check but perhaps this may help you: SELECT Stage FROM computerpatchingstats WHERE ComputerId = '%computerid%' I look for a '1' to indicate Pilot. I believe 0 is test and 2 production but please verify.

this is on the systems and running a "Check for Updates" - does not show. Therefore does not show in CWA.

KB4562562 is not required for this, it is 'recommended' according to Microsoft but not required.

Has anyone else noticed that KB4561608 on Server 2019 is showing as not required? I have loaded up some fresh servers to test and it installs but am finding that existing servers in production are not showing as requiring the Security patch. Wondering if anyone else is seeing similar. Thanks