Windows Agent

<< Click to Display Table of Contents >>

RayManageSoft Unified Endpoint Manager > 3.1 > User Guide > Appendix II: Logging on Managed Devices 

Windows Agent

The following chapter describes how logging works for the Windows agent.

 

The significant registry values for logging are as follows:

 

LogFile - The filename in which the log is saved.

LogLevel - The categories of information that are to be logged. Set this value to A-z in order to log everything.

LogModules - The modules through which RMS UEM AppCenter events are logged.

LogMsgCatPath - The location of the messages catalog to use for log message translation (only 8 bit locales are supported).

LogFileSize - The maximum size for the log file. When the file reaches this size, it will be moved to LogFileOld and a new file will be created.

LogFileOld - The name under which the old log files are stored.

 

Feature

Registry Key

Application usage agent

HKLM\SOFTWARE\ManageSoft corp\ManageSoft\Usage Agent
\CurrentVersion

Data reporting agent

HKLM\SOFTWARE\ManageSoft corp\ManageSoft\Uploader
\CurrentVersion

Installation agent

HKLM\SOFTWARE\ManageSoft corp\ManageSoft\Launcher
\CurrentVersion

Inventory agent

HKLM\SOFTWARE\ManageSoft corp\ManageSoft\Tracker
\CurrentVersion

RMS UEM AppCenter

HKLM\SOFTWARE\ManageSoft corp\ManageSoft\Selector
\CurrentVersion

Policy agent

HKLM\SOFTWARE\ManageSoft corp\ManageSoft\Policy Client
\CurrentVersion

Scheduling agent

HKLM\SOFTWARE\ManageSoft corp\ManageSoft\Schedule Agent
\CurrrentVersion

 

Logging Types and Sublevels

The following tables describe each of the logging types and sublevels available. For example, in order to request icon logging, the LogLevel setting should be configured as G7.

 

It is possible to combine different sublevels. The following ways of combining exist:

 

References to different logging types can be separated with semi-colons. It is not possible to include more than one reference of the same logging type to the list. For example:

oG0;N4 - This is a valid combination.

oG0;N4;G1 - This is invalid as there are two references of the G logging type.

References to different sublevels can be separated by commata.  For example: G0, 5, 9.

A range of sublevels (within the same type) can be expressed with a hyphen. For example: G1-3, 9;N4;A.

 

General Logging - G

Sublevel

Description

0

Miscellaneous general information

1

Base URL information

2

Versioning

3

Digital Signatures information

4

Virus Checking

5

Staging of downloaded files

6

Status information

7

Icon information

8

Auto

9

File / Directory information

 

User Interface Logging - U

Sublevel

Description

0

Miscellaneous user interface information

 

Network Logging - N

Sublevel

Description

0

Miscellaneous network information

1

Dialup information

 

Verification Logging - V

Sublevel

Description

0

Miscellaneous verification information

 

Security Logging - S

Sublevel

Description

0

Miscellaneous security information

1

Security matching (such as trusted URL location)

 

Preference Logging - P

Sublevel

Description

0

Miscellaneous preference  information

1

Retrieval (Get)

 

Schedule Logging - A

Sublevel

Description

0

Miscellaneous schedule information

 

Callout Logging -C

Sublevel

Description

0

Internal callout information

1

External callout information