Jump to content

Search the Community

Showing results for tags 'windows'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • MSPGeek
    • Announcements
    • The Geek Cast
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development

Categories

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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Agent Count


INTERESTS


OCCUPATION


ICQ


WEBSITE


WLM


YAHOO


AOL


FACEBOOK


GOOGLEPLUS


SKYPE


TWITTER


YOUTUBE

Found 5 results

  1. We are a small tech team servicing multiple clients (mostly dents offices) and many do have windows 10 computers. Due to what Microsoft has changed to their updates some updates cannot be pushed by labtech and need to be done manually. How are ya'll handling pushing these updates that labtech is not pushing. Is there a script we can create to push these big update such as the version 1809? Is the plugins4automate Patch-Remedy a good option? Anyone use it?
  2. Hi All, Following an update to 1809, we have had issues with definitions for any Windows 10 machine with Intune (or just the vanilla Windows Defender). Turns out the 'RemediationEXE' referenced by the LT default definition no longer exists. I create the below definition which seems to work fine - thought I'd share with you all! 😀 Name: Windows Defender 10 AV Process: msmpeng* Program Location: {%_if|{%_ne|{%-HKLM\SOFTWARE\Microsoft\Windows Defender:DisableAntiVirus-%}|1_%}|{%-HKLM\SOFTWARE\Microsoft\Windows Defender:InstallLocation-%}MsMpEng.exe_%} Definition Location: {%-HKLM\SOFTWARE\Microsoft\Windows Defender\Signature Updates:SignatureLocation-%}\mpavdlta.vdm Date Mask: (.*) Update Command: "{%-HKLM\SOFTWARE\Microsoft\Windows Defender:InstallLocation-%}\mpcmdrun.exe" -SignatureUpdate -Trace -Grouping 15 -GetFiles
  3. 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 more to patching then just letting the approvals happen. Windows regularly updates the agent (engine) they use to manage and seek for patches. By making sure this agent stays up to date you are making sure your users PCs stay current with the latest in system and office patches. We wanted to help the fellow LabTech geeks out there with a tool to help identify and rectify systems that are falling behind with the current WUA version. So we created Patch Remedy to assist LabTech MSPs with managing WUA. The tool is very simple to use and is mostly automated. Just turn on the master switch and wait for the data to start streaming in. We also added several manual tools inside the plugin that will allow for quick remediation of several common issues with WUA. This plugin is based on this post - http://www.labtechgeek.com/forum/viewtopic.php?f=7&t=2123 https://www.plugins4labtech.com/products/patch-remedy Enjoy Cubert :ugeek:
  4. johnduprey

    Windows License Information

    The purpose of this script is to collect license data for windows from a workstation and populate EDFs. There are monitors included that can be used to collect license data and report on any potential issues. Directions: Import the XML expansion first, this includes the script and EDF values. Once the EDFs are installed, import the monitor SQL Create an Alert Template on the Licensing - Refresh License Data monitor to run the script. This will refresh KMS/Eval based licenses daily, MAK/Retail/OEM licenses generally will never need to be refreshed since they don't expire. Set alert templates on the other monitors to create a ticket or send an email accordingly. Edit: Updated to add Partial Product Key EDF and modified schedule to refresh licensing weekly for systems with a valid non KMS license. Windows Licensing.zip
  5. Cubert

    Chocolatey For Automate Plugin

    We just extended the beta of Chocolatey for Automate and released build 3.0.0.16 today https://www.plugins4labtech.com/blogs/blog/chocolatey-for-automate-beta-gets-extended
×