/build/static/layout/Breadcrumb_cap_w.png

Custom Inventory - Registry Question

We are trying to get a value out of the registry. Attached is a screenshot of the key we would like.

And this is the rule we have been trying to use but it is not working.
RegistryValueReturn(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Environment,TIA,NUMBER)

Are we missing something in the rule?

Thank You


0 Comments   [ + ] Show comments

Answers (6)

Posted by: cmccracken 12 years ago
Orange Senior Belt
1
There should be a space between Session and Manager.

Casey
Posted by: cmccracken 12 years ago
Orange Senior Belt
0
What if you return it as TEXT?

Casey
Posted by: bmrayner 12 years ago
Yellow Belt
0
Still nothing is returned
Posted by: bmrayner 12 years ago
Yellow Belt
0
ORIGINAL: cmccracken

There should be a space between Session and Manager.

Casey


That worked and thank you for the help. Not sure how we missed that in the first place. [:-]
Posted by: merrymax 12 years ago
Senior Purple Belt
0
Hi,

I am also trying to get a value of registry but the value is dward , can any body suggest a solution regarding getting a DWARD value.
Posted by: cblake 12 years ago
Red Belt
0
The key type isn't applicable; the data type is. Meaning TEXT, NUMBER, DATE are the only types of data that the K1 can return. So if it's a DWORD in regedit; return it as text or number as shown above.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ