I threw a simple one together yesterday just so that I could get a quick count of fixed vs not fixed. I wasn’t overly concerned with getting it to perfectly tell me “true” or “false”. Using Install Spy - I found which registry entries were changed after running the update. Here is what I looked for for EST. Bascially there were only 2-4 possible values (that I came up with). Two of the four were a couple of machines that had issues. But 99% of my systems fell between 2 possible values.
Changed - 00000300020002000000000000000000
Not Changed - 00000400010002000000000000000000
if (exists key “HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation” of registry) then (value “DayLightStart” of key “HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation” of registry as string) else “None”
Q: name of operating system as lowercase is “win2000” and (value “TZI” of key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Eastern Standard Time” of registry) as string != “2c01000000000000c4ffffff00000b0000000100020000000000000000000300000002000200000000000000”
It won’t tell if if the vbscript has been run, but it will tell you if the registry keys have been imported. It’s really arbitrary which of the timezone values you compare. Either they are updated or they are not.
Thanks for your contributions on the board… Note that many BigFix customers either made their own Fixlets for unsupported Microsoft OSes or purchased fully supported BigFix Fixlets for all MS OSes that not only fix the issue on a single computer but allow you to fix the issue on all of their computers in their organizations.
I have deleted the 5 identical posts that you have posted elsewhere on this forum, but we can leave this one post here just in case users are interested in your solution. In the future, please do not spam our forum or use it as an advertisement medium.