Iain Rawson 0 Posted June 19, 2023 Share Posted June 19, 2023 I have created an installation package for ESET 10 via the Protect Cloud console. This install package works fine and installs perfectly, however when trying to use the --silent --accepteula --avr-disable flags in the command line within the WDS/MDT deployment system, the install has failed every single time I've attempted this. After rebooting said machines at the end of the MDT process, logging back in and attempting to install from the same package, it works fine. Have the silent install flags changed at all or is there something I'm missing here? Thanks, Iain Link to comment Share on other sites More sharing options...
Administrators Marcos 5,238 Posted June 19, 2023 Administrators Share Posted June 19, 2023 What if you run the installer with the said parameters? Does it work or end with an error? Link to comment Share on other sites More sharing options...
Iain Rawson 0 Posted June 19, 2023 Author Share Posted June 19, 2023 I've just removed the AV install from the MDT deployment role for a moment - I'll run a laptop through it and attempt manual install with the parameters at the end of the install before rebooting (so it's still in the same state as it would be - after a reboot I do usually log in with network credentials rather than local). Thanks, Iain Link to comment Share on other sites More sharing options...
Iain Rawson 0 Posted June 20, 2023 Author Share Posted June 20, 2023 Just tested - with the flags it does nothing - simply pops up in task manager then goes away. Without any flags it provides an error stating there is no connectivity, so it would appear to be an issue with our web filtering, hence why it works fine once logged back in with network credentials and credentials have been passed to the filter. Thanks for your help - no issue to diagnose, it seems!! Iain Link to comment Share on other sites More sharing options...
Command IT 7 Posted June 21, 2023 Share Posted June 21, 2023 We had the same issue. Removing the --accepteula flag got ours working. We also don't use the --avr-disable flag. So we just use PROTECT_Installer_x64_en_US.exe --silent John Link to comment Share on other sites More sharing options...
Administrators Marcos 5,238 Posted June 21, 2023 Administrators Share Posted June 21, 2023 For me it works also with the --accepteula parameter. The only time I the installer did not run successfully was when I executed it without elevated administrator permissions. Link to comment Share on other sites More sharing options...
Recommended Posts