when I use the curl option on Win10 and above there are no user prompts, but this gets run as SYSTEM via old RMM. When I sign into the computer and launch CMD from GUI and use the curl, there is still the prompt. If you have no current RMM tools that run as SYSTEM, maybe PsExec + curl can get the job done?

Just a heads up I always have to add a full path to the "setup.msi" in (both spots) in the curl command provided in the Agent installer screen or I get errors (e.g C:\Users\Public\Downloads\setup.msi)

Can't believe this is actually a feature request - it was like this before you changed it!!

Is there an update on this?

Our primary way of installing agents is through group policy or remote command line.

Since the privacy message has been implemented we have begun installing a third party agent that allows us to use command line modifiers. This means we have to install two agents and touch every machine personally. We would appreciate the agent installer being completely silent since we take responsibility for our customers privacy via BA's that they sign.

We usually roll out new products by pushing out software using group policy which saves a lot of time for administrators.

The Atera agent worked great before it required an acknowledgement. Atera now forces everyone to acknowledge the Agent install. The acknowledgement step is a change that creates nothing but more work or user involvement. It does absolutely nothing useful except involve users or require administrators to visit or remotely visit every machine on the network. .

Having a popup warning requiring a click is an understandable countermeasure to the agent being used by bad actors to take control of unwary users. Especially because Atera can be trialed without the use of a credit card.

As a resolution, we suggest the Agent first contacts the servers and find out whether this is a paid agent, and if it has at least 3 months of activity. If not, the popup shows up. This still allows for a trial of the agent, and will allow Atera to figure out whether this is a legitimate MSP account prior to lifting the popup requirement.

Hope this helps.

My boss and I have had loads of trouble trying to fix a workaround the acknowledge message as our Pc's aren't sorted per location but our users are. Our locations are up to 4 hours away by car so manually installing the client isn't on the table. As the last resort we've had to push the agent to the machines that a user logs into via a Group Policy into an unassigned site and manually sort them into the correct sites.
Another issue, we're missing about 25 computers.
if we didn't have the acknowlegde message we'd have saved days of work and probably all our PC's would have the agent installed.

I agree. I do not understand why Atera put the privacy message in there unless they have customers that are using their platform for malicious activity. But even then, I would assume they would just ban/block them and not change their product.

If that is what's happening, Atera should verify businesses before doing business with them. There are plenty of companies that offer a service to do that, but it wouldn't be hard for Atera to just lookup a business before making a sale. That would prevent a lot of malicious activity.

But as a security measure, it's not a very effective one. Most of us that manage users know that when a message box pops up, most of the people we support will try to close the box or just click ok. The message Atera has does not include the name of the company managing their system, no link to read more from the provider or from Atera, and no clear option to cancel the operation. It really is just a nusance for MSPs and serves little to no purpose for the end user.

If you think about the use case of a silent RMM install, there are really only 3 options: 1) MSP acquires a new client, 2) Existing client acquires new device, 3) Moving to a different RMM.

In the first 2 cases, a manual install on each endpoint is inconvenient but not all that bad. But can you imagine if you had 1k+ endpoints across dozens of clients and were trying to move to Atera? That would be a nightmare to have to hit each one of these endpoints manually. Also, deploying software via GPO is really not a good idea especially when the thing you're installing doesn't like to be reinstalled, and you know it'll need to be updated in at least a year.

I do not understand why RMM providers have to make deployments so unnecessarily complicated. Just provide a static link to the latest version of the agent MSI file, and allow us to specify the necessary MSI properties as arguments when calling. Wouldn't it be great to deploy an agent with a script like this:
msiexec.exe /i https://app.atera.com/GetAgent/latest.msi /qn /norestart ACCOUNT=someone@example.com CUSTOMER=a4ba85 FOLDER=Workstations

This is most likely a measure to combat Atera being used as part of malicious attacks. However, I propose another way of going about it. I would guess that most attackers are either using trials or accounts with an age of less than a year, so perhaps bypassing the prompt for accounts older than that would be a workable compromise.

I chatted with support about this today. They claim it's a security measure, but all it is, is a pain in the ass for administrators. If we're administratively pushing the agent, the ideal solution is to NOT involve the users. Atera now forces everyone to acknowledge this which makes the silent install process a joke. Their solution.... submit an RFE. It's a truly stupid change that makes me second guess my decision to use them.

I ended up repackaging a current Atera agent set to assign to the "unassigned" group and then install the repackaged MSI silently. This way I can copy the files, set reg keys, create and start the service, etc. Would be good to not need this workaround and non-silent install isn't practical when rolling it out in bulk during transition from another RMM.

Why not use the old installer and let atera update itself?