Detailed Repository Configuration |
The section provides you with options to configure revision for each repository product separately. To edit repository configuration 1.Select the item on the main menu of the Control Center. 2.In the opened window, in the subsection of the control menu, select the product you want to edit. 3.Configure all necessary repository settings for the selected product, described below. 4.The following options to manage the whole repository product are available on the toolbar: •—delete the product from repository completely. At this, all revisions of the product will be deleted and update of the product from GUS will be disabled. The button is available if the product has not yet been deleted from the repository. After the product has been deleted, the button changes its name to .
•—restore the product in the repository if it was deleted earlier using the button. At this, update of the product from GUS will be enabled. The most fresh revision of the product available on GUS will be downloaded to the repository. Please note the possible data amount to download. You can configure updates downloading in the General repository configuration section. After the product has been restored, the button changes its name to . •—save all your changes. At that, the current version of the repository is reloaded from the disk (see also Repository state). On the tab, you can view information on all revisions available on the Server for this product. To delete separate revisions, set the flags next to these revisions and click on the toolbar.
The table of revisions contains the following columns:
The ability to downgrade products installed at stations to previous versions is determined by the following provisions: •Databases always can be downgraded to a previous version. •To downgrade the Agent, this option must be allowed in the Update restrictions section. •You cannot downgrade the Agent to a previous version if revision installed at station is marked as .
On the tab, you can configure parameters for updating the Server repository from GUS: •The field specifies the number of product revisions temporary stored on disk not including revisions which are marked at least in one column of the tab. When a new revision is received and the number of temporary stored revisions already reached the specified allowed value, the oldest temporary stored revision is removed. Revisions marked as , , and are not automatically removed and are not taken into account when calculating temporary stored revisions. This setting will be overwritten with a single value for all products if the General Repository Configuration section is edited. •Set the flag to disable receiving updates for this product from the GUS servers. Agents will be updated to the current revision on the Server (or according to the procedure used to select the distributed revision). For some products, the following settings are also available: •Set the flag to receive updates from GUS only for the file listed below. •Set the flag to disable updating from GUS only for the file listed below. Files can be specified in the format of regular expressions. If both flags are set, files for an update are selected as follows: 1.From the full list of product files only those are selected that are specified in the lists. 2.From the selection at step 1, files specified in the lists are removed. 3.Files resulting from the selection at step 2 are updated from GUS. Notifications On the tab, you can configure notifications on repository updates: •Set the flag to disable notifications on events of the files listed below. •Set the flag to enable notifications on events of the files listed below. Files can be specified in the format of regular expressions. If exceptions list are not specified, all notifications enabled on the Notifications configuration page are sent. Parameters of notifications on repository updates are configured in the Notifications configuration page, in the section. On the tab, you can delay distribution of updates on stations for the specified period of time. A delayed revision is considered frozen. The option to delay updates is useful when you need to temporarily cancel distribution of last product revision on all stations of the anti-virus network, e.g., if you want to perform preliminary testing of this revision on a limited number of stations. To use delayed updates functional 1.For the product, update of which you want to freeze, configure delayed updates as described below. 2.To disable distribution of the last revision, set one of the previous revisions as a current on the Revision list tab. 3.For the group of stations that will receive the last revision, set the flag on the Update Restrictions for Workstations section. Other workstations will receive the revision which you selected as current at step 2. 4.The next downloaded from the GUS revision which is satisfying the conditions specified for the option, will be frozen and delayed for the time period specified in the list. 1.Set the flag to temporarily disable downloading updates from GUS servers for this product. 2.In the drop-down list, select the time period to delay downloading of updates starting from the moment of their receive from the GUS servers. 3.If required, set the flag to delay distribution of updates that contain files which corresponds to the masks specified below. Masks are specified in the format of regular expressions. If the flag is cleared, all updates from the GUS are frozen. To disable the frozen state •On the tab, click to disable the frozen state for the product and add the revision to the list of revisions distributed to stations according to the general procedure. •On the tab, click to disable the frozen state for the product and forbid the revision. Updating from the GUS is restored. Unfrozen revision will be removed from the list of product revisions. After the next revision is received, the unfrozen revision will be removed from the disk. •When the time specified in the list is out, the revision becomes unfrozen and is included to the list of revisions distributed to stations according to the general procedure. You can manage frozen revisions for all products on the Delayed Updates page. |