Jump to content

Search the Community

Showing results for tags 'plugin'.



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


About Me


Location


Agent Count


INTERESTS


OCCUPATION


ICQ


WEBSITE


WLM


YAHOO


AOL


FACEBOOK


GOOGLEPLUS


SKYPE


TWITTER


YOUTUBE

Found 9 results

  1. Hey All! Been a while since I've posted updated information about this plugin, but I wanted to re-share it since it's grown and improved so much since that last post. ESX hosts are now checked. This will cover the same manufacturers as other computers - HP, Dell, Lenovo, IBM, Toshiba, and Fujitsu. This does require the Virtualization Manager plugin, and the plugin needs to find the hosts in order for them to be scanned. ESX hosts are also added to the WLU report via Report Center. The report is automatically added and will be updated. This eliminates the manual steps of importing and publishing it. Lenovo and IBM look-ups will now include the warranty start date. Any existing look-ups that just have the end date will be updated automatically 30 days after the most recent update, or you can manually update each one from the WLU plugin tile for the computer. The report is cleaned up and separates ESX hosts, servers, and workstations into different groups. The dashboard is cleaned up and more reliable. (Recently added) Improved performance and bug fixes. (Recently added) Report available in report center (that is now automatically integrated and updated). (Recently added) Warranty information can be copied to the computers table and synced to your PSA such as Manage or Autotask. If you're looking for a tool to query warranty information across your clients that works reliably, has great features, and has an affordable cost, you should seriously consider Warranty Looker Upper. You can get more information about it on the plugin page here. Enjoy! -Tim
  2. Hi All, The Discover Keys plugin is an alternate to Product Key collection script provided by ConnectWise the purpose of this plugin is to collect product keys using either Produ-Key (Free) or Recover Keys (Paid) and populate the information collected into Product Keys Table in Automate. The plugin isn't 100% finished and is a little rough around the edges in some aspects (this has been the case for a while, i know!) but it works and unfortunately I've had to focus efforts elsewhere. There is currently no Documentation available for this integration but i believe it to be simple enough to install and configure, a highlight of the features is below Availability Install this integration through my Plugin Installer All Installs will activate in Trial mode At this stage the plugin is operating in an Extended Trial mode through to the end of 2019, this could potentially change but you will be notified Currently no documentation is available. Current Version Info Discover Keys - 1.0.1.8 Discover Keys Remote Agent - 1.0.1.8 Features Script Free - All Product Key collection is handled as an Inventory Process on a schedule, currently this hooks into the "Software Inventory" but plans will be to split it out into it's own schedule ProduKey - Free Product Key Recovery utility, ProduKey executable is transferred from the Automate Server to the Computer. Recover Keys Version(s) 11.0, 10.0, 9.0 and 8.0 - a more advanced collection method using a licensed product which provides greater detail and supports a larger product range, again files are transferred directly from the Automate server to the Computer. Product Keys Tab - Added a tab to the Computer Screen to show Product Keys directly relating to the computer you are viewing. Setup Install the Plugin using the Plugin Installer listed above, wait 60 seconds. Reload your Automate Control Center. Navigate to the System Dashboard > Config > Integration > Discover Keys and select your desired options. Done! Notes Recover Keys 11.0, 10.0, 9.0 and 8.0 are Supported. Failing to enter a Recover Keys Serial number will result in Recover Keys running in a Demo Mode which will return partial key information. Entering an incorrect Recover Keys Serial number will result in Recover Keys running in a Demo Mode which will return partial key information. There is an option to Disable the In-Built Product Key collection script. Recover Keys files will be automatically downloaded to your LT Share for distribution. ProduKey files will be automatically downloaded to your LT Share for distribution. The Product Keys Tab on the Computer Screen has linked permissions directly back to the users right's to View or modify Product keys (Client Level Permission), the TAB will NOT appear if the user does not have rights to view Product Key,
  3. Sendto Slack - a LabTech plugin that can be used to send LabTech alerts to Slack channel or slack user using LabTech Alert Template. It works like email alert action. You can send LabTech alerts to any number of Slack workspace. Please visit the following link to know more about this. https://sankalpit.com/sendto-slack-plugin/ Thank you
  4. Hey everyone, I decided to flex my programming muscles a bit and try to develop some internal-use plugins for Automate, but I seem to have hit a snag. I was attempting to follow the quick start guide located here but unfortunately it's outdated now that Automate 12 is in production. I chatted with official CW support and the tech told me that his manager told him it has something to do with the fact that Automate 12 uses REST API for plugins instead of SOAP API which was used by version 11. I'm not sure where to go next as I was hoping for a simple guide to use as a starting point. Any tips/suggestions? Thanks in advance!
  5. How are other people with Webroot monitoring for threat detections on Macs? The 3.0 plugin does not pull detection data from the GSM console into the plugin_webroot3_threathistory table (as it does for PC's), and thus the "Webroot 3 - Active Infection" monitor never triggers for Macs. Webroot support confirmed this is expected behavior (since the mac client isn't "fully supported" yet).
  6. For those using the Surflog plugin we have launched a new build 1.2.0.x that uses the DevExpress Charting to make in compatible with Automate 12. The drawback is that Labtech 10.5 users should not upgrade from the 1.1.3.x builds of this plugin. New Automate 12 Computer Console View
  7. I installed the Expiry plugin and users are listed with the number of days left until password expiration. The issue I am having is the email is being sent with "Domain Password Expiration Notification" in the subject line and "Ok" in the body. It should email the users a specific template made in html with the user's name, how many days left, and a link to reset the password. Any idea why this would be happening?
  8. Does anyone know of a way to test whether a (specifically Mac OS X) endpoint is accessible via ScreenConnect without actually launching a session and potentially incurring a confused/irate call from a client about why we were randomly taking over their system? I'm fighting with an issue where multiple Mac OS endpoints show ScreenConnect as installed but will only display a black screen (or the "your partner has not connected yet" error) when our techs try to remote in. I've attacked this in a couple of ways, including a Labtech search for installed software and a script that queries running processes with pgrep and returns the PID for screenconnect and/or connectwisecontrol. Some of these systems report the plugin running and return a valid PID (confirmed via terminal commands in the Labtech CMD prompt) but they're still not accessible via a ScreenConnect session, which our techs only find out when they actually need to open a session. I've seen some posts here about running commands against ScreenConnect and a script uploaded to reinstall/redeploy on Windows and MacOS hosts, but I'm not sure how to go about applying them. Ultimately what I'm looking to do is get a definitive list of hosts that cannot be accessed via ScreenConnect (even though the client is present and the process running...GUID mismatch maybe?) so that I can then force a removal and redeployment. Any assistance is greatly appreciated. Thanks!
  9. 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
×
×
  • Create New...