Patch not applicable

Usage and Config Patch
1

(imported topic written by capricorn8091)

The product is not installed on windows and BigFix is reporting it as fail. The manual install of the patch dont work with pop up message saying The patch is not applicable.

If the product is not installed why BigFix report it?

How you can deal with such problem from computer point of view and any other solution?

Thanks.

2

(imported comment written by BenKus)

Hi capricorn,

Can you give us some info on which Fixlet is causing the issue (the Fixlet title and/or ID would help) and we can look into it…

Thanks!

Ben

3

(imported comment written by capricorn8091)

Hi Ben!

Thanks but unfortunately I am not the one who contains the Fixlet thats why I asked if I can troubleshoot it from computer side i.e. from client side.

I have seen the problem on many machines like the machine dont haave .Net 3.5 installed and BigFix is reporting missing patch for .Net 3.5.1. If i try to update the patch i get error that its not applicable.

Thanks.

4

(imported comment written by capricorn8091)

Is it not possible to do anything from client side or any suggestion?

5

(imported comment written by NoahSalzman)

What you are effectively saying is:

Someone told me something is wrong with our client? Can you fix it?

There are thousands of settings on your client that could be “fixed”. We have to have specifics to help. And, even with specific information about your client, we will still probably need to know the Fixlet ID that is causing the confusion.

6

(imported comment written by capricorn8091)

You are right but from my side the problem is i don’t have the Fixlet ID and its with BigFix Administrators. I can only see the report related to my machines and BigFix is pointing to fail for many machines with .Net 3.5.1 and when i try to install the mentioned patch windows is saying that its not applicable. Its a nightmare from support side who don’t have access to BigFix console and do the work from client side. May be its that corrupt patch methodology used by BigFix which is bad for us because its hard for support team to correct dll.

I know you people work from BigFix console end but i wanted to get help from client side where BigFix agent is installed and keep reporting many machines with missing patches when we cant even install that patch manually.

If its not possible to get any info without Fixlet ID than its fine.

Thanks.

7

(imported comment written by SystemAdmin)

If you look in the TEM Client logs, it might give you the FixletID.

I’m doing this from memory … Forgive me if the path is off a bit

C:\Program Files\BES Enterprise\BESClient__Global__Data\Logs

Once you get the FixletID, we can get the Relevance clauses for it and determine why it is showing relevant to your computer(s).