无SCCM环境下批处理检测ESET存在性并自动静默安装的方法

Alright, let's build that batch script you need for checking ESET Security's presence across your SCCM-less environment. Here's a straightforward, reliable solution that checks both 32-bit and 64-bit install paths, then triggers a silent install if ESET is missing:

Core Logic Breakdown #

First, we need to account for both system architectures since ESET installs to different Program Files directories depending on whether the machine is 64-bit or 32-bit:

• C:\Program Files\ESET\ESET Security\egui.exe (64-bit systems)
• C:\Program Files (x86)\ESET\ESET Security\egui.exe (32-bit systems)

If neither of these files exists, the script will kick off a silent MSI install from your server share. If either path is found, the script exits quietly with no extra action.

Full Batch Script #

@echo off
setlocal enabledelayedexpansion

:: Define the two possible install paths for ESET's egui.exe
set "esetPath64=C:\Program Files\ESET\ESET Security\egui.exe"
set "esetPath32=C:\Program Files (x86)\ESET\ESET Security\egui.exe"

:: Check if ESET is already installed in either path
if exist "%esetPath64%" (
    echo ESET Security detected (64-bit install). Exiting script...
    goto :cleanup
)
if exist "%esetPath32%" (
    echo ESET Security detected (32-bit install). Exiting script...
    goto :cleanup
)

:: If we reach here, ESET is missing—initiate silent install
echo ESET Security not found. Starting silent installation from server share...
msiexec /i "\\myserver\your-eset-share\ESET-Installer.msi" /qn /norestart

:cleanup
endlocal
:: Optional: Remove the pause if you don't want the window to stay open
pause >nul

Key Tips for Smooth Deployment #

• Permissions: Ensure the account running this script has read access to your server's installer share, plus local admin rights on the target machine to run the MSI install.
• MSI Path: Replace \\myserver\your-eset-share\ESET-Installer.msi with the actual network path to your ESET installer file.
• Silent Parameters: The /qn flag runs the install completely without user input; /norestart prevents automatic system reboots (adjust this to /forcerestart if you want machines to reboot post-install).
• Testing: Always test the script on a non-production machine first to confirm it triggers the install correctly and doesn't throw unexpected errors.

内容的提问来源于stack exchange，提问作者StackBuck