Discovery updating incorrect RAM value for Windows server?

[pavan garige]

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?

[AJ-TechTrek]

Hi @pavan garige ,

You may want to review your Windows credentials to ensure Discovery has appropriate access to them retrieve thorough information for your devices.

More information can be found within the credentials section of this documentation.

https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/discovery/refe...

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1116898

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

Ajay Kumar

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[Pratiksha]

In major cases you wont see incorrect value. You can check the status logs to see the value which is coming in payload. Discovery runs powershell commands to get the information. 

Regards,

Pratiksha

[pavan garige]

HI Pratiksha

Thanks for the information.we have checked the payload value of RAM which is 0 (incorrect value) .

[Pratiksha]

The credentials should have access to run the powershell commands. Things you can try : 

• login with same creds on device and see if you can run the commands to get the values. 
• you should try connecting the server from mid server. That will help you to solve more. 
• if all are good try to debug the windows server pattern it will tell you if the pattern is getting to the results or not. 

[ChiranjeeviR]

Hi @pavan garige 

check Payload details and if you are using probes convert them to pattern to use discovery which will resolve the issue