DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2831166 - Last Review: April 29, 2013 - Revision: 2.1

Symptoms

Consider the following scenario:

·  Microsoft BitLocker Administration and Monitoring (MBAM) 2.0 is installed in a System Center Configuration Manager Integrated topology.
·  MBAM is uninstalled from the System Center Configuration Manager server.
·  You attempt to reinstall MBAM on the System Center Configuration Manager server again.

In this scenario, the MBAM installer fails during the prerequisite check with the following error:

System Center CM Objects Already Installed

Cause

If MBAM 2.0 is removed from a System Center Configuration Manager server, the MBAM collection, reports, Configuration Items, and Configuration Baselines are not removed. When you attempt to reinstall MBAM on the server in a System Center Configuration Manager integrated topology, you will receive the error above during the installer's prerequisite check.

Resolution

To resolve the issue, manually remove the MBAM collection, reports, Configuration Items and Configuration Baselines from System Center Configuration Manager before reinstalling. To manually remove these objects, complete the steps below:

1. Delete the MBAM reports folder.

a. Open Internet Explorer on the server where MBAM was installed and browse to the SQL Server Reporting Services URL that System Center Configuration Manager is using for its Reporting Services Point.
b. Navigate to the appropriate System Center Configuration Manager report folder.
c. Locate the MBAM folder and delete it.

2. Delete the MBAM Supported Computers collection.

a. Open the System Center Configuration Manager Administrator Console.
b. Delete the MBAM Supported Computers collection.
i. Do not click “Delete Special” in System Center Configuration Manager 2007 when deleting the collection or all device resources will be removed.

ii. Do not check “Delete each collection member from the database” in System Center Configuration Manager 2012 when deleting the collection or all device resources will be removed.

3. Delete the BitLocker Protection Configuration Baseline.

Open the System Center Configuration Manager Administrator Console.
a. In System Center Configuration Manager 2007, delete the BitLocker Protection Configuration Baseline under Desired Configuration Management -> Configuration Baselines.
b. In System Center 2012 Configuration Manager, delete the BitLocker Protection Configuration Baseline under Assets and Compliance -> Compliance Settings -> Configuration Baselines.

4. Delete the BitLocker Fixed Data Drives Protection and BitLocker Operating System Drive Protection Configuration Items.

Open the System Center Configuration Manager Administrator Console.
a. In System Center Configuration Manager 2007, delete the BitLocker Fixed Data Drives Protection and BitLocker Operating System Drive Protection Configuration Items under Desired Configuration Management -> Configuration Items.
b. In System Center 2012 Configuration Manager, delete the BitLocker Fixed Data Drives Protection and BitLocker Operating System Drive Protection Configuration Items under Assets and Compliance -> Compliance Settings -> Configuration Items.
5. In System Center Configuration Manager 2007, delete entries from the CI_SDMPackages table in the System Center SQL database by using the following SQL command (replace ‘AAA’ with your System Center site code):

DELETE FROM [SMS_AAA].[dbo].[CI_SDMPackages] WHERE [SDMPackageName] LIKE ‘%ScopeId_MBAM%’

Once these items have been removed, re-run the MBAM server installer.

Optional
If you would like to clean up the MBAM hardware inventory classes, complete the steps below:

System Center Configuration Manager 2007

1. Delete the MBAM classes from configuration.mof and sms_def.mof (see the MBAM documentation for more information).      
The MOF files are normally located at:
%ProgramFiles(x86)%”\Microsoft Configuration Manager\inboxes\clifiles.src\hinv”
2. Download and install System Center Configuration Manager 2007 Toolkit V2: http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=9257 (http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=9257)
a. At an elevated command prompt, run the following command by changing the directory to the location where the System Center Configuration Manager 2007 Toolkit V2 is installed (usually %ProgramFiles(x86)%”\ConfigMgr 2007 Toolkit V2”):
cd %ProgramFiles(x86)%\"ConfigMgr 2007 Toolkit V2\ServerTools"
b. Run the Delgrp.exe tool to delete the MBAM class groups from the SQL database. After you run Delgrep.exe each time, restart the SMS_EXECUTIVE service by entering the following:
- DelGrp.Exe "MICROSOFT|MBAM_POLICY|1.0"
- sc stop SMS_EXECUTIVE
- sc start SMS_EXECUTIVE
- DelGrp.Exe "MICROSOFT|BITLOCKER_DETAILS|1.0"
- sc stop SMS_EXECUTIVE
- sc start SMS_EXECUTIVE

Note: Configuration Manager will take a few minutes to clean up the MBAM WMI classes from the SMS provider. Once the MBAM hardware inventory classes have been cleared, re-add them following the instructions in the MBAM documentation.


System Center 2012 Configuration Manager

1. Delete the MBAM classes from the configuration.mof file.
This file is generally located at:
%ProgramFiles%”\Microsoft Configuration Manager\inboxes\clifiles.src\hinv”
2. Delete the hardware inventory classes from the Default Client Settings by completing the following steps:
3. From the Client Settings node in the Configuration Manager console, select Default Client Settings and then click Properties on the Home ribbon.
4. Select Hardware Inventory and then click Set Classes.
5. Select each of the following classes, and then click Delete:

BitLocker Encryption Details (Win32_BitLockerEncryptionDetails)
BitLocker Policy (Win32Reg_MBAMPolicy)
Computer System Ex (CCM_ComputerSystemExtended)
Operating System Ex (CCM_OperatingSystemExtended)

6. Click OK.
Once the MBAM hardware inventory classes have been cleared, re-add them following the instructions in the MBAM documentation.

More information

For more information on MBAM and how it can help you in your environment, please see the following:

Getting Started with MBAM 2.0: http://go.microsoft.com/fwlink/?LinkId=275639 (http://go.microsoft.com/fwlink/?LinkId=275639)
Planning for MBAM 2.0: http://go.microsoft.com/fwlink/?LinkId=286874 (http://go.microsoft.com/fwlink/?LinkId=286874)
Deploying MBAM 2.0: http://go.microsoft.com/fwlink/?LinkId=288850 (http://go.microsoft.com/fwlink/?LinkId=288850)
Operations for MBAM 2.0: http://go.microsoft.com/fwlink/?LinkId=288851 (http://go.microsoft.com/fwlink/?LinkId=288851)
Troubleshooting MBAM 2.0: http://go.microsoft.com/fwlink/?LinkId=288852 (http://go.microsoft.com/fwlink/?LinkId=288852)
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

Applies to
  • Microsoft BitLocker Administration and Monitoring 2.0
  • Microsoft System Center 2012 Configuration Manager
  • Microsoft System Center 2012 Configuration Manager Service Pack 1
  • Microsoft System Center Configuration Manager 2007
  • Microsoft System Center Configuration Manager 2007 R2
  • Microsoft System Center Configuration Manager 2007 R3
  • Microsoft System Center Configuration Manager 2007 Service Pack 1
  • Microsoft System Center Configuration Manager 2007 Service Pack 2
Keywords: 
KB2831166
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support