Jump to content

database

Members
 View Profile  See their activity

  • Posts

    15

  • Joined

  • Last visited

 Content Type 

Posts posted by database

    ESMC Server to Virtual Appliance: migrate MS SQL db

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hello again,

    after waiting for all the clients to receive the ESMC policy with the new server address, I stopped the old server service and made a SQL backup as per the migration procedure ( https://support.eset.com/kb6764/?locale=en_US&viewlocale=en_US )

    The old server is at address 192.168.2.18 and the new appliance was given temporary address 2.36, which should become permanent. I log on to the VA and load the renamed backup db, but at import time the VA throws an error about missing era_db in the header. After importing it, the VA reboots and shows "configuring" and just sits there. The log shows an error resetting the network card. Do I have to turn off the old server for the VA to finish its config?

    The migration instructions seem to suggest that MySQL is the default; do I have to perform any operations on the MS SQL backup? I didn't do anything except renaming it as per the procedure.

    Thanks!

    ESMC: show clients with pending policy application

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Thank you MichalJ,

    this is working quite well. Filtering by policy name, I'm getting a list of PC's where the policy is applied, with object count. I can compare the 131 total clients from the Dashboard to 107 now complying with the policy.

    If I could get the non compliant hostnames, that would be cool. Maybe I'm missing a negative filter? I'll try to combine more filters ("show all clients with Agent installed, where policy Listen_to_VA is not present)

    ESMC: show clients with pending policy application

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hello,

    I'd like to know if there's a way of knowing the following:

    1. In ESMC, I create a policy and apply it to a group
    2. There's a list of the PC's that received the policy, but I can see no synthetic summary (eg "policy applied to 35 clients") and the list cannot be organized by subgroups.
    3. There's no list of PC's that are in the group, but are not applying the policy (due to being offline or any other reason, e.g. conflicting policies)

    Point no. 3 is very important for certain tasks, eg applying a policy to migrate to another ESMC server (or to the VA, which I'm trying to achieve)

    Thanks!

    Remote locations vs packet repository

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Thanks MartinK

    I do have some local server/NAS box at each remote location so it should be feasible to apply your suggestion.

    The command returns:

    nslookup repository.eset.com
    Server:  FQDN of our main DNS server
    Address:  our main DNS server address

    Risposta da un server non autorevole:
    Nome:    repo.wip.eset.com
    Address:  91.228.167.25
    Aliases:  repository.eset.com

    which seems good to me

    Remote locations vs packet repository

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hello,

    I'm still dealing with the same error as in this thread (I'd resurrect it, but it's probably too old to post):

    Maybe I'm missing something about the configuration of remote locations.

    - The agent successfully installs at first try 95% of the times (2 stubborn clients remain, out of 120 deployments. Only 10 to 15 deployments required more than 1 attempt or taking direct control of the PC)
    - All the remote servers except one were updated via ESMC task (upgrade ESET products)
    - Upgrading clients yields a lot of "packet repository" errors (like 18 fails out of 20 upgrades)
    - The ESMC server is set to AUTOSELECT
    - The "Allow automatic restart" flag is not an option because updates will be pushed whenever the clients are available, and this means mostly during working hours
    - Some clients at the main site will not upgrade, because they are connected to WiFi links set to very low bandwidths (these links are supposed to handle handheld devices for Whatsapp and similar services, but employees like to use them for laptops and then complain about slow network performance). Are there recommendations or guidelines regarding low bandwidth or link interruptions?

    Thank you for your input

    ESMC Agent and ESET Endpoint compatibility with XP and Server 2003

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by database
    Info on last server

    Update: yesterday 2 of the servers updated successfully: a mixture of pending updates with associated reboot, and insufficient disk space on C:\ was leading to the failure.

    Procedure was as follows:

    - Perform disk cleanup on C:\ (from This PC > right click on C:\ > Properties)
    - Empty C:\Windows\SoftwareDistribution\Download
    - Check for Microsoft Updates, apply the important updates, and reboot
    - From ESMC, upgrade your ESET product allowing automatic reboot (do not run the failed task again, just click the Upgrade ESET Products on the installed apps page in ESMC)
    - Wait for the server to come back online in ESMC
    - From ESMC, run an Upgrade ESMC components task (do not rerun the failed task, click on the PC name and select Upgrade ESMC components from recent tasks).

    The last 2003 server was given this treatment, but the upgrade is failing due to unstable Internet link at this remote location. Our ISP is looking into it and should solve the issue today.

    Edit: After the ISP intervention I could upgrade the Agent via ESMC Server task. Since the AV install was still failing ("archive packet synchronization error"), I downloaded the package from the ESET website and installed manually (without uninstalling the previous version). After restarting, the Agent took control of the new version and everything appears to be fine in ESMC.

    ESMC Agent and ESET Endpoint compatibility with XP and Server 2003

    in ESET PROTECT On-prem (Remote Management)

    Posted

    2 minutes ago, MartinK said:

    Could you please try to manually upgrade to AGENT v7 on one of those systems to verify it will be successful? Could you verify that AUTOSELECT repository is used in problematic AGENTs configuration. This specific error means that there is either no package for your operating system, something is not properly configured. I would recommend to concat official ESET support, as they will known what logs are required - especially in case this affects only specific systems. /snip

    Thanks MartinK.

    I know that I can manually install the new agent downloading it from the ESET website, but would it keep the existing configuration? Asking because in a similar scenario I got duplicate clients in ESMC - I overwrote the existing agent distributed via ESMC with one from an integrated installer package (generated by the very same server).

    Also could you please point me to some how-to about retrieving the Agent configuration? Can I do this on the client (rsop style)? I know I can see what policies are applied within ESMC, but I'm not sure that's what you mean.

    Maybe the message has something to do with the "bitness" of those systems? Server 2003 is quite cryptic about it being 32 or 64...

    Thank you for all your other inputs too.

    ESMC Agent and ESET Endpoint compatibility with XP and Server 2003

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hello,

    I'm sorry to resurrect very old OSes, but my production environment is crawling to Windows 10 at an appalling speed. Changes are being done, but both management and staff are pulling hard on the handbrake. In the meantime, it is paramount that old equipment is protected as well as possible, and this brings me to the following questions.

    I'm getting some strange errors when trying to install the latest Agent on some Server 2003 machines via ESMC:

    "Impossibile eseguire attività: Il pacchetto dell’archivio con riferimento non è disponibile"

    which should approximately translate to "Could not execute planned task: referred archive packet not available". I could not find an error code (maybe I didn't see the correct page in ESMC: if it's there, please point me to it).

    These servers are marked as Outdated in ESMC, and another 2003 server updated successfully both AV and Agent, so I suppose they should upgrade too. I always update the Agent before the AV: can I try upgrading the AV before the Agent? What do I do to avoid the error?

    Moving to the latest ESET Endpoint: while ESMC reports XP clients with Endpoint 6.6 as current, some were manually installed with 7.0.2073.1, but upgrade to the latest version seems to fail both via ESMC and ESMC integrated installer packages. Is XP somewhat supported in EE 7 or is it better to leave/downgrade these clients at 6.6?

    Thank you!

    Failed to synchronize packet repository

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Update: MichalJ got back to me immediately today via PM. He did submit my case to the appropriate staff, but the PM was not marked as read because of PM redirection to his email address (the email was read and forwarded, but the PM was not).

    Thanks to both Marcos and MichalJ for their support - let's wait and see if the logs reveal something.

    Is there some documentation on what data does ESMC send, and where it's sent to? Is this reporting optional, or essential for ESMC to work?

    I suppose some degree of logging and connectivity is required to distribute updates and such, but I'd like to learn some more about those "remote logs".

     

    Failed to synchronize packet repository

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hello everybody,

    I'm currently facing an issue with deployment of the latest Eset Endpoint Antivirus to clients from my ESMC (v.7 migrated from 6).

    Everything is fine if I work on the subnet where the ESMC server is. But I also need to manage 3 remote locations, each with its own VPN link, subnet, and local Apache HTTP proxy.

    Updating/remotely installing the client agents always works. Remote uninstall of 5.2 and previous ESET products also works. Upgrading from 6.6 to 7 via "Upgrade ESET products" or pushing installation of ESET Endpoint Antivirus 7 almost always returns this message: "Impossibile sincronizzare archivio pacchetto. Consultare il messaggio di traccia per maggiori dettagli", which should translate to "Failed to synchronize packet repository. Check message trace for more details".

    Again, on the main subnet everything is fine, and in the rare cases where the remote install doesn't show the message on the other subnets, the upgrade/install works fine.

    The proxy cache is populated and set to only accept ESET traffic.

    Is it a bandwidth problem? (speaking of which, is there a way to limit the software transfer speed for ESMC?)

    Thanks!

×
×
  • Create New...