"Assigned to" Attribute is "empty"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2023 10:54 AM - edited 11-27-2023 03:25 AM
OK - I am seeing a lot of assets that have the attribute "assigned to" as "empty". My goal is to ensure all endpoint assets(laptops/desktops) are assigned to an employee. I am seeing about 10% that are unassigned. From what I have read ServiceNOW probe Shazzam by default doesn’t use anything other than the mid server discovery pattern Windows OS Information to set the assigned to. The discovery error on these devices is "<IP Address> is not a reachable host(no response to target ports scanned by MIDI)".
Please let me know what steps you have taken to fix the issue in these situations. Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2023 03:55 AM
sorry, but is an absolute unclear question. What is your expectation regarding the "Assigned to". Which person should be linked by Discovery? This is not a technical issue but a business one! Therefore explain better your situation, your problems and the underlying business requirement!
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2023 03:24 AM
OK - I am seeing a lot of assets that have the attribute "assigned to" as "empty". My goal is to ensure an endpoint assets(laptops/desktops) are assigned to an employee. I am seeing about 10% that are unassigned. From what I have read ServiceNOW probe Shazzam by default doesn’t use anything other than the mid server discovery pattern Windows OS Information to set the assigned to. The discovery error on these devices is "<IP Address> is not a reachable host(no response to target ports scanned by MIDI)".
Please let me know what steps you have taken to fix the issue in these situations. Thanks