IT Asset Models
To access the available models for the IT Asset module, go to the main menu and navigate to the “IT Asset” section:
From here, we can find various usable models. In the following articles there is a detailed description of each
ITAM Device
From there you can see the Devices and organize them into by configuring your custom grids and access the form containing their data to modify them if it is necessary.
From this section, you can manually add a device using the ‘Add Device’ button. Anyway, for this purpose, you can use the CMDB module. The difference is that the IT Asset module is designed to automatically retrieve devices, unlike the CMDB module through which management of devices is only manual.
To add a new Device by agent, you can click on the ‘Download Agent’ button (Agent installation procedure is illustrated here). Once the agent is downloaded and configured your current Device will be added as a record on the grid.
Licenses in use: Available at the top of the page, it indicates the available number of devices that can be added. In fact, the devices in this module are subject to licensing.
Device Tab & Fields
By clicking on a Device in the grid, you can access the form containing its data, such as:
- CPU
- BIOS
- HDD
- Network Interfaces
- Operating System
- RAM
- installed software
In device edit or creation, the following tab and fields are available:
Device Data Tab
On Device Data Tab, there are the main information of a device. Below is the detail:
Field | Description |
Name | Text field with the retrieved Device’s name. |
Device Name | The retrieved Device’s name |
Status | Select field with two values: enabled or disabled. Initially its value is set to enabled. |
Type | Select field where you can choose a device type. It has already some pre-configured values such as: physical, virtual, other and unknown. |
Subtype | Select field where you can choose a device subtype. Each subtype value is linked to a type. |
Description | Text area field where can add a description for your device. |
Serial Number, Model Name, Vendor Name, Domain, Last Username, Last User Domain | Text fields which are auto populated from agent, with the current device’s corresponding data. |
Last Scan At | Datetime field which indicates the last time this device was scanned by an agent or remote collector. |
Last Seen At | Datetime field which reflects the last time the device was observed to be active and responsive. |
In Service | Select field with two values: ‘Yes’ and ‘No’, which indicates if the device still has the agent downloaded and is currently active and operational within the network. |
Hardware Tab
On Hardware Tab, all device’s hardware such as BIOS, System Chassis, CPU, RAM, Network Interface etc.
All device-related hardware information is stored in different grid fields. Each grid record has an action column, which you can click to view further details on the related hardware data.
Software Tab
Under “Software” tab, there are all software information related to the main device. We can find the following grids:
- Operating System: Grid field which stores all the information related to the device’s operating system.
- Software: field which stores all data about software programs installed in your device.
Users Tab
In the Users Tab you can relate client information to the device.
Field | Description |
Owner Company, Assigned Company | Select fields with values retrieved from Company model. |
Owner Group, Assigned Group | Select fields with values retrieved from Group model. |
Owner User, Assigned User | Select fields with values retrieved from User model. |
Monitoring Tab
Through “Monitoring” Tab, you can monitor your device’s data:
The available fields are:
Field | Description |
Remote Control | Select field which allows you to connect and take control of the device remotely. |
Monitoring Data | It shows a graphical representation of your device resources usage during a period of time. |
Metrics | Multiselect field where you can choose the resource usage that you want to show on the graph. |
Period | Select field where you can choose timeframe for displaying data. |
ITAM Software
The software installed on collected devices is automatically added to Deepser.
You can also organize software by configuring custom grids and manually add new records.
By clicking on a Software entry in the grid, you can access the form containing its data:
The available fields for this module are:
Field | Description |
Name | Text field with the retrieved software’s name |
Vendor | Text field with the related vendor of the software |
Version | Text field that indicates the current version of the software |
Install Date | Datetime field which indicates the date the software was installed. |
First Scanned At | Datetime field which indicates the date when the software was scanned on the device. |
Identifying Number | Text field with a unique string to identify the software. |
Device | Text field where it is saved the device Id connected to this software |
Description | Text area field where you can add a description for the software |
ITAM Network
- Subnet: This type stores information about network subnets. It helps in organizing and managing large ranges of IP addresses by grouping them into subnets. You can configure various attributes related to the subnet, such as its range and any relevant network settings.
- IP Address: This type stores specific details about individual IP addresses within the defined subnets. It allows for the tracking and management of each IP address, including its assignment status, associated device, and any additional configuration details.
Together, these types provide a comprehensive framework for managing network infrastructure, ensuring that both broad subnet information and detailed IP address data are effectively organized and accessible.
Subnet
We can access existing Subnet or manually create one from the main menu: “IT Asset > Network > Subnet”.
By clicking on “Add IP Address” or selecting an existing record, the following screen will appear:
For Subnet editing or creation, the following fields are available:
Field | Description |
Name | Text field which is used to indicate the name of subnet. |
Network Address | Text field which indicates the base address of the subnet. This field is populated by a CIDR IP address. |
Bitmask | The subnet mask in bit form, indicating the number of bits used for the network portion of the address. |
Range Start | The first usable IP address in the subnet. |
Range End | The last usable IP address in the subnet. |
Gateway IP Address | The IP address of the gateway or router for the subnet, used for routing traffic outside the subnet. |
Gateway Mac Address | The MAC address of the gateway or router associated with the Gateway IP Address. |
Subnet Unique Id | A unique identifier for the subnet within the system |
Last Seen At | Datetime field indicating the last time this subnet was observed or updated. |
Status | Select field in which you can enable or disable the subnet. |
Subnet IPs | Grid field where there are shown all the ips connected to this subnet. |
IP Address
We can access existing IP addresses or manually create one from the main menu: “IT Asset > Network > IP Address”.
By clicking on “Add IP Address” or selecting an existing record, the following screen will appear:
Field | Description |
IPv4 Address | Text field where IPv4 address is stored. |
IPv6 Address | Text field that stores an IPv6 address. Allowed format for this field is the standard notation of IPv6 |
Subnet | Select field with all the available subnets which can be connected to this ip. |
Device | Select field which links the device with this ip address. |
Network Interface | This field is used to select the network interface associated with the IP address. It could refer to a physical or virtual interface on a device. |
Status | Select field which can ‘enable’ or ‘disable’ this ip address. |
ITAM Management
- Scripting allows administrators to automate tasks by running predefined scripts on devices, reducing manual effort and ensuring consistency.
- Updates enable the monitoring and deployment of software updates across all devices, ensuring they remain secure and up-to-date.
- Jobs provide a way to schedule and manage recurring tasks or operations, offering flexibility and control over routine maintenance.
Below are the detailed operations of each type.
Scripting
We can access the “Scripting” type from the main menu: “IT Asset > Management > Scripting”
Within the Scripting type, there are two separate sections:
- Script: In this section, you can view and manage predefined scripts that are available for execution on devices. You can also create new scripts by clicking the “Add Script” button. These scripts can automate various tasks and operations on your devices.
- Run History: This section provides a detailed log of all script executions. It shows the history of scripts that have been run, including information such as the date and time of execution, the status of the script, and any errors or issues encountered. By clicking on individual log records, you can access detailed information about each execution, including which devices were affected and the results of the script.
These sections allow you to effectively manage and monitor script usage, automate tasks, and review the outcomes of script executions.
Script
Clicking on “Script” we can access to the list of predefined script that can be execute on your device (and cannot be modified):
However, you can also create your own script to execute by clicking on the “Add Script” button located at the top right corner of the screen:
The fields available in the script model are the following:
Field | Description |
Name | The name for your script |
Type | With this field you can choose the type of your script: • Batch • Powershell • Bash (Linux/Mac) |
Scope | With this field you can choose if the script should be run for all system users or for the current user. |
Category 1 | Categories are used to categorize the script you are creating. |
Category 2 | |
Description | A field to describe the script you are creating. |
Content | This field should contain the command you want to execute. In this field should be inserted powershell, batch or bash commands. |
Execution Timeout | Waiting time before the script is marked as not completed successfully. |
Arguments | With this field you can provide additional parameters to the script. |
User Defined | This field is read-only and indicates whether the script was manually created by a user. Existing scripts have this field set to “No”. |
Status | With this field you can enable or disable the script. |
Script Example
Below an example of an existing script:
This script allow a user to clean up a disk with a PoweShell command. It can be identified by “Type” field (Powershell) and the “Content” which contains the commands to be sent to a device.
Execute Script
To execute a script on a device, you need to access the specific device, and at the top right corner of the screen, you can use the green “Run Script” button:
Clicking on the button will open a new screen:
From here, you can choose to execute either a user-defined script (on the left side) or a script from the System Library (on the right side).
Clicking the “Run” button next to a script will execute it.
Additionally, the “Run History” button at the top center of the screen allows you to access the history of executed scripts (“Run History” section).
Run History
As previously mentioned, the Run History section enables users to check and verify results of executed scripts:
By clicking on a history record we can see the following information:
Below is the detail of their operation:
Field | Description |
Script | History related script. |
Device | Device on which the script was executed |
Execution Status | This field determine the execution status. |
Sent By | The user who sent the command. |
Sent At | The date when the command was sent to the server. |
Executed At | The execution date. |
Output | The output received from the sent command. |
Return Code | Exit status or result code returned by sent command. |
Updates
We can access “Updates” type from the main menu: “IT Asset > Management > Updates”.
In this section, you can find a list of all available updates detected by the remote collector on the scanned devices. This includes:
- Updates Available for Installation: These are updates that have been detected on the scanned devices but have not yet been installed. The list shows which devices can receive these updates.
- Updates Already Installed: These are updates that have already been applied to the scanned devices. The list indicates which devices have successfully installed these updates.
- Update Details: For each update, you can view additional information such as the update name, version, release date, and any relevant descriptions or notes.
- Installation Status: See the number of devices where each update is pending installation or has been installed. This helps in monitoring the update deployment process.
- Filter and Search Options: You may have options to filter or search for specific updates, platform and other data making it easier to manage and track updates across your IT infrastructure.
This comprehensive view helps you effectively manage and oversee the update status of your devices, ensuring that all necessary updates are applied and monitored
In the “Available For Devices” column of the grid, you can see which scanned devices can receive the update. The number in the blue box indicates how many devices the update can be installed on.
Clicking on the blue box will display a list of devices on which you can install the update:
In the “Installed On Devices” column of the grid, you can see which scanned devices have had the update installed. The number in the gray box indicates how many devices have received the update.
Clicking on the gray box will display a detailed list of devices on which the update has been installed. Depending on the type of update, you may also have the option to uninstall it:
Job
- Configuration: In this section, you can create, view, and manage job configurations. This includes setting up new jobs, defining parameters, and scheduling tasks. It allows you to configure how jobs are executed, including specifying details such as target devices, job types, and execution schedules.
- Event Log: This section provides a comprehensive log of all job executions based on your configurations. Here, you can review the history of job runs, including details on the status of each job, any errors encountered, and the outcomes of the execution. This log helps in monitoring job performance and troubleshooting issues by providing insights into job activities and results.
These sections help manage and track the execution of jobs within Deepser, ensuring effective job management and performance monitoring.
Configuration
With a Job, a user can automate the release of updates on scanned devices. To create a new Job Configuration, click on “Add RRM Job” after accessing the Configuration section:
The following screen will appear:
For a job configuration, the following fields are available:
Field | Description |
Name | Text field that identifies the job configuration. |
Platform | At the moment, only Windows platform are supported. |
Cron Expression | It allows you to define the run interval of the job. |
Install Update Types | Multiselect field through which you can choose the types of updates you want to handle with the job configuration. You can select the following types:
|
Device Exp In | Using this query builder field, you can filter the devices to be included in the job configuration. |
Device Filter (Script) | In the scripting area field, you can define the criteria to filter the devices that should be included in the job configuration. It can be used for more complex filtering based on device data. |
Status | Select field which can ‘enable’ or disable the job configuration. |
Event Log
n the “Event Log” section of Management, you can view all job configurations executed according to your settings. This section contains a log of job executions:
Clicking on a single log record will provide information about the update (or uninstalled update) on a device, details of the installed update, and the job that was executed:
