Scanning Registry Keys

agpost123 · 12-12-2008, 09:29 AM

Hello everyone,

I have a questions i need some help with. We have a Standard Desktop Image, and have a few versions (with updates and new software etc). We add a registry key under Local Machine that says which version build it is. We would like to be able to create collections to know which computer is which build.

Any one have any idea's how to let Inventory (or some other tool) to scan the registry? (a key we select)

Thanks
Tony

jharings · 12-12-2008, 09:41 AM

Custom inventory can gather that key.

The inventory reference guide has a pretty good step by step, and this link:https://kb.altiris.com/article.asp?article=4237&p=1 has some samples.

Obviously, if you have trouble post your work (or the details to the key in question here) and we can help you out.

Nick · 12-12-2008, 09:49 AM

Tony,

I've done exactly what you are trying to do in the past and Jim's advice is exactly what you need to do.

Something else I did was to also gather the OS Install Date using custom inventory as well. This way I would be able to see the version of the image as well as the date the image was applied.

tbarkdull · 03-16-2009, 11:30 AM

This resource has great potential. But for us with little or no XML background. it is of little help. Can anyone provide links or recommendations for XML editing and understanding? I wish to modify one of them to obtain the default printer for each user which is located in the registry at HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows.

tbarkdull · 03-18-2009, 10:43 AM

I modified an xml included in the above link to attempt to create a new table in NS to report the default printer. Can anyone provide input as to review it and make any changes? All help is appreciated.

grantis · 06-04-2009, 08:07 AM

Thought this solution we use might help you guys as it has proved a great and easy solution for us.

At every build release we create a windows installer package named say "COMPANY NAME Build Version 3.5"

This drops an exe named "COMPANY NAME Build Version 3.5" into Program Files folder.

Inventory picks up Add/Remove programs and the exe for our Build Collections and they build up.

so from our base image we deploy build updates that increment depending on what inventory has picked up and the machine populated to particular buil version collection.

So collections update sooner as well as we dont rely on full inventory, just add/remove inventory which runs more often.

We also add a bitmap with the build version as the wallpaper so users know they are up to date.

Hope this helps