Jump to content

Search the Community

Showing results for tags 'mac'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • MSPGeek
    • The Geek Cast
    • Code of Conduct
  • 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. With recent events, the demand for remote connectivity is high. For partners using the MAC Signup functionality issues can arise when remote connectivity solutions use duplicate MAC addresses. Like most issues in Automate, it's possible to work around this and use monitors/scripts/searches/etc. to create a creative solution. However, basic validity checking is a native function of MySQL, and there's an elegant approach that will help in this situation (and may not completely replace creative solutions). This guide is designed to demo how to use database triggers in MySQL to enforce data validation. This can be useful for several things, but we'll use the "duplicate software MAC" problem (Cisco AnyConnect VPN) as our example. Important notes: Database triggers are rather low-level items and are difficult to troubleshoot You can only have one trigger per time per operation per table This is unsupported by CW (both on the grounds of database modification and the manipulation of how the application works). With that, open up your favorite MySQL client and let's get started. DELIMITER $$ CREATE TRIGGER `computer_update` BEFORE UPDATE ON `labtech`.`computers` FOR EACH ROW BEGIN IF NEW.mac IN ('00-05-9A-3C-7A-00', '00-00-00-00-00-00') AND OLD.mac IS NOT NULL THEN SET NEW.mac = OLD.mac; END IF; END$$ DELIMITER ; The above code creates a trigger for the updating of the MAC address in the computers table. MySQL triggers can reference the old and new values, and they do so via KEYWORD.COLUMNNAME syntax. We begin by checking if the new MAC address is in the list of known bad MAC addresses ('00-00-00-00-00-00' is just added here for example) and if the old MAC address is not null. IMPORTANT: This means that if there's no existing MAC address (like on agent signup) this MAC could still be written to the DB. This is why the creative solutions might still have a place depending on the particular issue you're solving. For this particular issue, we're going to assume that these MAC addresses are already blacklisted for signup and we're just trying to solve for inventory updates. Next, we set the new value for the column to be the old value, as we'd want to keep the old MAC address if a user connects a VPN client. You'll notice that we switch the delimiter when creating this trigger. This is needed since our trigger itself contains semicolons, and to parse correctly we temporarily switch how we're terminating our lines. This may throw your particular SQL client for a loop. At this point, once we execute the code to create this trigger we are set. If you try to update a computer's MAC address to one of the values in the list the statement will still run without errors, but the value won't change (this would appear to be black magic to anyone who did not know the trigger was in place -- please be advised if you're considering a broader use case). Hopefully this guide has been useful to you. If you ever need support for the Automate database and want a professional DBA opinion feel free to reach out to us: https://automationtheory.org/
  2. I've noticed lately that a lot of the time when I run commands against Mac OS X endpoints, the shell returns "OK" rather than the expected result of the command. For example: ls /Applications OK This happens when running commands interactively as well as when the commands are executed by a script - I enable script engine logging (and even explicitly log %shellresult% to the console) and the same thing happens: a long list of comments on what the command is doing, with "OK"s between them. Does anyone know why this is happening and/or how to fix it? Some Mac endpoints respond fine to shell commands, but then stop. Others have a chain of "OK" entries in recent history but then respond fine to interactive commands when I test them. Makes no sense to me.
  3. Does anyone have a working AV Definition configuration for ESET Endpoint Antivirus on a Mac? I have tried a few combinations today, but can't get it working. I found a post from 2013, which mentioned LT Support had informed it was not possible to monitor AV on OSX, but it was a long time ago now, so hoping that has been resolved! Below is what I have tried. Thanks Kev
  4. Hey Guys! Has anyone had any luck creating an agent uninstaller script for Mac endpoints?
  5. Is there a way to force Labtech to see the agent as a server instead of just a workstation, aside from installing the Mac Server software package? Thanks, Stephen
  6. Hey All, We are running into an issue with machines running the latest version of OSX (10.13) Apple has enabled a feature blocking apps that touch the kernel (Eset in our case), and make you click a couple buttons to allow it. May not seem like a big deal on the face, but tracking down users and clicking a couple buttons on over 100 machines is going to become a lot of work fairly quickly Her is the Eset and Apple KBs: https://developer.apple.com/library/content/technotes/tn2459/_index.html#//apple_ref/doc/uid/DTS40017658 https://support.eset.com/kb6512/ Eset just told me they don't have a workaround. I wanted to know if you guys have any ideas on getting around this in an automated fashion. Thanks, Stephen
  7. 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).
  8. Has anyone had any luck writing a LT Script that will copy a URL file to a Mac OS desktop? Or create the URL shortcut some other way using Labtech?
  9. Hi we are looking to address a critical security flaw lets anyone gain root access to a Mac running macOS High Sierra. We would like to make sure the root account is set with a password as that is the recommended best solution for anyone running OS High Sierra. Any thoughts on how one may be able to achieve this from the dashboard? When I check System > Users the user box is blank. Here is an article discussing the security flaw: http://bgr.com/2017/11/28/macos-high-sierra-login-bug-hack-how-to-fix/
×
×
  • Create New...