LesRMed

@pudding69 Honestly, do you really think comments like this will help you get anywhere?

It is working this morning. Thank you!!

Created a new one and got the same results.

I found this entry in the Logs collected on the PC that I think is the issue - HTTP Request to "repository.eset.com/v1/com/eset/apps/business/eea/windows//manifest.erm" opened with status=20011 and response=404 Logs attached ELC_logs.zip

We're using ESET Protect Cloud AV and File Security for Windows Servers (3AK-ACH-MEN). I've had an issue trying to run the AIO installer on two servers yesterday and now a PC today. When the new File Security was announced yesterday, I created a new AIO installer (maybe didn't need to do that) and tried to run it on two different servers, but kept getting the attached error. Today, I'm setting up a new PC and using the AIO installer I've been using since we moved to the cloud version. I'm getting the same message at the same point in the install. This comes up almost immediately after clicking Continue on the Install Components screen.

How does this relate to ESET?

I haven't had any problems at all and I've been on and off of the forums all day.

Does the path maybe need to be in quotes?

I did what the instructions told me to do (see below). And since that's the only Management Agent in my cloud console, that's the one I modified. Nowhere in it does it reference any certificates.

So basically, I get to do a manual agent install on all my workstations. Not cool!!

@MichalJ Is there a way to change the certificate on the "cloud server" to match what's on all these clients?

I did the migration by following this article: https://help.eset.com/protect_cloud/en-US/?cloud_migration.html Everything went fine with the migration for all the local endpoints. I spent the weekend remoting into PC's that are external to our network to manually install the new version. Everything was running fine. I did an edit on the agent to lock the policies (see below) so they couldn't be changed on the workstations. Within seconds, every endpoint that was turned on went red with the Peer Certificate error. As far as I can tell, there is no way to edit or change a certificate anywhere in the agent. Since there is no certificate listed anywhere (and there's only one ESET Management Agent shown), I'm really confused and upset that this simple change created this huge problem.

Geez! That makes for a lot of work on my part. Any idea what would have caused this?

Is the "Agent Upgrade" task what I should use to re-deploy? I ask because I did that, but it's not running on the clients.

I'm getting this on the clients:

I recently migrated from a local ESET install to ESET Cloud. Everything was fine, all the computers were being updated. I made a change to the agent to lock some of the settings. Now all of my computers are reporting that the Peer Certificate is Invalid. How can I remedy this?

Thanks, but that's off as well.

I just migrated our company from EAV to EPC. All the existing policies were migrated over. I had it set to not show when Windows required updates. The policy still shows "No Updates", yet I'm seeing warning in the console. What am I missing?

Anything you upload here can only be viewed by ESET personnel.

I did, that's why I said if you got it to work on a couple of them, then you did better than I did. LOL

If you got it to work on a couple of machines, you did better than I did. Even though it said success on every computer I ran it on, it didn't work. I finally gave up and I'm about to embark on a migration from my local setup to the cloud as shown here https://help.eset.com/protect_cloud/en-US/cloud_migration.html.

That's what I was looking for! Thank you @MichalJ!!

I guess I should have added this to my original post...I've tried using the remote deployment tool and even though it shows successful, nothing changes on the computers. It seems that the only way to get them to show up correctly is to manually uninstall and manually install the new AIO installer.

I'm moving our company from ESET Protect to ESET Protect Cloud. I enabled a rogue detector to gather a list of computers only to find that there's not an Agent Deployment Task in the cloud version. What's the easiest way to get the agent installed without manually going to each computer?

Thank you @MichalJ and @Marcos! This is what I've been looking for. Now I just need to figure out how to get it in our MSP account. Thanks again!