Comodo Internet Security Local Update Server

This manual will detail the process of raising your local Comodo update server on Windows without using any paid components. Unlike Comodo Offline Updater and analogs, there is no need to configure a proxy on the client side.

Requirements:

• OS: Windows 7 SP1 and above or Windows Server 2008 and above (for 7 and 2008 you need WMF 3.0 or WMF 4.0 )
• URL Rewrite 2.1 module
• Script download updates on PowerShell
• 7-zip

Windows 7 SP1 Pro x64 (IIS 6.7) will be used as a server. For newer OS installation and configuration is similar.
')

1) Installing IIS

"Enable or disable Windows components" in the "Add or Remove Programs" section, check "IIS" for installation. Automatically marked components are enough.

2) Script and logic for downloading updates

The script is written in PowerShell v4, so to work correctly on Windows 7 you need to update WMF4.0. Reboot after installation is required. 7-Zip is also required for unpacking. By itself, to run a script, you need to translate the PS Execution Policy to Unrestricted. This is done with the Set-ExecutionPolicy Unrestricted command.

Comodo updates are divided into 2 parts: the base and the update of the program itself. Files of both parts can be packaged or not. I recommend using packaged ones, since they occupy much less disk space - 290MB versus 635MB only in databases.


The script uses the following user variables:

$ 7z - Path to 7z.exe
$ downloadpath - The path for downloading, folders are created automatically. In this example, “C: \ inetpub \ wwwroot”
$ serverurl - Comodo server to download from
$ inis - Update branch, more on that below.
$ proto - the version of the recognizer
$ xx - Bit rate for download ("x32", "x64"), you can specify only one
$ cispacked - Downloading packaged (* .7z) updates or not. Possible values: $ true or $ false
$ avpacked - Download packaged (* .cav.z) databases. Possible values: $ true or $ false
$ release_notes - Downloading Release Notes. Possible values: $ true or $ false.

Regarding the program's update branches: up to version 8.2.0.4508 inclusive, inis_4010 is used, then any existing above, for example 4080. That is, if you need to update clients of versions 8 and below, then you need to deflate inis_4010 ($ inis = "4010", $ proto = "6") and current ($ inis = "4080", $ proto = "10"). Thus, I managed to upgrade from v6 to the current v10 with two reboots without any problems.

To facilitate administration, the script has 3 startup parameters:

cis - download program updates
av - database download
av-clean - removal of obsolete databases
It remains only to add tasks with a specified frequency in the Task Scheduler.

3) Configure IIS

In this example, the Default Web Site, created automatically, will be used.
For debugging, I recommend enabling the "Browse Directory". To do this, select the desired site, go to the "Browse Directory" menu and click "Enable" on the right side.

To download updates correctly, you need to configure MIME Types: in the corresponding menu item, add file extensions and assign application / octet-stream type to them.

4) Rewrite module

Installing the URL Rewrite 2.1 module is trivial. This module is required to redirect to the desired inis_ branch.
After installation, you must re-open IIS Manager, otherwise the corresponding menu item will not be visible. To configure, go to the “URL Redefinition” item and add an empty rule for incoming traffic with the following content:

Name: arbitrary
Template:
(cis / download / updates / release / inis) _ [0-9] * / (. *)
Override URL:
{R: 1} _4080 / {R: 2}

In the last address, specify those numbers that are specified in the script in the $ inis variable.


If you need to update outdated versions, you need to create another rule above.

Name: arbitrary
Template:
(cis / download / updates / release / inis) _ [0-9] * / (. *)
Conditions (match with any of the elements):
{REQUEST_URI},. * / Inis_40 [0-1] 0 /.* and {REQUEST_URI},. * / Inis_ [1-3] [0-9] * /. *
Override URL:
{R: 1} _4010 / {R: 2}
Stop processing subsequent rules


This completes the server side setup.

5) Setting up clients on a local server

The easiest way to do this manually or through the registry. In the registry, the list of update servers is located at HKEY_LOCAL_MACHINE \ SOFTWARE \ COMODO \ CIS \ Options in the UpdateURL parameter.
For example, this option looks like when setting up the av.local server and disabling the default server: av.local ! Https: //download.comodo.com/

As a result, you get a local Comodo update server and significantly reduce the load on the external channel.