Identifying Duplicate CI Manually
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2024 12:56 PM
Hi All,
We are working to find duplicate CIs present in system which are not identified by system to create deduplicate tasks.
Some of class we excluded as its expected to have same display name in that particular class Ex : cmdb_ci_app_server_tomcat, IP_address
In the same way which all class can be expected to have same display name out of below list and why
If some one can help will be great help 🙂
.NET Application |
ACL EP |
Amazon Redshift |
Apache Active MQ |
Apache Web Server |
Application |
Application Cluster |
Application Server Instance |
Automatic Storage Management |
Availability Zone |
AWS Cloud ECS Cluster |
AWS Cloud ECS Service |
AWS Cloud ECS Task |
AWS Cloud ECS TaskDefinition |
AWS Datacenter |
Azure Datacenter |
Azure Subscription |
Block EP |
Business Application |
Business Capability |
Business Process |
CIM Profiles |
Cisco Firewall Device |
Citrix License server |
Citrix Netscaler |
Cloud Authentication |
Cloud DataBase |
Cloud DataBase Cluster |
Cloud File Service |
Cloud File Share |
Cloud Hardware Type |
Cloud Host |
Cloud Image |
Cloud IP Address |
Cloud Key Pair |
Cloud LB IPAddress |
Cloud Load Balancer |
Cloud Mgmt Network Interface |
Cloud Object Service |
Cloud Object Storage |
Cloud Public IP Address |
Cloud Queue Service |
Cloud Service Account |
Cloud Storage Account |
Cloud Table Service |
Cloud WebServer |
Cluster |
Cluster Node |
Cluster Virtual IP |
Cluster VM Affinity Rule Info |
Cluster VM Host Rule Info |
Coldfusion Application |
Coldfusion Server |
Compute Security Group |
Computer |
Configuration Item |
Container Repository |
Container Repository Entry |
CSU/DSU |
Customer Gateway |
Customer Gateway EP |
Data Center |
Database |
Database Instance |
Datastore Disk |
DB2 Instance |
DNS Alias |
DNS Name |
DNS Zone |
Docker Container |
Docker Engine |
Docker Image |
Docker Image Tag |
Docker Local Image |
DRS VM Config |
DynamoDB Table |
Edge Device |
ESX Resource Pool |
ESX Server |
Exchange Client Access Server |
Exchange MailBox |
ExchangeHub |
Fibre Channel Port |
Generic Application |
GlassFish |
Gunicorn |
Handheld Computing Device |
Hardware |
HBase Instance |
HP Service Manager |
HTTPs |
Hyper-V Resource Pool |
Hyper-V Resource Pool Component |
Hyper-V Server |
Hyper-V Virtual Machine Instance |
Hyper-V Virtual Network |
IBM Websphere |
IBM WebSphere MQ |
IIS Website |
Instance Scale Set |
Internet Gateway |
Internet Gateway EP |
IoT Device |
IP Address |
IP Firewall |
IP Router |
IP Switch |
J2EE EAR |
JBoss |
Jboss Fuse |
Jboss module |
Jboss Module Inclusion |
Kafka Broker |
Kafka Zoo Keeper |
KVM |
Linux Server |
Load Balancer |
Manual Endpoint |
Mapped Application Service |
Microsoft iis Web Server |
MongoDB Instance |
MS SQL DataBase |
MS SQL db inclusion |
MS SQL Server EP |
MSFT SQL Instance |
MSSQL Cluster |
MSSQL Cluster Node |
Multimedia Device |
MySQL Instance |
MySQL Server |
NAT |
NAT EP |
NAT Gateway |
Network ACL |
Network Gear |
Nginx Web Server |
Oracle Cluster |
Oracle Cluster Node |
Oracle Database |
Oracle Database Listener |
Oracle DB |
Oracle DB Service |
Oracle Enqueue Monitor |
Oracle Instance |
Oracle Management Agent |
Outbound Cluster Endpoint |
Outlet |
Out-of-Band Device |
Palo Alto Firewall Device |
PDU |
Personal Computer |
PostgreSQL Instance |
Print Queue |
Printer |
Route |
Route Table EP |
SAP ASCS Application |
SAP Business Objects CMS server |
SAP CI Application |
SAP DI Application |
SAP Hana Db |
SAP SCS Application |
SAP System |
Server |
Serverless Hardware |
Service |
Service Group |
Service Offering |
ServiceNow Application |
ServiceNow Application Component |
ServiceNow Connector |
ServiceNow MID Server |
SNC Component |
SQL Server Analysis Services |
SQL Server Integration Services |
SQL Server Reporting Services |
Storage Controller |
Storage File Share |
Storage HBA |
Storage Mapping |
Storage Pool |
Storage Server |
Storage Volume |
Subnet EP |
Switch Forwarding Rule |
Tag-Based Application Service |
TCP |
Tomcat |
Tomcat Connector |
Tomcat WAR Inclusion |
Tuxedo |
UNIX Cluster |
UNIX Cluster Node |
UNIX Cluster Resource |
UPS |
UPS Alarm |
UPS Input |
UPS Output |
Veritas Replicator |
Virtual Network Gateway Connection |
Virtual Private Gateway |
Virtual Private Gateway EP |
Virtual Server Array |
VMware Network Adapter |
VMware vCenter Cluster |
VMware vCenter Datacenter |
VMware vCenter Datastore |
VMware vCenter Host Group |
VMware vCenter Instance |
VMware vCenter VM Group |
VMware Virtual Machine Instance |
VMware Virtual Machine Template |
VNIC EP |
WBEM Service |
Wearable Technology |
Web Application |
Web Server Instance |
Web Service |
Web Site |
Weblogic |
Weblogic LB |
Weblogic Module |
Weblogic Module Server |
Websphere Cell |
Websphere Portal |
Windows Cluster |
Windows Cluster Node |
Windows Cluster Resource |
Windows Server |
Zoo Keeper Cluster |
Zoo Keeper Cluster Node |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2024 01:36 PM
Hi @Roopa11,
Classes that can be expected to have the same display name across instances are those that represent similar entities or functionalities. For instance:
Generic Classes: Classes like "IP Address," "Cluster," and "Server" may have similar display names as they represent fundamental components with common names.
Cloud-related Classes: Classes associated with cloud services, such as "AWS Cloud ECS Cluster" or "Azure Subscription," might share display names within the same cloud environment.
Web Technologies: Classes like "Web Server Instance," "Tomcat," and "Weblogic" could have common display names as they are related to web technologies.
Middleware and Integration Classes: Classes like "ServiceNow Connector" and "SQL Server Integration Services" may share display names if they serve similar integration functions.
Networking Classes: Classes related to networking devices, such as "Router" and "Switch," might have similar display names.
Remember, the key is to look for classes that fulfill similar roles or represent similar types of entities, as they are more likely to share display names. Always consider the specific context and functionality of each class within your system.
Please mark this as correct answer and helpful if it is resolved, or mark this helpful if this helps you to reach towards solution.
Thanks,
Arsalan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2024 01:58 PM - edited 02-18-2024 01:59 PM
Hi ,Arsalan
Thanks for reply,
How will we get to know what above mentioned classes belongs to below categories and what is the reason to have same display names
Generic Classes:
Cloud-related Classes:
Web Technologies:
Middleware and Integration Classes:
Networking Classes
Thanks
Roopa