Jump to content

Update issue in Endpoint security 6.4


21jags
 Share

Recommended Posts

Hi, 

 

We have created policy for updates using sharing method.

 

We are using Endpoint security 6.4 on all of the system(100). Out of which there 13 client having Window XP SP3.

 

Now the problem is when we update window XP system it's give error Username and password is invalid.

 

But with the same policy we are able to update ESET VSDB  on other OS.

 

Check console the client is communicating properly.

 

The issue is with Only window XP system.    

Link to comment
Share on other sites

  • Administrators

What product do you use to create a mirror? What operating system is the mirror stored on? Is that computer in a domain? How does the path to the mirror look like in the update setup on Windows XP? Is the username in the update setup on clients in the form of domain\username ? Is sharing the mirrored files via an http server not an option for you?

Link to comment
Share on other sites

We have used ESET file security to create mirror. Mirror is stored on Window server 2008 R2. The working environment is work Group. \\Server-IP\Esetmirror is path and in username and password we gave System credential.

 

With http server we were facing many issue.

 

Now the update issue has been resolved in all system except window XP systems 

 

We have allowed sharing for ESET mirror for to everyone.    

 

The User is having 100 workstation and facing issue only with 12 XP workstation. 

 

Other than this agent is communicating properly. 

Link to comment
Share on other sites

  • ESET Staff

This is most probably caused by "ESET Service" being executed with LocalSystem system account (this can be verified in services.msc). I would suggest to double-check permissions configuration and search for possible solutions as it seems this may be problem especially in non-domain environment, see for example this topic in microsoft's forum. For further analysis starting cmd.exe or other programs with the same privileges may be required, as described in "Running a CMD prompt as System". Is it possible to enable logging on server hosting shared folder to check authorization failure?

Link to comment
Share on other sites

  • Administrators

With http server we were facing many issue.

 

Did you have issues with Apache HTTP server, IIS, another http server or the internal ESET's http server? What kind of issues did you encounter? Providing updates via http is usually hassle-free unlike providing them via network shares.

Link to comment
Share on other sites

The client is using proxy for internet connection which is configured on 3128 port. Apache HTTP server is also configured on same port so change the Apache HTTP server port to 3129, but the distribution of update was not proper, Only some of the Workstation was getting Updates.

Then tried update through ESET HTTTP server and it was conflicting with web control.

Earlier client was using Version 5 and update distribution was configured using sharing method.

Will check the the solution provided by MartinK and inform you the same.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

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