Quick Heal Endpoint Security

Which application is the best for endpoint security in small to mid-size organizations?

Quick Heal Endpoint Security (QHEPS) is the best endpoint security for small to mid-size organizations. This application security provides complete antivirus protection to the computers against malware, Trojans, and worms, network security against backdoors, hackers, and spyware, and web security against phishing, riskware and pornware.

It is a web-based IT security management application that includes the following features:

  • Manage clients in the small to mid-size network.
  • Group the clients into domains for managing network security centrally.
  • Provides latest information of all clients and keeps comprehensive logs about virus incidents, company security policies, and web security updates at a central location.
  • Coordinates automatic deployment of antivirus security policies, signature pattern updates, and software updates on every client and server.

The network structure of our organization is based on agent server/client agent architecture. Is Quick Heal Endpoint Security fit for it?

Yes. Quick Heal Endpoint Security works on client/server architecture that ensures complete networking security.

  1. Agent Server: runs on server where QHEPS is installed
  2. Client Agent: runs on workstations
    • Default Port of Agent Server: 5044 (Administrator can change this default port)
    • Default Port of Client Agent: 62115 (If this port is used by any other application, Client Agent configures itself to some other port which is free. (E.g. 62116, 62117 etc.)
How does Agent Server work?

Agent Server is a service that runs on QHEPS Server system. It helps in sending various requests such as Client Settings, Scan Now, and Update Now to all the clients initiated by the Administrator. It also provides latest information of the clients and keeps comprehensive logs about virus incidents, company security policies, and endpoint security updates at a central location.

How does Client Agent work?

This feature of network security runs on every QHEPS Client system. It communicates with the Agent Server and performs various tasks such as Scan Now and Update Now initiated from the Admin Server by the Administrator. It also sends virus logs to the Admin Server when any infection is found and status information if it is changed.

Taking updates on each client separately in the network makes it a hectic task. Does Quick Heal Endpoint Security have any solution to it?

Yes. Quick Heal provides a tool called Update Manager integrated with Quick Heal Endpoint Security that is centrally deployed to help download the latest updates from the server of Quick Heal. This tool constantly monitors whether new updates are available from Quick Heal and if available it automatically downloads them. It shares the latest downloaded updates to all the clients in the network. Thus you do not need to download the updates on all the clients separately. This feature provides complete application and computer data security against latest threats.

Our organization needs endpoint security to be deployed in various ways given that the clients are installed in physically dislocated workstations. How does Quick Heal Endpoint Security help in this?

Understanding the needs of today’s IT security management, Quick Heal Endpoint Security has been designed to be deployed in various ways such as:

  • Synchronization with Active Directory
  • Remote install
  • Notify Install
  • Client Packager
  • Login script setup
  • Disk imaging

Why is Quick Heal Endpoint Security not getting installed although Client Agent is installed successfully?

Possible causes are listed as follows:

  • The Client Agent is not able to download the build as the Endpoint Security site is not accessible from the remote system. This problem generally may occur in case of domain-based network and improper DNS configuration.
  • URL or port is blocked in Firewall.
  • Insufficient free disk space on remote system.
  • The Agent Server service is not started on the Endpoint Security server.
  • Internet connection is configured using Proxy Server.
  • Incorrect subnet mask is configured on the remote system.

You can resolve this problem in any of the following ways:

  • Check the system on which the Endpoint Security server is installed whether it is getting 'ping' from the remote system.

Give the ping command in the following way:

  • If the Endpoint Security site has been configured on IP Address
    ping < IP address of Admin Server>
    Example: ping 192.168.100.34

  • If the Endpoint Security site has been configured on Domain Name
    ping < domain name of Admin Server >
    Example: ping quickheal.admin.com

  • In case of Domain-based network, if the Endpoint Security site is configured on Domain Name and DNS is not properly configured, the remote system will not be able to ping the Endpoint Security Server system. To solve this problem, Administrator needs to configure proper DNS settings on the remote system.
  • We recommend you to configure Endpoint Security Site on the IP Address rather to configure it on the domain name.
  • Check the Installer logs (Go to Client > Client Settings > View Status > View Installer logs). Here, you will get the exact reason about why Quick Heal is not getting installed on the remote system.
  • If any Firewall is running, check whether the URL or Port through which the build is getting downloaded is blocked.
  • Ensure there is sufficient disk space on the Remote System to download and install Quick Heal Endpoint Security, if the installer log shows installation failed due to insufficient disk space.
  • Verify if the Agent Server service is started on the Endpoint Security server.
    1. Go to Start > Run.
    2. Type Services.msc.
    3. Click OK.
    4. in Services, check the Agent Server Service status is 'Started'.
  • If Internet Connection is configured using Proxy Server, it may not be able to resolve the name or IP of the Endpoint Security server. In this case, bypass the Proxy Settings for the Endpoint Security site.
  • Subnet Mask of the Remote System should be as per the IP class assigned to the Endpoint Security server system.

Why does the Endpoint Security site show Quick Heal Client offline although Client Agent is installed successfully?

Possible causes are listed as follows:

  • The Client Agent is not able to connect to the Agent Server OR vice versa.

This problem can be resolved in any of the following ways:

  • Check if both the Endpoint Security server and Remote System are able to communicate with each other on the configured port. To check, follow these steps:

    • Verify if the Agent Server Service is started on the Endpoint Security server.
      1. Go to Start > Run.
      2. Type Services.msc.
      3. Click OK.
      4. In Services, check the Agent Server Service status is 'Started'.
    • Verify if the Client Agent Service is started on Remote System.
      1. Go to Start > Run.
      2. Type Services.msc.
      3. Click OK.
      4. In Services, check the Client Agent Service status is 'Started'.
    • Telnet < IP Address of Endpoint Security Server > < Agent Server Port >
      Suppose IP address of Endpoint Security Server is 192.168.100.34 and 5044 is the port on which Agent Server is listening. Then execute the following command on remote system.

      Telnet 192.168.100.34 5044

  • If you receive any response from the Agent Server, check whether the Agent Server is able to communicate with the Client Agent.

    • Telnet < IP address of Remote System > < Client Agent Port >

      Suppose IP address of the remote system is 192.168.100.66 and 62115 is the port on which the Client Agent is listening, then execute the following command on Endpoint Security Server.

      Telnet 192.168.100.66 62115

 

  • Please check if any Firewall service is installed on the system. If so, then the Firewall can block the communication between Agent Server and Client Agent.

The Endpoint Security site does not open if proxy is configured in Internet Explorer? But if we remove the proxy settings from Internet Explorer, the site opens. What could be the reason behind this?

Possible causes are listed as follows:

  • When proxy setting has been configured in Internet Explorer, it tries to resolve the Endpoint Security site via Proxy Server and if Proxy Server is not able to resolve it, the site does not open.


This problem can be resolved in any of the following ways:


Check the Proxy Server configuration of the remote system. Proxy Server should be able to resolve the IP address or domain name on which the Endpoint Security site is configured.


Follow these steps to bypass Proxy Server while opening the Endpoint Security site:


  1. Open Internet Explorer.
  2. Go to Tools > Internet Options > Connection Tab > Click on LAN Settings.
  3. Click the Advance button.
  4. In the Exceptions section, type the address of the Endpoint Security website along with the Port number.
  5. Click OK.

Why is Update Manager not able to download the updates while the Clients of Endpoint Security are able to download the updates?

Taking the latest updates regularly ensures complete computer data security. If the Update Manager is not able to take the updates, the following may be its causes:

  • Firewall is blocking the Update Manager Application.
  • Firewall is blocking the Quick Heal URL.
  • Firewall is blocking the extensions like .bin or .dat.
  • Update Manager Connection is configured through Proxy Server.

This problem can be resolved in any of the following ways:


    1. Check the Firewall settings and allow Update Manager, the Quick Heal URL and extensions like .bin or .dat if they are blocked.
    2. Clear the cache of the Proxy Server

Internet Explorer is not being able to open the Quick Heal Endpoint Security site. What could be the reason behind this?

Possible causes are listed as follows:

  • Web Server Service is not running.
  • Endpoint Security Site or its port is blocked by Firewall.
  • Request is going through Proxy Server but the Proxy Server is not able to resolve.

This problem can be resolved in any of the following ways:


  • If the Endpoint Security server is configured using IIS Server, check if the IIS Admin Service is running. Also check whether the Endpoint Security website is running in IIS.
  • If the Endpoint Security server is configured using Apache HTTP Server, check if the Apache Service is running.

    1. Go to Start > Run.
    2. Type Services.msc.
    3. Click OK.
    4. In Services, check the Apache2 Service status is 'Started'.
  • Check for if UTM (Unified Threat Management) device in the network is blocking the port. If so, open the port of the Endpoint Security server.

How can I upgrade Quick Heal Endpoint Security?

To know about how to upgrade your existing Quick Heal Endpoint Security 5.3, visit the following link Quick Heal Endpoint Security 5.3.


Share your feedback or suggestions for this website at webmaster@quickheal.com