1 of 1 people found this helpful
there should be logs in the RSCD install dir on the target under Transactions/logs named like bldeploy-blah-blah. look in there and see if you can find out why it failed, or look at the job run log in the GUI and see why it failed.
also when you say 'compliance job fails' do you mean that the complaince job failed a condition of a rule or that the job errored out in some way?
are you using any custom properties in the blpackage?
The compliance job did fail - but more accurately it was the installation of the one software deployment that failed.
Looking back over my set up, I found that of the three (3) BLPackages I created for software deployment, two (2) of them were "soft-linked" and one was not - the one that always failed. I dug into the windows logs on the target server and found an error from the msi installer - a missing file.
I recreated that one BLPackage - and this time "soft-linked" it and re ran the compliance job -- and now it works.
So it appears the the soft-link is important for compliance jobs as not all of the installation package gets sent during auto-remediation.
Go figure. Thanks anyway Bill - you are helpful as always.