Jump to content

Search the Community

Showing results for tags 'script run'.



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 1 result

  1. I've been putting together an automated-deployment script for new client workstations and am running into a minor snag - we have another script that installs our managed ESET package which I'm calling via the "Script Run" function in my master script. However, the ESET script has conflict-detection built in and is falsely alerting on Windows Defender as a competing/conflicting AV package. The ESET script has a parameter @ForceEsetInstall@ to disable conflict detection but I can't figure out how to set it from inside my master script. I've tried preemptively setting @ForceEsetInstall@ = 1 in my master script but apparently it doesn't get passed through to the ESET script when the time comes to invoke it. Can anyone tell me what I'm missing (or, indeed, if it's even possible to do what I'm trying to do)? Thanks!
×
×
  • Create New...