TN LMG 8 Posted May 2 Share Posted May 2 Since migrating to the new Rocky VA, I've been unable to get an Agent Deployment Server Task to run successfully. I realise there are many factors involved here and it may not be related to the new device or migration at all, but wondered if anyone else has had issues or is able to verify whether this still works. I used to run them routinely from the old CentOS server, so I'm confident I have the right settings/permissions. There have been several bugs already with the new VA, so I'm wondering if this is another kink still to be worked out. Quote Link to comment Share on other sites More sharing options...
TN LMG 8 Posted May 2 Author Share Posted May 2 + net -i -k rpc service delete eset-remote-installer -W ******** -U *********** -S ************** WARNING: The option -k|--kerberos is deprecated! Could not connect to server *************** Connection failed: NT_STATUS_INVALID_PARAMETER * [Exit code = 255] This is what I have in /var/log/eset/RemoteAdministrator/Server/trace.log if anyone has insight (domain -W, username -U and target machine FQDN -S have been replaced with stars for security) Quote Link to comment Share on other sites More sharing options...
TN LMG 8 Posted May 8 Author Share Posted May 8 I tested today from a fresh copy of the old CentOS VA and can run an Agent Deployment Server Task to run successfully. Using identical settings on the Rocky VA the task fails. Will raise a support request to have the bug investigated. Quote Link to comment Share on other sites More sharing options...
Solution TN LMG 8 Posted May 23 Author Solution Share Posted May 23 The error messages in /var/log/eset/RemoteAdministrator/Server/trace.log pointed me to /var/opt/eset/RemoteAdministrator/Server/Scripts/UnixWindowsNetworkRemoteInstall.sh In line 623, if I change use_kerberos=: to use_kerberos=false then the task runs successfully. Please note this is not an ESET approved fix, only my own work while waiting for ESET support to begin an investigation. Use is at your own risk. Please ensure you have a backup to roll back to. Quote Link to comment Share on other sites More sharing options...
TN LMG 8 Posted May 24 Author Share Posted May 24 Just to note that I tested and confirmed today this issue is still present on the updated Version: 11.0.19.1 Quote Link to comment Share on other sites More sharing options...
TN LMG 8 Posted May 24 Author Share Posted May 24 Retested after update to ESET PROTECT on-prem (Server), Version 11.0 (11.0.224.0), the issue still remains for deployment to Windows machines. My workaround was overwritten by the update, so I've reapplied it for my server. For any ESET staff, my support ticket reporting this bug, and including log extracts, is #00757734 (submitted 8 May). Quote Link to comment Share on other sites More sharing options...
TN LMG 8 Posted May 29 Author Share Posted May 29 ESET support have finally confirmed Quote The development team is aware of this and it will be fixed in the next release of the virtual appliance. We do not have an ETA for it at this time. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.