Seqrite Endpoint Security 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.

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

1. Agent Server: runs on server where Seqrite EPS is installed.
2. Client Agent: runs on workstations
   • Default Port of Agent Server: 5047 (Administrator can change this default port)
   • Default Port of Client Agent: 62118 (If this port is used by any other application, Client Agent configures itself to some other port which is free. (E.g. 62118, 62119 etc.)

Agent Server is a service that runs on Seqrite EPS 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.

This feature of network security runs on every Seqrite EPS 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.

Yes. Seqrite provides a tool called Update Manager integrated with Seqrite Endpoint Security that is centrally deployed to help download the latest updates from the server of Seqrite. This tool constantly monitors whether new updates are available from Seqrite 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.

Understanding the needs of today’s IT security management, Seqrite 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

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 seqrite.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 Seqrite 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 Seqrite 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'.

• 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'.

• 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.

 

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 5047 is the port on which Agent Server is listening. Then execute the following command on remote system.
    Telnet 192.168.100.34 5047

• 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 62118 is the port on which the Client Agent is listening, then execute the following command on Endpoint Security Server.
  Telnet 192.168.100.66 62118

• 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.

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.

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 Seqrite 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 Seqrite URL and extensions like .bin  or .dat  if they are blocked.
2. Clear the cache of the Proxy Server.

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 TERMINATOR (UTM) device in the network is blocking the port. If so, open the port of the Endpoint Security server.

To know about how to upgrade your existing Seqrite Endpoint Security, visit the following link Seqrite Endpoint Security

Microsoft has recommended configuring trusted zones for security solutions, which if not done correctly can give rise to issues such as system getting hanged, slow or non-responsive. These configurations involve excluding certain directories, and file names from file-level scanners.

Note: After you have installed Seqrite Endpoint Security on a system running MS Exchange, as a first step you must follow the guidelines and instructions listed below to exclude files and folders recommended by Microsoft.

Steps to follow:

1. Log on to Seqrite Endpoint Security web console; click the Settings tab.
2. On the Settings screen, click Scan Settings.
3. Under Exclude File and Folders, click Add.
4. On the Exclude Item screen, select either of the following (Exclude Folder or Exclude File):
   1. Exclude Folder(if you select this, follow the steps below)
      1. Type the folder path in the Enter folder path.
   2. Exclude File(if you select this, follow the step below)
      1. Type the folder path in the Enter folder path.
5. Under Exclude from, select Known Virus Detection.
6. Click OK to save your settings.

Note:

1. The steps mentioned above are applicable to default policy of Seqrite Endpoint Security.
2. If your system on which Microsoft Exchange Server is installed, is in a different group that has some different policy applied, then you need to configure the above mentioned settings for that policy. You can do so from Client Settings > Manage Policies section.

The following list/locations is recommended by Microsoft for Microsoft Exchange server:

Microsoft Exchange Server:

Cluster:

%systemroot%\Cluster\*.*

IIS server:

%systemroot%\system32\inetsrv\*.*

Note:

1. %SYSTEMROOT% specifies the location of the Windows folder i.e C:\WINDOWS e.g. %SYSTEMROOT%\System32 = C:\WINDOWS\System32
2. %ProgramFiles% specifies the location of the Program Files folder i.e C:\Program Files.
3. %SYSTEMDRIVE%\ specifies the location of Systems root drive i.e. C:\
4. *.* specifies include Sub Folder.
5. Exclude all files having extensions '.edb,.stm,.chk,.log,.dat,.stf' from '%ProgramFiles%\Exchsrvr\MDBDATA\' location.

For more details, please go through below mentioned links to see complete list of exclusions provided by Microsoft for MS Exchange.

1. For Microsoft Exchange 2013, click here to see the complete list of exclusions.
2. For Microsoft Exchange 2010, click here to see the complete list of exclusions.
3. For Microsoft Exchange 2007, click here to see the complete list of exclusions.

The following antivirus solutions are detected for uninstallation while Seqrite Endpoint Security is being installed:

• 360 Internet Security 2014
• 360 Total Security 2014
• Avast Antivirus 2014/Business Security Client 2015.10.2.2505
• Avast Free Antivirus
• Avast Home Edition
• AVG
• AVG 2012/2014/Internet Security Business Edition Client 2016.7.7227
• AVG 8
• AVG Antivirus 2011
• AVG Antivirus 2012
• Avira Antivirus 2014
• Avira Professional Security
• BitDefender 2011
• Bitdefender 2012/2014
• BitDefender AntiVirus
• BitDefender AntiVirus 2008
• BitDefender AntiVirus Plus
• Bitdefender Endpoint Security Tools Client 6.2.3.569, 6.2.7.696
• Bitdefender Free Antivirus 2014
• BitDefender Internet Security
• BitDefender Internet Security 2008
• BitDefender Internet Security 2010
• BitDefender Total Security 2008
• BitDefender Total Security 2010
• Bullguard Antivirus 2014
• E-Scan Internet Security
• eScan Anti-Virus 10.0/11.0/14.0
• eScan Corporate for Windows Client 14.0.1400.1789
• Escan IS Ver11.0/TS Ver14.0
• Escan Total Security 2014
• Eset NOD 32 Antivirus 2014
• Eset Endpoint Security Client 6.2.2033.0
• Eset NOD 32 Smart Security 2014
• ESet NOD32 Antivirus
• ESet NOD32 Antivirus 9.0.31.0
• ESet Smart Security
• ESet Smart Security 2012
• F-Secure Anti-Virus 2011
• F-Secure Antivirus 2012/2014
• F-Secure Client Security 12 premium
• F-Secure Internet Security 2011
• G Data Antivirus 2014
• G Data Internet Security 2014
• G Data Total Security 2014
• K7 Antivirus Plus 2014
• K7 Antivirus Plus Ver 11.0/14.0
• K7 Antivirus Premium 2014
• K7 AV Premium/TS 2014
• K7 Endpoint Security Client 13.2.0028, 14.2.0084
• K7 Total Security
• K7 Total Security 2014
• K7 Ultimate Security 2014
• Kasperskry Antivirus 2014
• Kaspersky AntiVirus
• Kaspersky AntiVirus 2009
• Kaspersky AntiVirus 2010
• Kaspersky Antivirus 2011
• Kaspersky Antivirus 2012
• Kaspersky Antivirus 2014
• Kaspersky AntiVirus 4.5
• Kaspersky Antivirus TS/IS/AV 16.0.0.614
• Kaspersky Endpoint Security 10.1.0 for Windows Client 10.1.0.867
• Kaspersky Endpoint Security 10.2.2 for Windows Client 10.2.2.10535
• Kaspersky Internet Security
• Kaspersky Internet Security 2009
• Kaspersky Internet Security 2010
• Kaspersky Internet Security 2011
• Kaspersky Pure 2.0
• Kaspersky PURE 2011
• Kaspersky PURE 3.0
• Kaspersky PURE 3.0 2014
• Kaspersky PURE 3.0 2014
• Kaspersky Small Office Security
• McAfee 2011/2014
• McAfee AntiVirus
• McAfee SecurityCenter
• McAfee VirusScan Enterprise Client 8.8.0.1385
• Microsoft Security Essentials
• Microsoft System Center Endpoint Protection Client 4.7.0213.0
• Norton 360
• Norton 360 Ver 4.0/5.0/21.0
• Norton AntiVirus
• Norton AntiVirus 2008
• Norton AntiVirus 2009/2011
• Norton Antivirus 2014
• Norton AV 2009/2011/2012/2014/2015
• Norton Internet Security
• Norton Internet Security 2008
• Norton Internet Security 2009/2011
• Norton Internet Security 2014
• NP Total Internet Security 2014
• Norton Security 22.5.4.24
• Net Protector 2016.0.0.0
• Panda AntiVirus
• Panda Antivirus 2011/2012/2014
• Panda Cloud Antivirus 2014
• Panda Cloud Antivirus Pro 2014
• Panda Endpoint Protection Client 7.20.0, 7.3.30, 7.40.1
• Panda Global Protection 2011/2012
• Panda Global Protection 2014
• Panda Internet Security 2011/2012
• Sophos Anti-Virus 10.0.3
• Sophos AntiVirus
• Sophos AntiVirus 2011
• Sophos Endpoint Security and Control Client 10.3
• symantec Endpoint Protection 11
• symantec Endpoint Protection 12
• Symantec Endpoint Protection 12.1 Client 12.1.4013.4013
• Symantec Endpoint Protection 12.1.5 Client 12.1.5337.5000
• Symantec Endpoint Protection 12.1.6 Client 12.1.6168.6000
• Symantec Endpoint Protection 12.1.6 RU6 MP1 Client 12.1.6306.6100
• Symantec Endpoint Protection 12.1.6 RU6 MP1 Client 12.1.6318.6100
• Symantec Endpoint Protection 12.1.6 RU6 MP4 Client 12.1.6867.6400
• Trend Micro
• Trend Micro 2008
• Trend Micro AntiVirus
• Trend Micro Antivirus 2011/2012/2014
• Trend Micro OfficeScan Client 11.0.1028, 10.5.1083
• Trend Micro PC-cillin Internet Security
• TrustPort Antivirus 2014
• Vipre Antivirus 2014
• Vipre Internet Security 2014
• Webroot SecureAnywhere
• WinCleaner AntiVirus
• Windows Live OneCare

To enable Microsoft IIS on Windows Server 2008 and 2008 R2

1. Click Start -> click on Control Panel -> click on Programs -> click on Programs and Features -> click Turn Windows Features On or Off. If you are prompted for an administrator password or confirmation, type the password or provide the confirmation.
2. The Windows Server Manager console will open. Now click on Add Roles
3. In the Role Services window select Web Server (IIS) and click on Next
4. In the list of Windows features, click the plus sign (+) next to Internet Information Services, click the plus sign (+) next to Web Management Tools and click on IIS Management Console.
5. In the list of Windows features, click the plus sign (+) next to World Wide Web Services, click the plus sign (+) next to Application Development Features and then select the following:
   

   SELECT THIS	THEN SELECT THIS
   Application Development	ASP.NET 4.0 and Later CGI .NET Extensibility ISAPI Extensions ISAPI Filters
   Common HTTP Features	Default Document Static Content
   Management Tools	IIS Management Console

6. Click on Next and click on Install. Wait for a few minutes till you see the Installation Succeeded window and then click on Close.

To enable Microsoft IIS on Windows Server 2012 and 2012 R2

1. Open Server Manager
2. Under the Manage menu, select Add Roles and Features
3. Select Role-based or Feature-based Installation
4. Select the appropriate server (local is selected by default)
5. In the Select Server Roles wizard, click on Web Server (IIS) and click Next
6. No additional features are needed for IIS in the Select Features wizard and click Next
7. In the Select Role Services wizard and in the list of Windows features select the following components:
   

   SELECT THIS	THEN SELECT THIS
   Application Development	ASP.NET 4.0 and Later CGI .NET Extensibility ISAPI Extensions ISAPI Filters
   Common HTTP Features	Default Document Static Content
   Management Tools	IIS Management Console

8. Click on Next and click on Install. Wait for a few minutes till you see the Installation Succeeded window and then click on Close.

To enable Microsoft IIS on Windows Vista / 7 / 8 / 8.1 / 10

1. Click Start -> click on Control Panel -> click on Programs and Features -> click Turn Windows Features On or Off. If you are prompted for an administrator password or confirmation, type the password or provide the confirmation.
2. In the list of Windows features, click the plus sign (+) next to Internet Information Services, click the plus sign (+) next to Web Management Tools and click IIS Management Console.
3. In the list of Windows features, click the plus sign (+) next to World Wide Web Services, click the plus sign (+) next to Application Development Features and then select the following:
   

   SELECT THIS	THEN SELECT THIS
   Web Management Tools	IIS Management Console
   Application Development	ASP.NET 4.0 and Later CGI .NET Extensibility ISAPI Extensions ISAPI Filters
   Common HTTP Features	Default Document Static Content

To enable Microsoft IIS on Windows Server 2003 and Windows XP

1. Click Start -> click on Settings -> click on Control Panel
2. In the Control Panel, double-click on Add or Remove Programs
3. In the Add or Remove Programs dialog box, click on Add/Remove Windows Components from the left pane
4. On the Windows Components page, in the Components box, click on Application Server/Internet Information Services (IIS) and then click on Next
5. Wait for the installation to finish and then close the wizard

Note: For IIS installation on Windows Server 2003 and Windows XP you may also need the OS installation CD.