TushLog PHYSICAL Table Structure

This page contains technical detail about the physical database structure. It is not required for normal day to day operation of the Point Of Sale.

Goto: Documentation Home

This table holds a log of all TUSH identification blocks seen. A TUSH block can be large and complex, with most fields are voluntary.

TUSH blocks hold information about a system. For details about a user or application, see CREDLog.

Example Row

Physkey	Date	MAC	IP	CpuName	SystemName	DiskSerial
VBR74B5I3954B5H47	1-Jan-2015	00-10-20-30-40-CF	192.168.1.10	DevDell	Dell Vostro 1500	SI9283828J65

Columns

FieldName	Datatype	Meta Info	Gnap	Description
Physkey	string:44,zerolen		100/s	Unique key assigned to this record
PhyskeyHash	long		101/E	Hash version of Physkey. This field can potentially have duplicates
Date	datetime		102/s	Date/Time this record was created
MAC	string:24,zerolen		120/s	Primary MAC address of system. Where multiple MAC addresses are present, the originator selects primary
IP	string:24,zerolen		121/s	Primary IP address of system. Where multiple IP addresses are present, the originator selects primary
DiskSerial			123/s	Disk drive serial number. This is not the Volume serial number assigned when a drive is formatted, it is the physical device serial number. Not all disks are capable of supplying this information
DiskModel			124/s
SystemIdent			130/s
SystemName			125/s	Hardware description as stored in BIOS
SystemUUID			126/s
SystemVendor			127/s	Hardware manufacturer
CpuName			128/s	The name of the computer as given by Windows
CpuUniqueId			129/s
CurDate			121/s
CurDateUTC			122/s
Licid			151/E
ActivePath			152/s
ActiveDatabase			153/s
DatabaseDriver			154/s
WindowsVersion			160/s	Actual version of Windows in use
TustKey			200/s	Unique id used on TUST status packets. This value is very likely to be unique over all systems, however it will be identical for machines that are ghosted at the physical disk level.
The WLAN_* information can be present multiple times. As multiple wireless networks may be visible we will record as many entries as possible. Increase the final number on the field to store more entries. There is no guarantee what order records will be written.
WLAN_SSID_0			/s	Name of visible wireless network
WLAN_BSSID_0			/s	Access Point MAC for visible wireless network
WLAN_Signal_0			/E	Signal strength
WLAN_Channel_0			/E	Channel

Indexing

❖ A unique primary key should exist on the physkey field.
❖ You may wish to index PhyskeyHash as an alternative for performance reasons.