Skip to content

Device42 integration

The OctoSAM to Device42 integration module provides inventory information to Device42. No devices are created, since it is assumed that Device42 gets information about new devices very early in their lifecycle from other sources such as finanacials.

Architecture

The integration connects via the Devic42 REST API and updates devices with matching machine names. Integration logic and the Device42 API client are integrated in the OctoSAM base software and can be configured via appsettings.json file.

OctoUtil

Synchronization can be triggered with the octoutil sync device42 command. Recommended to configure via Housekeeping Scripts after daily housekeeping.

Device fields

Fieldname Type Description
manufacturer String Normalized manufacturer name from OctoSAM catalog (only for physical machines)
hardware String Scanned hardware model name (only for physical machines)
ram_size Number RAM Size in GB
cpu_speed Number Processor speed in GHz
hz_id Number always value 2 (GHz)
total_cpus Number Number of sockets
core_per_cpu Number
threads_per_core Number
hard_disk_count Number Number of disk devices (USB disk and mounted file systems are not counted)
hard_disk_size Number Total size of disk in GB
bios_version Number

Operating system fields

OperatingSystem is an own entity in Device42, for new OS we create the OS Entity and then create the relations to the device.

Fieldname Type Description
manufacturer String Normalized manufacturer name from OctoSAM catalog
name String Name of the operating system

Device custom fields

Fieldname Type Description
FirstScan Date OctoSAM first scan date
LastScan Date OctoSAM last scan date
LastFoundInDirectory Date Date OctoSAM last found this object in Active Directory
DeletedInDirectory Boolean Optional flag that OctoSAM detected deletion of the object in ActiveDirectory

Device URL

Optionally, we create a device URL that points to the devices Page in OctoSAM.

Synchronization status fields in OctoSAM

Optionally, synchronization writes its state to the SynchLastSynch and SynchTokenId fields in the OctoSAM database. These fields are potentially shared with other integrations (except ServiceNow integration which has its own exclusive fields), Only one integration can write its state back to the database.