Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Problem with Installed Rules

I have created a package with the latest client of VMware Horizon View. The problem is that Windows Update on the local computer I have approved the update on, don't understand that VMware is already installed. I run Windows update and I see the VMware Horizon View client, I install it, restart the computer and run Windows update again, Windows update will install the update again! I think that is my "Installed rules" not working. what am I doing wrong?

Here is my installed rule:

Installed rules.JPG

And here is the properties of the file from Windows Explorer:

File version.JPG

Find more posts tagged with

installed_rules

vmware_client_install

Accepted answers

LGarvin

Okay... a false positive for Needing the update is a completely different consideration from not recognizing the package as Installed.

What is the actual state of the update package displayed in the console: [1] Installed, [2] Not Installed, or [3] Not Applicable

Also, please confirm via the WindowsUpdate.log that the WUA has actually evaluated the current revision and is not still reporting state on an earlier revision.

In the WindowsUpdate,log, find the most recent entry for the update package of this form:

2014-04-20 00:23:49:457 1072 2f08 Agent * Added update {B8879058-1915-4DD6-970E-CFC9528FA2D5}.201 to search result

Specifically, the value after the decimal point following the GUID tells us the Revision Number of the package that was evaluated.

Verify that matches the most recent revision number published to the WSUS server.

If the current revision is the one being evaluated, then in the Package Wizard,

for each of the rulesets (Prerequisite, Applicability, Installed), click on the View XML button and copy/paste the XML for each ruleset.

All comments

LGarvin

Right on the money with the analysis, Johan. This is certainly a problematic Installed Rule.

The issue exists in the Common Path and Path value. Due to an implementation issue with our XML generator, failing to define a COMMON_PATH results in the inclusion of an undefined attribute in the underlying XML, which confuses the Windows Update Agent.

In order to reference the Program Files (x86) folder, regardless of the rule type, it must be back-pathed from the defined PROGRAM_FILES common path.

Reference it in the Rule Editor by the following:

Set Common Path = "PROGRAM_FILES"

Set Path = "..\Program Files (x86)\and_the_rest_of_the_path

So, specifically for your example, the dialog should look like this:

4-24-2014 12-58-19 PM.png

johan.sjogren

Thanks for your quick reply. I change the installed rules and add 2 .. in the beginning, saved it and published again but Windows updates still saying that the computer need the update.

Med vänlig hälsning / Best regards

Johan Sjögren

IT Department

Redovisning<www.accountor.se/.../101>, Elektronisk fakturahantering<www.accountor.se/.../92>, Lönehantering<www.accountor.se/.../96>

Accountor AB

Box 1126 SE 111 81 STOCKHOLM

Visitors: Dalagatan 100, 9tr

Direct: +46 (0)8 506 116 66

Sms:

Office: +46 (0)8 506 116 00

Fax: +46 (0)8 506 116 16

www.accountor.se<http://www.accountor.se>

Från: Lawrence Garvin

Skickat: den 24 april 2014 20:00

Till: Sjögren Johan

Ämne: Re: - Problem with Installed Rules

thwack<thwack.solarwinds.com/>

Problem with Installed Rules

reply from Lawrence Garvin<thwack.solarwinds.com/.../LGarvin in Patch Manager - View the full discussion<thwack.solarwinds.com/.../234793

LGarvin

Okay... a false positive for Needing the update is a completely different consideration from not recognizing the package as Installed.

What is the actual state of the update package displayed in the console: [1] Installed, [2] Not Installed, or [3] Not Applicable

Also, please confirm via the WindowsUpdate.log that the WUA has actually evaluated the current revision and is not still reporting state on an earlier revision.

In the WindowsUpdate,log, find the most recent entry for the update package of this form:

2014-04-20 00:23:49:457 1072 2f08 Agent * Added update {B8879058-1915-4DD6-970E-CFC9528FA2D5}.201 to search result

Specifically, the value after the decimal point following the GUID tells us the Revision Number of the package that was evaluated.

Verify that matches the most recent revision number published to the WSUS server.

If the current revision is the one being evaluated, then in the Package Wizard,

for each of the rulesets (Prerequisite, Applicability, Installed), click on the View XML button and copy/paste the XML for each ruleset.