Pre Service Mapping Task script fetching wrong computer_id
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2025 02:37 AM - edited 02-18-2025 03:58 AM
We are performing Service Mapping and noticed that we are always getting different load balancers everytime we run top-down discovery. On checking the OOTB Pre Service Mapping Task script (LoadBalncerInfo), we see that the variable "computer_id" is bringing in different sys_IDs for every discovery run. Any idea where this variable "computer_id" fetches CI sys_IDs from?
0 REPLIES 0