The reason for the request is from this "adventure" I had last week:
I had spent about 3 days trying to setup the proper Installable, Installed rules for Trend Micro Officescan. I was only able to actually see the reason why Installable was false and Installed was false after I enabled debugging of the WSUS client service and hammered on the rules.
Turns out Trend Micro includes a installed & installable rule where the MSI code matches an existing code found it won't install despite the version of each package being different. Only after running a client in debugging did I see a package rule show up (didn't see them in the WSUS package Publisher publishing view, but then again I've never seen a package have rules already defined). I deleted the package rules during the initial publishing (the second time I published it) and it fixed that issue.
The second issue was a Reg_SZ key wasn't being evaluated when set to "equal" as opposed to "contains" when comparing the registry key against a DisplayVersion "10.6.5162". The debugging showed it completely fail attempting to validate the installed rule and instead report an error about the "C:\Program Files\Update Services\v4\xml" was corrupt on the client, which made no sense. In a blind guess I flipped it to "contains" and it successfully reported it matched therefor was installed already.
I had spent about 3 days trying to setup the proper Installable, Installed rules for Trend Micro Officescan. I was only able to actually see the reason why Installable was false and Installed was false after I enabled debugging of the WSUS client service and hammered on the rules.
Turns out Trend Micro includes a installed & installable rule where the MSI code matches an existing code found it won't install despite the version of each package being different. Only after running a client in debugging did I see a package rule show up (didn't see them in the WSUS package Publisher publishing view, but then again I've never seen a package have rules already defined). I deleted the package rules during the initial publishing (the second time I published it) and it fixed that issue.
The second issue was a Reg_SZ key wasn't being evaluated when set to "equal" as opposed to "contains" when comparing the registry key against a DisplayVersion "10.6.5162". The debugging showed it completely fail attempting to validate the installed rule and instead report an error about the "C:\Program Files\Update Services\v4\xml" was corrupt on the client, which made no sense. In a blind guess I flipped it to "contains" and it successfully reported it matched therefor was installed already.
