Hi Hellfried,

That is a fair and excellent point. You have correctly identified the divergence between End User Compute (Laptops) and Data Center Infrastructure (Servers).

While the "Rename" strategy is perfect for generic assets like laptops (where history is less critical), your Server Cluster scenario absolutely demands a clean slate. You cannot have a new project team inheriting the Change History, Incidents, and Maintenance Windows of a cancelled project.

Here is the refined architecture for your specific Data Center use cases:

Use Case 1: Server Re-use (Project A -> Project B)

Goal: Same Hardware, totally new Identity. Your proposed workaround: "Hide the old asset from discovery by altering serial number..."

Verdict: You are correct. In the Data Center world, if you must reuse physical hardware for a completely new logical purpose, you must perform a "Neutralization" of the old record.

1. Retire the Old CI.

2. Scrub the Identity: You must clear or suffix the Serial Number on the Retired CI (e.g., change SN12345 to SN12345-RETIRED).

3. Discovery: When Discovery scans the "wiped" hardware again (now with a new hostname/IP), the IRE will not find a match on Serial Number (since you changed the old one) and will correctly create a pristine New CI.

Use Case 2: Hardware Replacement (RMA / Upgrade)

Goal: New Hardware, keep the old Relationships/Business Logic. Your Pain: "All relations and references must be copied... not that easy."

Verdict: This is solved by CSDM Abstraction, not by HAM. The architectural fix here is to ensure your Business Services and Change Requests are not pointed at the Hardware CI, but at the Logical CI (Application Service or Cluster Node).

• Bad Architecture: Business Service -> Depends on -> Server Hardware A

  • (If Hardware A breaks, the relationship breaks).

• Good Architecture: Business Service -> Depends on -> App Service / Cluster VIP -> Runs on -> Server Hardware A

  • (If Hardware A breaks, you swap it for Hardware B. You only update the downstream "Runs on" relationship. The Upstream business logic remains untouched).

Summary:

• For Laptops: Rename.

• For Servers (Reuse): Retire, Scrub Serial Number (Neutralize), and Discover as New.

• For Servers (Swap): Use logical abstraction layers (CSDM) so the hardware swap doesn't disconnect the Service Map.

If this deeper architectural view aligns with your server management needs, please mark it as Accepted Solution.

Best regards,
Brandão.