Should have investigated this before I posted. I found this on the current blapp server:
Should I point the Patch Global Configuration to that? The name is slightly different than I expected, so I don't know if it's the same thing.
The modified date is from a few weeks before we upgraded to 8.5, so even if this is it, I don't believe it's the newest version.
1 of 1 people found this helpful
I don't think you should need to override the buit in product_categories for BSA 8.5.
I would suggest removing the Windows Filter Configuration File entry in Patch Global Configuration and test - if you see any "No Mapping" type messages in Catalog Update Job Run Log then get back to us or raise a support ticket with the details.
Thanks & Regards,
Okay, thanks. That makes sense, so I did remove it as you suggested. I ran the catalog update job and I got a few "no mapping" errors. Specifically for Visio 2007, Project 2007 and Project 2010, for whatever reason.
I'm more concerned that I still don't see Office 2013 listed, which is what got me checking this in the first place. I read that there is an updated xml that can be imported for 8.2 and 8.3, but I thought I understood that Office 2013 would be included in the filters with BSA version 8.5.
Sent PM with an updated file to try.
Thanks, that seemed to do it. I now see Office 2013. Tonight our weekly catalog update job will run, so I'll wait until after it runs to check, but I am confident I'll see Office 2013 patches as well as the Project and Vision ones.
I don't know if there is a recommended place to store the XML, but I placed it here on the blapp server:
I assume that should be okay. As I said it works, but that catalog directory normally only contains sub-directories for catalog versions.
You can store the file any place where it is accessible by the Console => Patch Global Configuration dialog.
We just upgraded Server Automation to version 188.8.131.52. We have been using an override file named xxxx_2014_03_20.xml as the Windows Filter Configuration file. I'm guessing that I should simply leave the Windows Filter Configuration File field blank, so that it uses the default product_categories for this version of Server Automation.
Thanks in advance for a confirmation or different recommendation.
1 of 1 people found this helpful
Upgraded from what version?
Best choice right now id probably to leave it blank, and then if you see ""No mappings were found for the selected product" messages, go to OS Patching Vendor Health Dashboard
That page has current health and a link to the most up to date BMC created Windows Filter Configuration file.
The override file I was using was put in place while we were at 184.108.40.2061, but we were at an interim build in between, which I think was 8.5 with SP1.
Anyway, thanks Jim and Joe for the link to the XMLs. I'll use the latest one after testing to see if using none is 100% successful.
The default product_categories for 220.127.116.11 still gave "No mappings found..." errors. I used product_categories_1.3.xml, which is the latest and that solved the issue.
Would you be able to provide details?
- What is in your filter selection?
- What appeared in the "No Mappings" messages?
Using the default product_categories for 18.104.22.168, SkyDrive Pro 2013 was the only product to show "No mappings". I believe that was corrected in the second newest version of the XML.
As for the filter selection, are you asking which products we have selected for patching? If so, there are a lot of them, but only Microsoft products are included. The application owners are responsible for patching non-MS products and Exchange.
Thanks Charlie :-)