Skip navigation

Client Management

3 Posts authored by: Julien Devienne Employee
Share:|

This article will reference cumulative hotfixes (OneOff) for BMC Client Management and updates for Atrium Integrator every time a new one will be released and until this idea has been implemented..

 

Note that the release notes actually only list the latest hotfixes that were added to this cumulative hotfix but that all the previously released hotfixes for the major version you are using will also be included in it. Check the previous release notes to find out which hotfixes are also in the cumulative hotfix you will be applying.

 

 

BMC Client Management 12.8

- Patch 1 - 181122n (2018, Nov): Release Note

 

BMC Client Management 12.7

- Hotfix 2- 180813o (2018, Oct): Release Note

 

BMC Client Management 12.6

- Hotfix 4 - 180813m (2018, Oct): Release Note

 

BMC Client Management 12.5

- Hotfix 9 - 180913l (2018, Oct): Release Note

 

BMC Client Management 12.1

- Hotfix 7 - 180214j (2018, Feb): Release Note [Important Update - make sure you read the release notes]

 

 

Atrium integrator

- 1.7 - 180531r - No release note yet

 

Note: do not forget to vote for this idea: New Hotfix/Update released - email notification

Share:|

This article intends to explain the software inventory basics, in order to teach you how to customize at the end. Download the complete documentation on our support site and read BMCFPAssetCore_InventoryManager.pdf (p.34 in the 11.7 doc) for more details about this filter.

 

The default software inventory filter is composed by "Filter Definitions" and "Cleaning Filters". Filter definitions will collect the value without checking if it's worthless, then the module will pass the resulting list through the cleaning filters to clean the results from, as an example, too many version numbers or to clean it up from executables that do not have any product name, manufacturer or version set in their details.

 

 

1- Create a new software inventory filter:

 

It might be easier to follow this article this way:

- Hardware and software inventory filters can be edited and created in the subnode "Global Settings" > "Inventory Filters" > "Software Inventory".

- Right click on the subnode or on the right window and select "Create filter"

Sans titre.png

Note that this filter is the same than the filter that is already set on all the devices you have deployed if you have never assigned a new one to these.

 

 

 

2- Filter Definitions:


Filter definitions will collect all applications it will find and that matches a certain patern when scanning the path you have set in the devices' software module configuration or that you have set in the step you use to scan your devices.

 

This filter must always be the last filter definition of the list. Filters that'd collect dll, exe and ocx that you'd add after will not be taken in consideration.

 

Edit the "Main Filter":

- In the "General" tab you will set the name of the filter and weither it accepts datas or reject them.

main_general.png

If it's set to "Reject" it'll reject the applications that match the "MATCHFILE tag".

If it's set to "Accept" it will collect the application that match the "MATCHFILE tag", then pass it on to the "Cleaning Filters"

 

- In the "MATCHFILE Tag" tab you'll set what the filter is supposed to match on:

main_match.png

This filter is supposed to collect all the exe, dll and ocx files it'll find (column "Value") in any path that is set either in the software inventory module or in the step you use to collect it.

 

- In the "CREATE Tag" tab you'll set what what you to output when the "MATCHFILE tag" has matched on something:

main_create.png

As you can see, the "Main Filter" will:

-  read values from the executable details for the "Tag Names":

- "NAME" -> "Product Name"

- "MANUFACTURER"

- "VERSION" -> "File Version" or "Product Version"

- not write anything in the field "DESCRIPTION"

- set the type "Application"

 

 

 

3- Cleaning Filters:

 

Once the module has collected applications, the module will clean the results using these filters. This is usefull to clean false postives but can also exclude applications or informations that you'd want to appear in your devices' software inventories.

 

Some cleaning filters won't exclude your application but they will clean some datas out such as the number of digits in the application version numbers.

 

A lot of customers need to list more than two digits so I have written this document to explain how to edit a cleaning filter to not to clean less than two digits. It will hopefully help you understand how these work.

 

 

 

4- Assign your new software inventory filter:

 

Once a new filter is created you have to assign it to the target devices to update the existing filter. If you don't, they'll keep using the older.


Beware as you might have inconsistent results if you only send this filter to some devices only and/or that you don't assign it to newly deployed devices. I'd assign a dynamic group containing all your devices to that new software inventory filter to make sure to avoid this kind of issue.


assign.png

 

 

5- Update your software inventory

 

The software inventory can be updated using two methods:

 

- the software inventory module configuration

module.png

You can set up the module to scan the device at every startup, or every two days without having to assign and schedule an operational rule to your device.

It'll probably be more efficient to call support to learn more about this, so i won't give more details here except if you ask.


- the step:

step.png

You can assign one of the dedicated "Out of the Box" operational rule and schedule it to run once a day maybe. Do not schedule it more often, it's rarely needed and can use bandwith for nothing.

 

Both methods will allow you to decide to:

- scan Add/Remove Programs, the MSI database. This is not mandatory, you can decide to scan directories only.

- include/exclude directories to scan

- limit the type of file extensions you want to scan. Do not set an extension that is not set in any definition filter.

- scan hidden directories, files or not

 

It's recommended to use the "Differential Upload" method to lower bandwith usage. If you don't check this check box the device qill upload a complete inventory everytime, instead of only sending the difference with the previous one.

 

 

 

5- Troubleshooting:


Check the target device's logs:

 

The best thing to understand why your application is not listed in your software inventory is to:

- select a test device

- enable full logs on it

- update its software inventory

- edit the logs and filter for keywords such as "SoftwareInventory*_YOUR_APP_.exe*rejected" or something like that and check the results

 

5-1 Rejected by a definition filter:

 

A- Details missing in the executable properties:

 

Some cleaning filters will totally exclude your application because the manufacturer did not set all the informations required by the "Main filter": "NAME", "MANUFACTURER", "VERSION".

To check the executable details, simply right click on the executable then click on the tab "Details":

details.png

You won't be able to see all the informations we collect on this tab, but it might help you find out why the application is not included in your device's software inventory. As an example the "Company" tag, used to fill the tag name "MANUFACTURER", is not visible here but i can see it when i pass the mouse on the exe.

 

To fix this kind of issue, you will have to create a specific filter to accept it such as the "Mozilla Firefox" filter:

def_moz_filt.png

As you can see this filter will not try to read the "NAME" from the executable" because it's not set in the executable details. This document should help you fix this kind of issue.

 

 

 

B- Check the logs:

 

2014/01/23 19:54:28 SoftwareInventory                I   [238020] File 'C:\Windows\System32\wbem\wbemtest.exe' has been rejected by filter 'system32'

 

This shows that the application "wbemtest.exe" has been rejected by the filter definition "system32":

def_filt_system32.png

If you want to collect it anyway, you will have to either:

- create a definition filter that'll accept it specifically and put it before the "system32" definition filter.

- delete the definition filter "system32" but this will have a big impact on your software inventories which will get a lot bigger.

 

 

5-2 Rejected by a cleaning filter:

 

2014/01/23 19:54:29 SoftwareInventory                I   [238020] Application 'Microsoft® HTML Help Executable' has been rejected by filter 'Remove bad names 1'

 

This shows that the application 'Microsoft® HTML Help Executable' has been reject by the cleaning filter 'Remove bad names 1'.

 

remove_bad_names2.png

If you want to collect it anyway, you will have to edit the definition filter "Remove bad names 1" and delete "|(HTML Help)" at the end of the column "Data".

 

 

5-3 The 'Google Update Setup' case:

 

This example is interesting because:

- the filter definition "Google Chrome" might make you think it'll collect it:

chrome_filter_def.png

But it won't, except if it's stored in a path containing "Google\Chrome" (note the escape caracter).

- it'll pass the definition filter "Main Filter as all informations required are set in the exe details

- it will be cleaned up by the cleaning filter "setup" beucause it's a setup program, not an installed application, which you can also see in the logs:

 

2014/01/23 19:54:30 SoftwareInventory                I   [238020] Application 'Google Update Setup' has been rejected by filter 'setup'

 

 

 

6- Enhance your software inventory filter:

 

I'm actually writting a document to help you achieve this.  I'll post it soon.

Share:|

This article will cover steps to upgrade BCM (ex Footprints Asset Core) to a new version then to a new one off version if available. It will be updated and enhanced from time to time.

 

Note that you'll also find information on how to upgrade in the documentations BCM_WindowsInstallation.pdf

(p.29 in the 12.0 doc) or BCM_LinuxInstallation.pdf (p.23 in the 12.0 doc). These documentations can be downloaded from our support website.

You will also find a lot of up to date documentation on the BCM wiki pages.

 

It's pretty simple to upgrade to a new FPAC version, this document will try to cover all the steps you need to go through in order to be successful.

Neither the master, the relays or the clients will have to be reinstalled: the master will be upgraded using an executable and the devices will be upgraded using provided operational rules.

 

I highly suggest that you make a copy of your OSD manager ../data/OSDeployment folder before you upgrade it, just in case. This article will give you more information about upgrading when you own the OSD module.

 

 

0- Prerequisites and pre-upgrade tests:

 

A- Check the new prerequisites:

 

It is possible that the OS of your master, or the version of your database engine or even the OS of your clients are not supported anymore in the newest version.

This is very important as some of our customers had issues in previous upgrades because they did not realize that MS SQL 2000 was not supported anymore when they upgraded, as well as Windows 2000 Server that was installed on another customer relays etc.

 

Prerequisites can be checked in the BCM_TechSpecs_Brochure_12_0_us.pdf documentation available on the support site.


This article will list which versions can be upgraded to which versions.

 

 

B- Test it on a test environment:

 

It is more than advised to create a test environment to avoid bad surprises. The best is to setup strict copies of the typical devices you are going to upgrade:

- Create a test master.

- Create test relays and clients.

- Create a copy of your OSD manager and test the upgrade on it. This copy can be made as described in this document.

 

It is important to create strict copies because that's how you might encounter issues that our QA hasn't encountered during the test sessions, in lab environments. This will help find bugs they did not replicate before the release and should prevent you from having issues right after going live.

 

 

 

1- Upgrade your licence:

 

If you do not have a licence valid for the version you want to upgrade to you will have to upgrade it on the support's website.

Note that 11.x licences are compatible with each others but not with 12.x licenses.

 

This document will help you upgrade and download your new license if you do not already have one in this new major version.

 

 

 

2- Download the upgrade packages:

 

You will need to create an account to download these. You will be able to download them from:

- the menu "Product Updates" or from the tab "BMC Client Management (Asset Core)"

support_dl.png

 

- from the BMC EPD website

EPD.png

This document will give you more information on how to download from the EPD website. If you don't have an account yet, this one will help you create one.

 

Select the update installer corresponding to your master and to its architecture and download it.

 

You might find some more information on this page.

 

 

 

3- Create new tablespaces:

 

This should be handled by the upgrade installer but you might want or you might have to create new tablespaces and grant new rights to the database user, depending on which version you are upgrading from.

You will find more information about these scripts in the documentation:

- v12.0 BCM_WindowsInstallation.pdf, p.34 and it subsections or on this page.

- v12.1: Preparing for upgrade - BMC Client Management 12.1 - BMC Documentation

 

Attention: the account you will specify to create these new tablespaces etc must be the same that the account specified in the file Vision64database.ini that you will find in the install folder of your master. If you don't you'll end up with new and upgraded objects being owned by another user and you will have to revert to backups.

 

 

 

4- Clean up the console:

 

It's advised to clean the console from old upgrade and one-off operational rules and packages prior to upgrading.

if you don't clean these up before you upgrade to a new major version (or update to a new one-off version) you might end-up with corrupted upgrade operational rules.

 

 

 

5- Upgrade the master:

 

This article will cover an upgrade of a windows or a linux master.

 

Recommendations:

- to reduce risks I'd only recommend to check the option "Upgrade your agent installations after this server upgrade is finished" if you have already validated the upgrade on a test environment.

- you can avoid to check the option "Back up Master installation directory" if you have daily backups or if you can make a snapshot before upgrading.

Warning: backups and snapshots must always be performed when the agent's service is stopped. If not, files might be corrupted.

- JRE 7 is a prerequisite in 11.7 and following, check the option "Install Java Runtime Environment 1.7" if it's not already installed on the master. JRE 8 can be used as well in 12.0 and 12.1

 

 

 

6- Upgrade your consoles:

 

- Install JRE 7 or JRE 8 (depending on the version you're upgrading to) on all the devices where the console must be installed/upgraded

- update the console by either:

- connect to the master using your old console. It should tell you it's too old and ask you if you want to upgrade it

- connect to the master's http://MASTER:PORT/console and download the java webstart console or the regular console.

"MASTER" is your master'name or ip, "PORT" is the agent's port, usually it's 1610.

You might find some more information on upgrading consoles on this page.

 

 

 

7- Upgrade the relays:

 

First upgrade the relays, then upgrade the clients only once their relay is upgraded. This is very important if you want to maximize the compatibility.

 

 

 

8- List all operational rules that contain steps that need to be updated:

 

Upgrades do not update the version of steps that are set in operational rules before the upgrade. This can prevent some operational rules to work successfully, as before the upgrade. This document will help you identify the steps that may cause issues.

 

 

 

9- Eventually repackage some packages:

 

The script install.chl that is used to install packages is not updated in existing packages. If you want the new version of the script to be included in your package you need to recreate a package from scratch.

Most of the time you won't need to create a new package, but I've seen issues in 12.0 where existing packages would not work on windows 8.1 which was newly supported.

I'd suggest that you only test this package by package when you see a package failing after an upgrade.

 

 

10- Apply the latest cumulative hotfix available

 

Cumulative hotfixes are not hosted on our old support site, they are now hosted on EPD. You will find more information on this in this document. There you'll be able to download the upgrade files for your master and for the clients. Please select the upgrade package corresponding to the OS/Architecture of your master.

Then you should read the release note available on the wiki. As an example this page is dedicated to the cumulative hotfixes release notes for 12.1.

 

Attention: Please pay extra attention to the eventual notes you'll find on the release note as there might be very important information such as the fact that applying the v12.0 cumulative hotfix implies to update your Footprints Service Core installation as well, because of the OpenSSL update:

NOTE:

This update for Client Management 12.0 may cause issues with the integration between Asset Core and Service Core; specifically the new version of OpenSSL included in this Asset Core update may not be compatible with the version of OpenSSL used by Service Core. In order for the integration to work correctly, the OpenSSL version used by Service Core must also be updated, and instructions for this update are available in article

TIA07295

 

Follow this document to learn how to apply cumulative hotfixes.

 

 

11- [DEPRECATED from 12.0 included] Update the rollout configurations:

 

This do not apply if you run v12.0 included and following as they will be updated automatically, starting from v12.0.

Note that this step is not mandatory, you can update your new clients after they are installed by a rollout, it'll simply use extra bandwidth/time.

 

 

 

12- OSD Updates:

 

- Unassign winpe drivers that are not windows 8.1 drivers from your projects:

12.1 ships with ADK 8.1, this implies that OS Deployment drivers must now be compatible with Windows 8.1.

Delete the uncompatible windows 7 drivers then either:

- rebuild the project and test it without os deployment drivers. Do not add windows 8.1 os deployment drivers to the project if it works

- replace the old drivers by the new 8.1 drivers and rebuild the project

 

- Upload your drivers by model:

This only applies if you set the alternate method to select your drivers and that you are upgrading to a version 12.1 and following.

 

The drivers you have set in your project folders will not be picked up by the alternate method after you will have upgraded to 12.1 and following. You will have to import them by model in the OSD module configuration. See the documentation for more information.

 

 

 

13- Upgrade nmap:

 

If you use the asset discovery module you should consider upgrading nmap on your scanners. Actually if you want to be able to discover windows 10 properly, there are chances that you must upgrade to nmap 7 (or following). You will find the path where it's installed in your scanner's configuration.

Filter Blog

By date:
By tag: