Note: Available only for new signups after the 31 March, 2026 release. If you signed up earlier, refer to the existing ITAM documentation.

Freshservice categorizes assets by their unique dependencies to ensure dependency maps accurately reflect your infrastructure.

• Virtual Devices: Tracks the relationship between a guest VM and its parent host.

• Blade Servers: Manages physical placement and slot numbering within a chassis.

This article covers host assignments, hypervisor-specific notes, and physical slot mapping for virtual and blade subtypes.

Prerequisites

You need the following before managing virtual and blade devices:

• Access to the IT Asset Management module in your Freshservice instance.

• Administrator privileges to edit device records and hardware models.

• Pre-configured host chassis for blade assignments or host servers for virtual machines.

Virtual devices and hypervisor details

For virtual devices, you can define the host relationship and manage core technical properties such as CPU/Memory/HardDisk specs, Operating System details, IP Addresses, and connectivity Ports.

A key distinction exists regarding device documentation:

• Hypervisor Description: This field automatically displays notes added to VMware virtual devices from outside of Freshservice (e.g., directly in vCenter). If no notes exist in VMware, this field is hidden.

• Device Notes: This is the standard Freshservice Notes field used for internal documentation. It remains separate from the hypervisor-sourced description to prevent data overwrites.

Blade device subtype

Blade is a specific subtype of physical devices. These records allow you to define the blade hardware model, support vendors, and physical orientation.

Critical fields for blade management include:

• Device Host Chassis: The parent physical enclosure where the blade is installed.

• Blade Slot #: The specific physical slot ID within the chassis.

Manage virtual machine host assignments

To associate a virtual device with its host, follow these steps:

1. Go to IT Asset Management > Inventory and select a virtual device record.

2. Click Edit in the upper-right corner.

3. In the Information tab, locate the Device Virtual Host field.

4. Select the parent host from the dropdown menu or click the Add new Device Virtual Host to create a new host.

5. Click Update.

Configure blade chassis and slot details

To map a blade server to a chassis, follow these steps:

1. Go to a device record with the Blade subtype and click Edit.

2. Locate the Device Host Chassis field and select the target enclosure.

3. Enter the specific slot position in the Blade Slot # field.

4. (Optional) Select the hardware model under the Hardware dropdown menu to define the physical dimensions of the blade.

5. Click Update.

Important considerations

Review the following information to ensure accurate virtual asset tracking and chassis management:

• Automated Population: Most virtual machine properties and hypervisor descriptions are automatically populated during a VMware or Hyper-V autodiscovery job.

• Blade Subtype Logic: When you select a blade hardware model, Freshservice uses the model's dimensions to ensure it fits within the defined slots of the host chassis.

• Data Separation: Changes made to the Notes field in Freshservice will not overwrite the Hypervisor Description pulled from your virtual environment, ensuring both local and external documentation are preserved.