Greetings, I'm running a test for ESET PROTECT (VA) with 3 x Windows end nodes in an offline environment. I have created an All-in-One installer including two custom policies specified (one for endpoint one for agent). I can still see the names of these policies shown at the beginning of the installation process, however, I noticed from the web console that neither of the policies were applied to the security product initially, then after the auto initial scan starts running, the builtin 'HTTP Proxy usage' policies for both ESET Endpoint for Windows and ESET Management Agent were applied on the security product on the node
Does anyone know how to fix this?
Thanks!