These registry keys can either be deleted manually or by running the below commands: REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\ATERA Networks\AlphaAgent" /f /v AgentId This way after the device is set up and it connects to the web, the keys will recreate automatically. Thus, installing the agent through a cloned image will result in duplicated devices reporting back to the console.Īs a workaround, the image needs to be created with all the registry keys deleted - except for the IntegratorLogin key. When the Atera agent is installed, a unique registry entry called AgentId found in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ATERA Networks\AlphaAgent is created. To disable it, change the value to '0' and the agent will start to work properly.Ītera does not recommend installing the AteraAgent as part of a clone image. If enabled, the value of the DWORDs would be '1' \HKLM\System\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy\MDMEnabled \HKLM\System\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy\Enabled Go to Registry Editor and check the presence of the following DWORDs: If this protocol is enabled, the agent cannot communicate with the console. The AteraAgent does not support FIPS at the moment. Reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v9" /v SystemDefaultTlsVersions /t REG_DWORD /d 00000001 /f To solve this, you can run the following commands in an elevated instance of CMD: reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v9" /v SystemDefaultTlsVersions /t REG_DWORD /d 00000001 /f
NET might be instructed to work with a TLS that’s disabled, which breaks the Atera communication as well (being a. This tool, IIS crypto, is changing the values to…strange values which break the communication over the protocol. This is a notorious tool for breaking TLS communications as it adds strange values for registry keys:Īll TLS keys (Enabled/DisabledByDefault) should have a value of 0 or 1 (disabled or enabled). TLS settings that have been applied with the third party tool IIS Crypto To solve (CMD with admin): bitsadmin /util /setieproxy localsystem no_proxyĢ. To check (CMD with admin): bitsadmin /util /getieproxy localsystem Permit content traffic in addition to TCP (4) traffic.Geo-blocking - As an example, SonicWall routers are well known for their Geo-Blocking features.
ALLOW IDISPLAY SERVER AVAST ZIP
Make sure to permit outbound traffic (ports 4) and file extensions ZIP & EXE from our website (Atera address: ).
Proxy - Proxy / Web-filtering is very common and can also be an obstacle to stable agent behavior.Using a VPN connection may override these restrictions, however, we cannot provide specific instructions or support for setting up such configurations. Therefore, machines that are located in this country will not be manageable from the console. Note: The Great Firewall of China is blocking some of the servers required by the AteraAgent to report the device's availability (online/offline status). In some cases, HTTPS inspection (Deep Packet Inspection/SSL Inspection) can also cause blockages, make sure to disable HTTPS scanning or add Atera and its servers to the whitelist. Make sure to add a rule to allow HTTPS traffic from LAN to WAN (Atera address: ). Firewall - In some networks HTTPS traffic is blocked.For testing purposes, you can also whitelist the folder C:\Windows\Installer, and attempt another installation, the whitelist should be removed once you have finished testing.You may need to enable/add an exemption policy for scanning password-protected ZIP files (or allow unscannable content to pass).Add the following paths to the Antivirus whitelist:Ĭ:\Program Files\Atera Networks (or C:\Program Files (x86)\ATERA Networks for 32bit).List of servers that the agent is communicating with: Allow outbound traffic over ports 4 (TCP/UDP) in the Antivirus, Firewall, and Proxy servers.NET Framework 4.5Īdditionally, please check the following: If after following the instructions for agent installation, you are experiencing any problems with agent stability, alert consistency, agent unavailability or remote connection instability, please verify that you are on.
0 kommentar(er)
