How to Completely Uninstall and Remove Client Management from your environment

Version 3
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Client Management


    Client Management


    All Versions of Client Management (formerly known as Footprints Asset Core)


    How do I completely uninstall and remove BMC Client Management from my environment?


    If you are looking to no longer use BMC Client Management, you will need to uninstall the agent from all of your devices.  The easiest way to do this is to use the Agent Rollout Wizard and create an "Uninstall" rollout - just select that from the dropdown on the first screen.  

    Uninstall Rollout - Rollout Wizard Screen 1

    Then on the second screen, change the name to reflect that it is an "Uninstall Rollout for BCM".

    Uninstall Rollout - Rollout Wizard Screen 2

    Then you can assign this rollout to all of your Client and Relay devices and add the admin credentials for a user that has permissions to uninstall on all your devices - ***Just be sure you do not assign it to your Master server.***

    Uninstall Rollout - Rollout Wizard Screen 3

    You may also need to confirm that there is nothing configured to automatically install the agent on devices that do not have it installed....This would be something like an "Unmanaged Devices" device group assigned to a Rollout.  If it remains assigned to that rollout, as soon as you uninstall the agent, it will most likely meet the criteria of that device group, and then the agent will automatically get reinstalled.  

    I also recommend going to the Rollout URL (https://MasterServerName or RolloutServerName:1610/rollout the login as the an administrator in the Console who has permissions to access Rollouts - you can download the Uninstall Rollout from that website so you have it in case you miss uninstalling on devices that may not be accessible before you decommission the Master server.  This .exe can just be run on any Windows device from a network share or a USB flash drive.  

    Rollout URL

    If you are trying to uninstall from a Mac OS device or Linux device, you will need to create an "Uninstall" rollout for those OS's and then either add those devices as targets to "push" the Uninstall Rollout to them - keeping in mind the 'root' account and SSH must be enabled on the devices and the 'root' account credentials must be used when configuring the Uninstall Rollout.  If you do not want to enable the 'root' account, then you will need to "pull" the Uninstall Rollout by downloading the file and running the following commands.  

    You can also download an executable which will install the agent. If you are unable to configure your devices to meet the prerequisites above (for example devices for work at home users which are not directly accessible from the rollout server), you must use this method to install the agent.

    • Windows installation/uninstall     
      1. Once the download of the rollout installer has completed, double click the downloaded .exe file to install the agent.
      3. On systems where Windows User Account Control is enabled, it may be necessary to right click the downloaded .exe file, and select "Run as Administrator" to install the agent.
    • Linux Installation/uninstall     
      1. Once the agent installer has been downloaded open a terminal window, and change into the directory where the rollout installer has been downloaded.
      3. Enter "chmod +x ROLLOUT_FILE_NAME" (where ROLLOUT_FILE_NAME is the name of the installer you downloaded from the rollout server).
      5. Enter "sudo ./ROLLOUT_FILE_NAME" to start the installation.
    • MacOS installation/uninstall                    
      • Method 1 (recommended for installing the agent on small numbers of devices)
      2. Once the agent installer has been downloaded open a terminal window (HD > Applications > Utilities > Terminal), and change into the directory where the rollout installer has been downloaded.
      4. Enter "chmod +x ROLLOUT_FILE_NAME" (where ROLLOUT_FILE_NAME is the name of the installer you downloaded from the rollout server).
      6. Enter "sudo ./ROLLOUT_FILE_NAME" to start the installation. You can also start the installation by double clicking the file in the Finder.
      • Method 2 (recommended for installing the agent on larger numbers of devices)
      1. Follow steps 1 and 2 under the above Method 1 section. After this, you should have a rollout file which has been marked as executable.
      3. Open the Disk Utility application (HD > Applications > Utilities > Disk Utility)
      5. Click the New Image button in the toolbar
      7. Configure the disk image as shown below, and click create. 
      9. Copy the agent installer downloaded from the rollout server to the newly created disk image.
      11. The image can now be unmounted, and sent to your users.
      13. Once received by your users, they would need to double click the disk image, then double click the agent installer file to start the installation.
    Once all of your agents have been uninstalled from your Clients and your Relays, then you can decide if you are ready to uninstall the Master or if you just want to disable the BMC Client Management Agent service on the Master.  If the service is disabled, it will not run, but it could be started at a later date if you need historical data.   

    Before you uninstall the Master, I do recommend that you confirm in the Vision64datbase.ini file where the database is located so you can decommission that as well - you may even just want to make a copy of this file to save for later.  This file is typically located in:    
      C:\Program Files\BMC Software\FootPrints Asset Core\Master\config  
      C:\Program Files\BMC Software\Client Management\Master\config

    depending on which version you initially installed on the Master.

    If you do not have any need for historical data, you can go to the Control Panel>Programs and Features and uninstall the BMC Client Management Console and BMC Client Management application from there.

    Lastly you will have a database to be decommissioned.  This may be on a separate server or it may be on the same server - all of that information is located in that Vision64database.ini file I referred to above.  You will need your database administrator to decommission the database after the Client Management application has been uninstalled from the Master and you know you have no need to go back to it for historical data.












    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles