Jump to content

local updates setup for PROTECT env.


Recommended Posts

  • Most Valued Members

Hi,

In the past with ESMC, I had setup an Agent policy that gets the deployed agents to point all updates requests to a local server.

I'd set the Updates path as http://<server>/updates/eset_upd/era6

Recently, I believe this isn't the right setting.  Looking at the site's documentation, it seems like I should just put

http://<server>/ 

I have the mirrors set to /opts/updates and Apache's backend directory set to /opts/updates.

Is this correct?

Thanks

Ed

Link to comment
Share on other sites

  • Administrators

Do you create a mirror with the ESET mirror tool on Linux / VA? Did you install Apache there to make the mirror accessible via http?

Link to comment
Share on other sites

  • Most Valued Members
1 hour ago, Marcos said:

Do you create a mirror with the ESET mirror tool on Linux / VA? Did you install Apache there to make the mirror accessible via http?

Yes, I used the mirror tool to download the necessary files to the /opts/updates path.   Apache is installed and is working.  I think what is confusing me is that from the Apache logs, module updates are looking for :

 

"HEAD /updates/dll/update.ver" 

I think I am confused in what i should put in the "custom server" updates part. For both the Updates and repo.

Thanks

Edmund

Link to comment
Share on other sites

  • Administrators

If /opts/updates is the web root folder set in the Apache cfg, use the update server path http://%ServerIPAddress% or https://%ServerHostname% on endpoints.

Link to comment
Share on other sites

  • Most Valued Members
12 hours ago, Marcos said:

If /opts/updates is the web root folder set in the Apache cfg, use the update server path http://%ServerIPAddress% or https://%ServerHostname% on endpoints.

I set that; but for some reasons (my confusion, probably), I see "HEAD /dll/update.ver",  which would refer to /opt/updates/dll/update.ver.   But in my /opt/updates directory, I have eset_upd/{ep10,ep6,ep7,ep8,ep9,era6,v4,v5}.

In the past, I'd fix the updates to /opt/updates/eset_upd/ep7  but that would only work for ESET v7 products.

For mixed product environments, that'd be wrong, no?  That's what's confusing me.

Thanks

Edmund

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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