Sperber

Thanks @LesRMed, assumed that there is an FTP or something like that. @Marcos, I´ve created a support ticket and included a secure link to the logfile.

Hi Marco, the generated logfile is not only compressed 110M big, but contains also securitywise info I can´t publish to a forum. Likewise the file is to big for the Contact ESET Technical Support-form (max. 21M). How shall I proceed?

Found this topic and I am aksing myself, wether this could be the same for me: - even when the Apache HTTP Proxy is replaced with ESET Bridge in v10. 48 servers, all in the same local domain and internal network, ranging from MS Server 2008 RC2 to 2022, the 2008RC2 are running on v9, no server has local firewall rules, no firewalls in between to the protect server with configured and running Update-Mirror and HTTP-Proxy. 19 Servers show the warning in the Protect Server and the local Client, that the EPNS-Service is unreachable. Doing a netstat on the Protect Server shows the other servers having a persistent connection to the epns-broker via the HTTP-Proxy. All servers have the same policies and all policies have been applied to each and every server. Meanwhile we´re looking for 2 days into it, to find a pattern that could make sense to be the origin of this weird behaviour. Any help would be really appreciated.

The issue has been solved. The RDT is obviously accessing the payload file in J:\eset\RDT\Deployment_Packages\Server64bit not from the local system where RDT is running. It just collects the info, passes it on to the Eset Protect Server and the server itself tries to access the file for the deployment. For that reason one can´t depend on the path the file explorer of the RDT chooses, but one rather has to use the absolute path in the network environment: \\SRV12345\\eset\RDT\Deployment_Packages\Server64bit\filename.exe . Unfortunaly it seems to me that this is nowhere mentioned in the docs.

Good morning everyone, trying to test a mass deployment for all domain-servers with a single one, using the RDT with domain admin credentials, an install-agent file without server/client binding. The install file resides in a file server path J:\eset\RDT, a shared folder every user in the network can access. Despite that, RDT tells me it can´t access the file, as seemingly it can´t find the path. Which is weird, since the file was selected by using the in-built file-browser, if this refers to the file server path at all. Or is this error message trying to tell me it can´t copy the file to the intented target system, as it can´t find some (which?) path on that machine? Is there some more information about the error code available, since I could find nothing in the KB or the forums? Or anyone around who could help me out here with a little assist? Any help appreciated. TIA!