Discovery updating incorrect RAM value for Windows server?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-15-2024 06:28 AM
Hi All,
I have tried to discover the windows server , it is able to discover and updating the correct information for Serial number, CPU, IP address etc , however it is updating RAM(MB) value is '0' instead of 16GB .
Here Server actual RAM is '16' GB , but it is discovering RAM is '0'.
Can anyone let us know the issue why it is discovery incorrect RAM Value?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-17-2024 03:42 AM - edited ‎05-17-2024 03:44 AM
Hi @pavan garige ,
Did you check in the payload for the values coming for RAM?
Try clearing cache as well.
To clear cache of CI, you can find here. Understanding Probe Results Cache returning as "Processed"
Please mark helpful and accept as solution if it helped.
Thanks,
Mahathi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-21-2024 12:41 AM
HI Mahathi,
Thanks for the information.we have checked the payload value of RAM which is 0 (incorrect value) and I could see no records in Probe result cache table even after discovering the CI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-21-2024 07:18 AM
Hi @pavan garige ,
If there is no value in the payload then please check with the server team.
You might have to change the location path from where the RAM Details are fetched.
Only if there is a value in the payload the same gets updated in ServiceNow.
Please mark helpful and accept as solution if this helped answer your query.
Thanks,
Mahathi