Jump to content

Search the Community

Showing results for tags 'patching'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • MSPGeek
    • The Geek Cast
    • Code of Conduct
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development


  • ConnectWise Automate
    • Scripts
    • Plugins
    • SQL Snippets
    • Role Definitions
    • Automate PowerShell Code
    • Reports
    • Internal Monitors
    • Remote Monitors
  • ConnectWise Manage
    • API Interacting Code


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me


Agent Count













Found 20 results

  1. THE PROBLEM: Windows Update stops reporting the monthly security Cumulative Update and instead only reports the Feature Update to the latest OS release. Automate relies on Windows Update to report that there are available security updates, so it treats it as "Everything is great, no missing updates!" when in fact the system is missing potentially critical Cumulative Updates. I used PSWindowsUpdate to test and confirm the behavior on a number of computers. As of yet, I have not found a way to get around this wonderful "feature" (presumably it works differently if you are using Enterprise o
  2. I decided we were going to update our patch policies to have a dropdown with all 24 hours available for patching, with a set patching window of 4 hours. I wanted to have every day available to select, as well as the end of the quarter. I also wanted to be able to toggle daytime patching with an EDF. Some quick math tells us that this would be 8*24*2 groups, or 384 groups, and 384 searches for your EDFs. This would be extremely tedious, and would absolutely cripple any automate database. I also have EDFs at the computer and location level, and allow
  3. Hi guys, First time poster and hit a bit of a snag, Automate support haven't been very helpful so I'm hoping you will come though. Our clients require their workstations to be patched every 2nd tuesday or 3rd wednesday of the month. Set days like the 1st/18th don't work for them as this could potentially land on a weekend. We have sent manual emails before now to alert them but we would like to automate this. From what I can see I can schedule scripts to send automated emails on a set date but nothing that will allow for the 2nd tuesday etc. I'm just wondering if anybody has bee
  4. Hello All, I came across an oddity. When I go to a client site and run a Service list data summary across all servers for the service name wuauserv, I find the report comes back with the service state stopped. If i right click on any device and start the service and then go to the command status page i can see it execute and then finish as success. Now if i pick the same server and install a Microsoft patch on it, and then log into the same server about 20 minutes later and check the installed patches, nothing shows for that KB as installed. If i check the same systems local services i can see
  5. Hi Geeks I wonder if any of you have been using Appget with Automate? It is an open source package manager for Windows. It is also an open source project on Github. It can install and update 800+ apps. I tried it on one of our PCs: References: https://appget.net/ https://github.com/appget/appget
  6. Is anyone using Patch Manager to patch large client sites based on groups set by autojoin searches based on OU? I was thinking of setting up a script to populate an EDF that contained the workstations default OU, then creating an autojoin search based on that EDF. Am I trying to reinvent the wheel or is there a better way to break up 1000+ agent sites by groups for patching?
  7. We were having trouble managing workstations, especially laptops, because they were going offline overnight. This monitor/autofix setup has drastically improved the situation. Components: Install and Apply Power Plan [function script] This creates and runs a powershell script to download a .pow file, install the power plan, and apply it. This assumes that @powerplanFileSource@ has been defined and points to a .pow file in the LTShare transfer folder. So if your powerplan file is \LTShare\Transfers\PowerPlans\nosleep.pow, you will have defined powerPlanFileSource =
  8. Summary: I think the Automate Patch Manager's stock Daytime Patching (DTP) functions give up way too easily. So I wrote a RAWSQL monitor that you can use to drive patch delivery scripts during the day to systems missing patches. The monitor is built to use stock Patch Manager features relating to Microsoft Update Policies, so it should be pretty universal. The configured criteria as written: System is online Windows OS No servers No reboot pending Has an effective Microsoft Update Policy that has Daytime Patching enabled Has more than 0 missing updates
  9. Hi All, After speaking with ConnectWise, I understand there is a script from the Solution Centre called 'Windows 10 - Install Feature Update' which requires you to deploy the latest build of Windows 10 to your LTShare, but that it's only a supported feature on-prem and cloud partners currently don't have support for this.. https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Knowledge_Base_Articles/Scripting%3A_Windows_10_Install_Feature_Update_Script As a potential workaround, ConnectWise have told me I can individually place the ISO und
  10. Does anyone have a solution to notifying clients of what patches will be installed automatically? We have a client that is asking that we notify them in advance of any and all patches that are to be installed on their systems and we are looking for an automatic way of doing that to ensure we are in compliance of their needs.
  11. I just spoke with Automate support since one of our servers was showing a last patched date of 6/20/2019 by Automate but we found that it had not actually been patched since November 2018. With that said, I found from Automate support that the "last patched" date includes third party patching as well. So, this server was patched by a third party patch on 6/20/2019 but Windows updates had not been installed since November 2018. I asked them if they had a better monitor to best track the agents that have not had a Windows update installed in the last 30 days but they said there wasn't one. T
  12. Hi there, We seem to be having a lot of problems patching in Server 2016 - is anyone else here having difficulties? A lot of our Server 2016 servers (but not all) seem to be having updates done by UpdateOrchestrator’ & not by ‘CM Automate’ (see attached screenshot) All the patch settings in Ignite seem to be the same between the Servers that are ok, and the ones that are not, and they are all in the same Patching group, so we are at a bit of a loss to understand why some are not being patched by Labtech & some are. Does anyone know where I can look further to see w
  13. Hi all, I am looking for a way to set up a group that will allow any computer added to it to continue patching all day long as long as it has outstanding patches. I envision being able to add new computers to this group and have them run MS patching until completely updated. Currently, I set up a group and assigned the following MS Update Policy to it: Day: Custom Start Time: 12AM Duration: 23 Hours Selected all days, of every month. I then assigned the follow reboot policy: Disable reboot window, issue reboot when patching is complete. Reboot based on
  14. I am looking to run/schedule a Patch Compliance Report. I can run this against the client only. This gives me all the workstations and servers. Since we have our servers in a different location would it be possible to run this report with the client and location thus giving me the report for just the servers? If there is a different report I need to be running please let me know that as well. What I would like to see is How Compliance is my servers. Last Patch Date and all patches approved and ready to install. Thank you! Rob
  15. We've recently ran into an issue with cumulative updates on Windows 10 machines causing the machines to bsd. Is there a way to have the cumulative updates install separately over the weekend?
  16. Geeks, Patching your Patch Engine, Microsoft’s Windows Update Agent (WUA) is an agent program that works in conjunction with Windows Server Update Services to support automated patch delivery and installation. Labtech uses this agent to help determine what patches are needed by each Windows system and deploys them. Microsoft often updates the WUA which increases the detection of missing patches more current then the installed version of WUA. This can cause you to get a perception that your patching is up to date when in actuality your massively behind. There is mor
  17. I have a simple script that will install all missing approved patches. If missing approved patches are found it will install them and create a ticket in CW. Is there a way to get the output of the Install Patch command into the ticket as well to show what was installed or if there was an error? Thanks!
  18. Hello all, A few weeks ago, I inherited the LabTech responsibilities for my company. We're using LabTech 10.5 for patching customer machines. In the past 2 weeks, I have gone from a broken, fully manual LabTech implementation to something that is starting to come together. My computers will now automatically join the correct client/location based on the custom agent installer. From there, custom auto-join searches file machines into the proper groups I've specified. These groups automatically onboard the machines and set schedules, etc, based on my group templates. I have figure
  19. In Continuum Patch Policy, they have failure notifications in the form of tickets. It can generate ticket for patch failures after x days out of compliance and I believe this is their way of tracking recent patching failures. Is there a built-in function like this in Automate 11 or, has anyone made something like this?
  20. Plugins4Automate.com has released a new build of Patch Remedy that now handles Windows 10 version 1709. Read our blog for information of what was added to this plugin at https://www.plugins4labtech.com/blogs/blog/patch-remedy-makes-way-for-windows-10-version-1709
  • Create New...