It seems as though with the upgrade from 7.0.7.82 to 7.0.7.96 that we’ve lost the ability for our Baselines to be run. It appears as though it immediately determines Not Relevent and stops the Baseline in it’s tracks. This issue was exhibited during automation testing using our 7.0.7.82 client and console. After reading the forums and the hotfix lists… we were under the impression this was ‘fixed’ with the 7.0.7.96 version… After the upgrade we are still seeing the same issues.
It seems that a number of people might be having this issue, or other oddities around running multiple groups. We’ve tried to change out MIME settings and have used Relays or directly relaying form the BES Server… still all situations exhibit the same issue, Not Relevent.
The client logs appear to have some General Transport Failures, which we don’t remember being prevelent in the past (aside from one-off issues). Has anyone had any luck getting multiple actions to work?
Also, We’ve uncovered some links referring to watching for hotfixes, but they go to either bad links or pages with no hotfix information, has anyone formally logged the issue and have information on a hotfix?
Also, I would like to note that we have also noticed issues running BESRemoval, which in the past, has worked 100% of the time. Now with the 7.0.7.82 and 7.0.7.96 clients we see unclean removals and errors deleting the BES directories… It says that the uninstall failed, but the service is gone… most of the folder structure is gone, but some registry entries remain. We are using the BesRemoval 7.0.7.82 version…
We did have an issue in BES Client 7.0.7.82 in which multiple action groups would respond as “Not Relevant”, but the issue didn’t affect baselines. Just to be sure, I just ran a few tests using 7.0.7.96 BES Agents and baseline actions and everything seemed to be working fine. It sounds like it might be an issue specific to your deployment, but the best way to figure it out is for us to take a look at the issue with you and we can try to see if we can figure it out. To start this process, please open a support ticket with us and we will go from there.
I will also check the BES Remove tool and make sure we have it functioning properly.
Nice call on the removal… I do believe that we POC’d some of the dlp functions and it was causing an issue with the besremoval. it was not properly deleting the folder structure… we cleaned that up and it has since been resolved.
Also, we did open a case with support… we are working out the issues but are surely seeing Not Revelent Baseline issues with the 7.0.7.96 client. When we resolve the issue I will report back as to what is the cause.
We will update the BES Remove tool to properly clean up the BES Client Logging Service to make the life of everyone with BigFix AntiVirus, AntiSpyware, DLP, Firewall easier.
Update: Looks like this was resolved… and by resolved i mean explained! as it appears this was ‘by design’… the whole client version and server version is irrelevent, basically when running a baseline applicability is applied through the baseline relevence, but also, a job needs to be relevent. Our automation process is a policy action that is always running, waiting for a text file to be dropped for the job to start… what we need is a job within our baseline to be relevent (or moreso, a job to have this checked “Baseline will be relevant on applicable computers where this component is relevant”).
so yeah… looks like the issue was by design, just nothing that was really obvious to us! Thanks to BES Support… we got to the bottom of it and are moving forward!