Export the Custom Definition (XML) and post it. That'll help give us an idea of what your detection logic is, perhaps that is where the problem is.
<ExportableContainer xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" LastSavedBy="yhdomain\kf8314" Revision="0" SourceCore="YHSVRLANDESK1" Guid="fake" SaveType="Inherit">
<Exportable xsi:type="EVulnerability" LastSavedBy="yhdomain\kf8314" Revision="720909" SourceCore="YHSVRLANDESK1" Guid="INTL_Paragon9.4.624" SaveType="Inherit">
<Title>Paragon PCR 9.4.624</Title>
<Patch Download="DManual" Silent="CRSYes" Reboot="RNo" UniqueFilename="*Paragon9.4.624_Rule 1" Hash="" Size="0">
<Arg N="dest" V="C:\Program Files\Paragon94" />
<Arg N="source" V="%SDMCACHE%%PATCHFILENAME%" />
Didn't notice you were on v9, I'm still on 8.
So... it won't let me import the file.
If I am reading this right, you are checking for a file, and if it's not there the patch is needed? Are you just checking that it's there, or date/time, etc, basically what is your detection rule?
What's inside the ZIP file? Are these just files that you have to copy over and that's it, the patch is done, or is something else needed?
Yes, as long as the text file is present, then the patch is "applied".
The ZIP file just contains a bunch of flat files that may or may not overwrite existing files. Included is the text file that the definition is looking for. Nothing else is required once that is done.
So if v9 is anything like v8, when you kick off the task, it should create a task log file in the "%programfiles%\ldclient\data" folder. Can you check to see if that file is there, and post it?
The file name will include the Task ID number, to narrow it down.
Not exactly the detail I was hoping for.
Give me a bit and I'll see if I can think of anything else.
The only other thing I can think of is to see if it's the destination of the files that is causing the problem.
Try changing your destination of the extracted files to "%temp%\Paragon" (without quotes) and see if the patch works.
It should put it in the local users temp folder, you can access it by going to the Run command and typing %temp%\paragon.
I tried changing the destination to %TEMP%\Paragon as you suggested and it still fails immediately, same result code 412. Nice idea though!
Well... perhaps the LANDesk extraction tool is having a problem. What are you using to ZIP the file(s)? Try manually extracting the files, re-zip them using WinZip or even the built-in Windows zip function. Update the hash for the patch (if you are using it) and try again.
I'd even just try creating a new custom def.
I just don't know what the 412 error is.
I figured out what the problem was...
I had specified the patch file location using the "Additional Files" section and providing a UNC path to the file. I remembered that patches need to run using the HTTP section. Once I did it that way, the patch worked 100% with no problem.
Thanks for your assistance!
patch.jpg 109.0 K
Sweet. Good work.