deploymentStatus

INTEGER { ok(0), info(1), warning(2), critical(3) }

.1.3.6.1.4.1.23668.1093.1.1.1

Deployment status. The status can be one of the following:

• Info. License is not valid for N devices anymore.
• Warning. One of the following:

  There are M devices with Kaspersky applications installed on a total of N devices in Administration Server groups (N > M).

  License L expires on N devices in M days.

  Task T of installing applications has been successfully finished on N devices, reboot is needed for M devices.

• Critical. License expired for N devices.
• OK. None of the above.

noAntivirusSoftware

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.1.2.1

The reason deploymentStatus shows that the Administration Server group contains too many devices without managed applications.

Value equals 1 in case a few devices were found without managed applications, and 0 otherwise.

remoteInstallTaskFailed

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.1.2.2

The reason deploymentStatus shows that the task of the remote installation has failed on some devices. The number of those devices can be obtained via hostsRemoteInstallFailed.

licenceExpiring

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.1.2.3

The reason deploymentStatus shows that there are some devices with a license expiring in the next 7 days. The number of those devices can be obtained via hostsLicenseExpiring.

licenceExpired

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.1.2.4

The reason deploymentStatus shows that there are some devices with an expired license. You can obtain the number of those devices via hostsLicenseExpired.

hostsInGroups

Counter32

.1.3.6.1.4.1.23668.1093.1.1.3

Number of devices in Administration Server groups.

hostsWithAntivirus

Counter32

.1.3.6.1.4.1.23668.1093.1.1.4

Number of devices in Administration Server groups with managed applications installed.

hostsRemoteInstallFailed

Counter32

.1.3.6.1.4.1.23668.1093.1.1.5

Number of devices on which the task of the remote installation failed.

licenceExpiringSerial

OCTET STRING

.1.3.6.1.4.1.23668.1093.1.1.6

ID of a license key that expires soon (in less than 7 days).

licenceExpiredSerial

OCTET STRING

.1.3.6.1.4.1.23668.1093.1.1.7

ID of the expired license key.

licenceExpiringDays

Unsigned32

.1.3.6.1.4.1.23668.1093.1.1.8

Number of days before the license expires. For this parameter, the license period is considered expired if there are less than 7 days left until the expiration date.

If there are more than 7 days left until the expiration date, the value is 0.

hostsLicenceExpiring

Counter32

.1.3.6.1.4.1.23668.1093.1.1.9

Number of devices with a license that expires soon (in less than 7 days).

hostsLicenceExpired

Counter32

.1.3.6.1.4.1.23668.1093.1.1.10

Number of devices with an expired license.

updatesStatus

INTEGER { ok(0), info(1), warning(2), critical(3) }

.1.3.6.1.4.1.23668.1093.1.2.1

Current status of Anti-virus bases update. The status can be one of the following:

• Info. Anti-virus bases on Administration Server or on the devices have not been updated in more than 1 day, and less than 1 day has passed since application installation.
• Warning. Anti-virus bases on Administration Server or on the devices have not been updated in more than 3 days. This value can be changed in group settings.
• Critical. Anti-virus bases on Administration Server or on the devices have not been updated in more than 7 days. This value can be changed in group settings.
• OK. None of the above.

serverNotUpdated

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.2.2.1

This reason shows that Administration Server was not updated for a log time. The amount of time considered long is specified in updatesStatus.

notUpdatedHosts

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.2.2.2

This reason shows that some devices were not updated for a long time (by default, 7 days or more for Critical and 3 days for Warning). You can obtain the number of those devices via hostsNotUpdated.

lastServerUpdateTime

OCTET STRING

.1.3.6.1.4.1.23668.1093.1.2.3

Last time when Anti-virus bases were updated on Administration Server.

hostsNotUpdated

Counter32

.1.3.6.1.4.1.23668.1093.1.2.4

Number of devices containing Anti-virus bases that are not updated for a long time (by default, 7 days or more for Critical and 3 days for Warning). If there are devices with the Critical update status, only these devices are counted. You can obtain the update status via updatesStatus.

protectionStatus

INTEGER { ok(0), warning(2), critical(3) }

.1.3.6.1.4.1.23668.1093.1.3.1

Status of real-time protection. One of the following:

• Warning. One of the following:

  A security breach is detected on a device that belongs to the Administration Server group.

  Encryption errors made some devices change protection status.

  Full scan has not been performed for a long time.

• Critical. Anti-virus protection is not working on some devices in Administration Server groups.
• OK. None of the above.

antivirusNotRunning

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.3.2.1

This reason shows that a security application is not running on some devices. You can obtain the number of those devices via hostsAntivirusNotRunning.

realtimeNotRunning

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.3.2.2

This reason shows that real-time protection is not running on some devices. You can obtain the number of those devices via hostsRealtimeNotRunning.

notCuredFound

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.3.2.4

This reason shows that there are devices containing non-disinfected objects. You can obtain the number of those devices via hostsNotCuredObject.

tooManyThreats

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.3.2.5

This reason shows that there are threats found on some devices. You can obtain the number of those devices via hostsTooManyThreats.

virusOutbreak

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.3.2.6

This reason shows the virus outbreak status of the system.

Value equals 1 if a certain amount of viruses were found during a certain amount of time, and 0 otherwise. Amount of viruses and amount of time are specified on Administration Server, by using the Virus attack settings.

hostsAntivirusNotRunning

Counter32

.1.3.6.1.4.1.23668.1093.1.3.3

Number of devices with security applications not running.

hostsRealtimeNotRunning

Counter32

.1.3.6.1.4.1.23668.1093.1.3.4

Number of devices with real-time protection not running.

hostsRealtimeLevelChanged

Counter32

.1.3.6.1.4.1.23668.1093.1.3.5

Number of devices with real-time protection level not acceptable.

hostsNotCuredObject

Counter32

.1.3.6.1.4.1.23668.1093.1.3.6

Number of devices containing non-disinfected objects.

hostsTooManyThreats

Counter32

.1.3.6.1.4.1.23668.1093.1.3.7

Number of devices containing threats.

fullscanStatus

INTEGER { ok(0), info(1), warning(2), critical(3) }

.1.3.6.1.4.1.23668.1093.1.4.1

Status of Anti-virus full scan. One of the following:

• Info. Less 7 days have passed since the moment of application installation.
• Warning. Anti-virus full scan hasn't been performed for more than 7 days since the moment of application installation.
• Critical. Anti-virus full scan hasn't been performed for more than 14 days since the moment of application installation.
• OK. None of the above.

notScannedLately

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.4.2.1

This reason shows that some devices have not been scanned for a certain amount of time. You can obtain the number of those devices via hostsNotScannedLately. The amount of time is specified in fullScanStatus.

hostsNotScannedLately

Counter32

.1.3.6.1.4.1.23668.1093.1.4.3

Number of devices that have not been scanned for a certain amount of time. The amount of time is specified in fullScanStatus.

logicalNetworkStatus

INTEGER { ok(0), warning(1), critical(2) }

.1.3.6.1.4.1.23668.1093.1.5.1

Status of the logical network of Administration Server. One of the following:

• Warning. If there are devices with a warning status that can't be accessed or if there are devices that do not belong to any Administration Server group.
• Critical. If there are devices whose control has been lost by Administration Server, or if there are devices with a critical status and that cannot be accessed.
• OK. None of the above.

notConnectedLongTime

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.5.2.1

This reason shows that some devices have not been connected to Administration Server for a long time (7 days or more for a device of Warning status and 4 days for a device of Critical status). You can obtain the number of those devices via hostsNotConnectedLongTime.

controlLost

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.5.2.2

This reason shows that there are devices whose control has been lost by Administration Server. You can obtain the number of those devices via hostsControlLost.

hostsFound

Counter32

.1.3.6.1.4.1.23668.1093.1.5.3

Number of devices found by Administration Server that do not belong to any Administration Server groups.

groupsCount

Counter32

.1.3.6.1.4.1.23668.1093.1.5.4

Number of groups at Administration Server.

hostsNotConnectedLongTime

Counter32

.1.3.6.1.4.1.23668.1093.1.5.5

Number of devices that have not been connected to Administration Server for a long time. The amount of time considered long is specified in notConnectedLongTime.

hostsControlLost

Counter32

.1.3.6.1.4.1.23668.1093.1.5.6

Number of devices that are not controlled by Administration Server.

eventsStatus

INTEGER { ok(0), warning(1), critical(2) }

.1.3.6.1.4.1.23668.1093.1.6.1

Status of events subsystem. One of the following:

• Warning. One of the following:

  Devices of Administration Server group have not been searching for Windows updates for a long time.

  There are devices with status problems.

• Critical. One of the following:

  There is an event of "Critical" importance on at least one device.

  There is an event of "Error" importance on at least one device.

  There is an event of task completing unsuccessfully on at least one device.

  Devices of Administration Server group have not been searching for Windows updates for a long time.

  There are devices with status problems.

• OK. None of the above.

criticalEventOccured

INTEGER { off(0), on(1) }

.1.3.6.1.4.1.23668.1093.1.6.2.1

The reason eventsStatus shows that there are some critical events on Administration Server. You can obtain the number of those events via criticalEventsCount.

Value equals 1 if there is at least one critical event on any device, and 0 otherwise.

criticalEventsCount

Counter32

.1.3.6.1.4.1.23668.1093.1.6.3

Number of critical events on Administration Server.