Discovery
Infrastructure Services
Understand what roles and services each server is running across your infrastructure — essential for dependency mapping and migration risk assessment.
Overview
Infrastructure Services maps the service roles of every device in your estate — Web Server, Database, Middleware, File Server, Domain Controller, Appliance, and more. It answers: what is each server actually doing? This view is critical for identifying servers that cannot be migrated without careful sequencing.
Server Roles
Distribution of normalised server roles across the estate.
Role Applications
Top 15 applications by how many servers run them (IIS, SQL, Apache, etc.).
Device Service Detail
Per-device breakdown of role, role applications, environment, and OS.
When to Use
- When building move groups — identify servers with shared service dependencies
- To find Domain Controllers and infrastructure services that must move last
- When assessing migration risk for a specific environment or business unit
- To identify devices with unknown roles that need investigation before migration
Dashboard Sections
| Section | What it shows |
|---|---|
| KPI Cards | % of devices with roles defined, count of unique server roles, count of unique role applications, count of devices with unknown roles. |
| Server Roles Distribution | Donut/bar chart of normalised roles: Web Server, Database, Middleware, File Server, Domain Controller, Appliance, Unknown. |
| Top 15 Role Applications | Most common software found across servers (SQL Server, PostgreSQL, IIS, Apache, NGINX, etc.) by device count. |
| Roles by Environment | How role distribution varies across Production, Development, Test, UAT, etc. |
| Applications by Server Role | Cross-tab of which role applications run on which server role types. |
| Device Service Details Table | Full table: Device Name, Role, Role Applications, Environment, Operating System, Power State. |
How to Use
1
Navigate to Discovery → Data Quality & Discovery → Infrastructure Services.
2
Check the KPI cards. A high "Unknown Roles" count means device role fields are not populated — this needs fixing before migration planning.
3
Review the Server Roles Distribution chart. Note how many Domain Controllers, Database servers, and shared services exist — these typically need to migrate last or be excluded from automated tools.
4
Use the Device Service Details table to export a list of devices with roles. Sort by Role to group servers of the same type for move group planning.
Key Fields
| Field | Description |
|---|---|
| Device Name | Hostname of the server. |
| Role | Normalised server role (Web Server, Database, Middleware, File Server, Domain Controller, Appliance, Unknown). |
| Role Applications | Software applications discovered running on this server (e.g. IIS, SQL Server, PostgreSQL). |
| Environment | Production, Development, Test, UAT, etc. |
| Operating System | OS and version. |
| Power State | Whether the device is currently powered on or off. |
Tips & Common Mistakes
Any device showing Unknown role should be investigated — either update the role in the CMDB Devices record or run a new integration import with fuller data.
Domain Controllers and shared database servers should always be placed in their own move group and migrated last to avoid breaking other services.
Role Applications data comes from integration imports (e.g. RVTools or Nutanix). If the data source doesn't include installed software, this chart will be empty.