Jump to content
An upgrade will take place on June 18, 2024 during the midday hours (UTC). The Forum will not be accessible for a short period of time. ×

Agent Deployment - Server Task - New Rocky VA


Go to solution Solved by TN LMG,

Recommended Posts

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.

Link to comment
Share on other sites

+ 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)

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

  • 2 weeks later...
  • Solution

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.

Link to comment
Share on other sites

Just to note that I tested and confirmed today this issue is still present on the updated Version: 11.0.19.1

Link to comment
Share on other sites

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).

Link to comment
Share on other sites

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. 



Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...