How does the Basic Inventory data gathering process work, and when is the data sent to the server or not?

book

Article ID: 179851

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

 

Resolution

Question

How does the Basic Inventory data gathering process work, and when is the data sent to the server or not?

Answer

The Basic Inventory dll gathers data from the computer in the following order (based on BasicInventory.cpp from NS 6.0.6074):

  • CEClientAgent
  • CEIdentification
  • CEIdIP
  • AeXSMSClientProp
  • CELocationInfo
  • CEPrimaryUser
  • CEClientConnectivity
  • If the machine runs Windows NT or above (VER_PLATFORM_WIN32_NT)
    • CEIdRoles
    • AeXNTServicesProp

Once the data is gathered we save the information to file and load it in an xml document. We then ensure that the Basic Inventory generated contains the "AeX AC Identification" class before we remove data that changes often and run a MD5 hash on the xml.

The following data fields  are cleared:

  • Attribute ( L"c8",  L"" ); // LastLogonUser
  • Attribute ( L"c9",  L"" ); // LastLogonDomain
  • Attribute ( L"c10", L"" ); // Client Date
  • Attribute ( L"c16", L"" ); // User primary language
  • Attribute ( L"c17", L"" ); // User sub language

Once this is done we compare the existing hash (stored in the registry) with the new hash. If the hash matches we do not send the Basic Inventory event unless the Basic Inventory update interval as elapsed. If the hash differ the data is sent to the Notification Server whether the last Basic Inventory was sent 5 minutes before or 12 hours before.

This is because the Basic Inventory data is vital to core Notification Server collection.