So I have been tasked to roll out IE11 via Kace.

I created an entry in Software with the custom inventory rules:
RegistryValueGreaterThan(HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer, svcVersion, 11)
AND RegistryValueLessThan(HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer, svcVersion, 12)

Which worked last week but now it is not. All I have done since then was update our agents to 6.3.314

I have also tried:
FileVersionGreaterThan(C:\Program Files\Internet Explorer\iexplorer.exe, 11) AND
FileVersionLessThan(C:\Program Files\Internet Explorer\iexplorer.exe, 12)

And still get nothing. 
Is anyone else having this issue?
Answer Summary:
The answer was to point it to the 64bit registry via HKLM64 and to make sure the only spaces were between the keys and the AND. IE: RegistryValueGreaterThan(HKEY_LOCAL_MACHINE64\SOFTWARE\Microsoft\Internet Explorer,svcVersion,11) AND RegistryValueLessThan(HKEY_LOCAL_MACHINE64\SOFTWARE\Microsoft\Internet Explorer,svcVersion,12) Also there is no Return or Enter between the two keys.
Cancel
2 Comments   [ + ] Show Comments

Comments

  • BE AWARE EVERY K1000 Administrator!!!

    My Script which has Verify a registry key exists... is not working even if I put HKLM64 or HKLM after I upgraded to this Agent version.
    I can set Value in HKLM64 but cannot ready or Verify......
  • http://www.itninja.com/question/don-t-update-to-kace-agent-6-3-31-if-you-have-script-to-verify-hklm-or-hklm64-or-custom-inventory-rule-registry
Please log in to comment

Answer Chosen by the Author

1
I have the latest agent and this custom inventory rule for IE11 is still working for me:

RegistryValueGreaterThan(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer,svcVersion,11) AND RegistryValueLessThan(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer,svcVersion,12)

I think you may be able to tweak yours this way to make it work:

RegistryValueGreaterThan(HKEY_LOCAL_MACHINE64\SOFTWARE\Microsoft\Internet Explorer,svcVersion,11)
AND RegistryValueLessThan(HKEY_LOCAL_MACHINE64\SOFTWARE\Microsoft\Internet Explorer,svcVersion,12)

In the case of IE11 there are entries for both 64 bit and 32 bit keys. I don't know why it worked before - but in you were pointing to the 32 bit key path but including Wow6432Node which doesn't exist there...
Answered 04/28/2015 by: jegolf
Red Belt

  • I have put that into my custom inventory rule and had a few PCs force check in and it is still not working.
    • I remember the rules getting picky on extra spaces at one point. Definitely don't have any additional spaces after your commas and no leading spaces or returns at the end...?
      • It was the spaces killing me. Thank you!
Please log in to comment

Answers

Answer this question or Comment on this question for clarity