/build/static/layout/Breadcrumb_cap_w.png

software custom inventory rule

Hello all, I am having a problem with a custom inventory rule for software. I have a software entry that is used to determine if a custom registry key is present on newly imaged systems. It works fine on my 32bit deployments, but not for 64bit, any ideas as to why? Yes I have all versions of Windows 7 selected as supported operating systems.

0 Comments   [ + ] Show comments

Answers (6)

Posted by: jrscribner 12 years ago
Purple Belt
0
I wonder if there is any relationship to the bug discussed in the post a couple days ago about FileExist custom inventory rules not working on x64 machines, for reference it was this post: http://itninja.com/question/sequence-question93
Posted by: airwolf 12 years ago
Red Belt
0
32-bit registry keys on a 64-bit system are stored in a sub-key named Wow6432Node.
Posted by: cblake 12 years ago
Red Belt
0
Maybe you could share your rule?
Posted by: csummers73 12 years ago
Orange Belt
0
well that would make sense if KBOX cannot do the file verification, so I will change the rule to look for something else. As for the registry, it is a custom key that I add during post-install while imaging, so it is not located in the Wow6432Node.
Posted by: rmeyer 12 years ago
Second Degree Blue Belt
0
a quick 'n dirty solution to this would be to add a script to the "runonce" that check for the file and put a check file if it exist or delete it if it doesn't in a folder like C:\MySpecialFolder\lalala\temp that you can check on insted.

I wouldn't recommend it because you will need to clean up after it at some point, but it is a workaround.

Or you could install a 32 bit version of the application then it will not end up in the 64 bit folder/registry and then kace should be able to find it since it's a 32 bit version
Posted by: ncsutmf 12 years ago
Green Belt
0
I reported a similar issue recently to support regarding the registry issue. I believe it is supposed to be one of the fixes in the next version of the client. But, until that comes out you can probably either make a separate post install for the 64-bit or have your post install check to see if it is 64-bit or 32-bit and put it in the Wow6432Node location if its 64-bit. Since its supposed to work correctly in an updated client, it may be best to put it in both places on the 64-bit machines.
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