Jump to content

Configuration of Micro Program Component Update (MicroPCU) for a Mirror Environment.


Recommended Posts

Hello @Marcos and Team,

 

I will want to know how to configure the Micro Program Component Update (MicroPCU) in an environment which is completely closed to the internet with 2 update servers acting as ESET Update Servers On-Prem for load balancing and Bandwidth saving purposes. 

1. Do I have to use the {hxxp://IP_Address:2221} method in the Component Update Section

2. Do I have to use the auto-select feature in achieving the required outcome.

 

Note: the environment is completely closed to the internet.

Link to comment
Share on other sites

  • 2 weeks later...

A month (if not more) has passed since the release date of ESET Endpoint Security 8.1.2031.0 and it is still not clear how the MicroPCU update mechanism works and whether it works at all.

Link to comment
Share on other sites

  • Most Valued Members
2 hours ago, labynko said:

A month (if not more) has passed since the release date of ESET Endpoint Security 8.1.2031.0 and it is still not clear how the MicroPCU update mechanism works and whether it works at all.

 

Quote

 

Details

MicroPCU provides automatic updates of ESET products and reduces required maintenance. MicroPCU does not interfere with the running instance of the endpoint and loads new drivers, components, and modules only after the recommended restart. MicroPCU does not require an immediate restart. It upgrades rather than reinstalls your product, it downloads less data (differential), comes with a friendly or completely suppressible reminder for the user, and is compatible with managed networks. Additionally, it has an Auto-update mode, which will update the endpoint as soon as the package goes through a successful global release.

Unmanaged environments: By default, Program Component Update in ESET endpoint Windows products is set to Ask before update. The ESET endpoint product will prompt you to confirm or refuse the program component update when they are available.

Managed environments: The automatic detection of installed Agent hides the Ask before update option in the Policy.

 

I guess you have to configuure it because as Default it would just ask for an upgrade , it won't do it automatically.

Link to comment
Share on other sites

Any word on this, I have purposely left a test machine on EEA v8.0, accepted the EULA prompt in ESET Protect, verified policies are set to automatically handle program updates, and nothing has changed to bring it to v8.1. 

Link to comment
Share on other sites

  • 2 months later...
  • 2 weeks later...
  • Administrators

1, To update modules that you share via http in your network, enter http://%ServerIP% in the Update server field under "Modules update"

2, To update the program from a local repository that you share via http, enter http://%ServerIP% in the Update server field under Program updates. You can update from ESET's servers, however. If you use an http proxy, it will cache the update files for use by other clients to update.

Link to comment
Share on other sites

  • 2 months later...

@Marcos,

I am using EFSW to download mirror. For months, there is no any uPCU files downloaded Mirror folder. Is there anything additional I need to know to download uPCU files over EFSW?

Edited by mathisbilgi
Link to comment
Share on other sites

mathisbilgi,

I don't know about EFSW, but I'm using ESET Mirror Tool 1.0.1258.0.

An example of running a program with parameters:

Quote

C:\MirrorTool\MirrorTool.exe --repositoryServer AUTOSELECT --intermediateRepositoryDirectory C:\MirrorTool\Temp --outputRepositoryDirectory "c:\Program Files\Apache HTTP Proxy 2.4.48\htdocs\v1" --filterFilePath C:\MirrorTool\filter.txt

Filter file (filter.txt) content example (the filter is configured to load only one product):

Quote

{
  "products": [
      {
        "app_id": "com.eset.apps.business.era.agent",
        "version": "=0.1.2.3",
        "languages": ["en_US"],
        "os_types": ["windows"],
        "platforms": ["x64"]
      },
      {
        "app_id": "com.eset.tools.installers.bootstrapper_era",
        "version": "=0.1.2.3",
        "languages": ["en_US"],
        "os_types": ["windows"],
        "platforms": ["x64"]
      },
      {
        "app_id": "com.eset.apps.business.ees.windows",
        "version": ">=8.1.2037.2",
        "languages": ["en_US"],
        "os_types": ["windows"],
        "platforms": ["x64"]
      }
    ]
}

 

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