I'm trying to create a simple third party package that evaluates as applicable if a file is missing from the client workstation and as installed if the file exists, but the agent is not reporting the expected status of the package.
The size, version and date of the file are irrelevant and may change so I don't want to include them in the test. The problem I have is that if I leave the "Created Date" and "Modified Date" boxes disabled in the rule, the client reports not applicable and logs the following warning:
2013-10-31 09:42:07:652 1248 1ba0 Agent WARNING: Failed to evaluate Installed rule, updateId = {921C6E69-6344-4A56-9668-7D5051F14272}.1, hr = 80070002
2013-10-31 09:42:07:652 1248 1ba0 Agent WARNING: Failed to evaluate Installable rule, updateId = {921C6E69-6344-4A56-9668-7D5051F14272}.1, hr = 80070002
If I enable the check boxes with the default values (03/16/09 12:00:00 AM), then on a client where the file is missing, the warning isn't logged, but the package is still evaluated as not applicable instead of applicable/not installed. The agent returns the same result whether or not the parent folder exists on the client.
My rules are very simple.
Prerequisite:
<sdp:PrerequisiteRule SchemaVersion="1.0">
<bar:WindowsVersion Comparison="GreaterThanOrEqualTo"MajorVersion="5"MinorVersion="0"ServicePackMajor="4"ServicePackMinor="0"/>
</sdp:PrerequisiteRule>
Applicability:
<sdp:ApplicabilityRule SchemaVersion="1.0">
<lar:Not>
<bar:FileExists Path="C:\folder\subfolder\9.1.4.3.5.1-03.txt"/>
</lar:Not>
</sdp:ApplicabilityRule>
Installed:
<sdp:InstalledRule SchemaVersion="1.0">
<bar:FileExists Path="C:\folder\subfolder\9.1.4.3.5.1-03.txt"/>
</sdp:InstalledRule>
Interestingly, the packages seems to evaluate exactly as expected if the test file has a simple filename, such as "filename.txt", but something appears to go wrong if I use the example filename "9.1.4.3.5.1-03.txt". I don't know if this is due to the length (14+3 chars), or the multiple dots or something else.
Edit: Title changed to remove reference to file date - problem doesn't seem related to date attribute