Search the Community
Showing results for tags 'script run'.
Found 1 result
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!