[BESAdmin-Announcements] Windows Registry Wizard changes

[Announcements for BES Administrators]

Dear BigFix administrators,

The Windows Registry Wizard has been updated to improve handling of REG_DWORD values. While these registry values are internally hexadecimal, administrators may choose to enter hexadecimal or integer values. The wizard will now interpret which type of value it has been given and construct appropriate detection relevance and action script. Additionally, bounds checking has been added so that oversized values and invalid hexadecimal strings cannot be accidentally used.

Some examples:

1) Input value: starts with "0x" [e.g. "0x20"]
   Solution: treat it as hexadecimal
   Target Relevance: "...("20" != it as integer as hexadecimal)..."
   Action Script: "...=dword:00000020"

2) Input value: contains only digits [e.g. "20"]
   Solution: treat it as integer
   Target Relevance: "...(20 != it as integer)..."
   Action Script: "...=dword:00000014" [converted integer 20 into hexadecimal 20, which is "14"]

3) Input value: contains letters and possibly numbers, but does not start with "0x" [e.g. "A0"]
   Solution: treat it as hexadecimal
   Target Relevance: "...("A0" != it as integer as hexadecimal)..."
   Action Script: "...=dword:000000A0"


Additionally, the DWORD caption in the wizard has been changed from "Enter in hexadecimal form (8 character maximum)" to "8 characters maximum (include 0x for hexadecimal)."

Thank you,
BigFix Application Engineering Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://bigmail.bigfix.com/pipermail/besadmin-announcements/attachments/20101013/4523ba92/attachment.htm