satellite360

Thank you.

Thanks - and is there any reason to keep the Rogue Detection Sensor installed or is that also redundant?

Hi I have recently migrated from a local install of Protect Server (v.9) to Protect Cloud having followed this guide: https://help.eset.com/protect_cloud/en-US/stop_using_cloud.html?cloud_migration.html All is working fine but I still have ESET Protect Server running on the local server. Is there a recommended method for uninstalling given that it is no longer in use? Thanks

I ended up reinstalling on the client which resolved the problem.

I have a client laptop that is showing as connected on both the client itself and via the Eset Business Account site (eba.eset.com/ba/devices) but the last connected time on the Protect Cloud is not updated and is showing a different software version to what is actually running on the device. Any advice on how to correct this? Thanks.

Pleased to report that upgrading to Management Agent 7.0.577.0 resolved the problem. Thanks.

Hi Attachment unavailable.

Hi I'm seeing this on all our clients (70+). Any indication as to whether or not this is affects performance? If not I'm content to leave until ESET supply a fix - would be interested to know if one is on the horizon. Thanks

We are not using HTTP proxy. Based in Beijing, China.

Guessing the following from \ESET\RemoteAdministrator\Server\EraServerApplicationData\Logs\trace.log might be what you are looking for?

Repository appeared for a while and is now empty again. Can you clarify which trace.log file should be checked? Thanks

Repository has been empty for me for several days now. No change in configuration (set to AUTOSELECT). Is there a way to resolve as waiting doesn't seem to be helping.

I've sent in both web seat ids and public license id but the problem persists - any news on getting this fixed? Thanks

17-18 hours since the upgrade. Rebooted after the upgrade and again just now. Just messaged you with the value of HKEY_LOCAL_MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Info\WebSeatId Thanks

Hi Marcos Just upgraded clients to 6.6.2068 and all are suffering from this issue. Just checked and there are no Username/Password values in the registry settings.