Microsoft Enterprise Platforms Support: Windows Server Core Team
EPS Team Blogs
Product Team Blogs
There have been situation where you as a MBAM Admin had to delete the entries of older/reimaged machine records from the MBAM compliance database. The only solution in this case was to run complex SQL queries to delete machines from the database. This tool helps you report the true state of encryption compliance in your environment by deleting the obsolete information from the MBAM Compliance Status database.
This is a command line tool which enables you to schedule it stale data deletion as a task to automate deletion of obsolete machine records from the MBAM compliance database.
This tool provides three different ways to delete machine records from the MBAM Compliance Status database:
1. Delete machines which have not reported in last X days.
2. Delete machines specified in a comma separated list via command line.
3. Delete machines specified in a text file.
This tool doesn’t delete the recovery information or any other data from MBAM Recovery and Hardware Database. All delete operations are performed strictly on the MBAM Compliance Status Database.
This tool is available for download from the TechNet website http://gallery.technet.microsoft.com/MBAM-Compliance-Data-9b4c950d as a self-extractable compressed file, which includes the executable and documentation.
This tool and documentation are provided "as-is". You bear the risk of using it. No express warranties, guarantees or conditions are provided. The tool supplied in this document is not supported under any Microsoft standard support program or service. However, you can report issues and bugs in the comments section on this page. Microsoft will, at its sole discretion, address issues and bugs reported.
Windows Core Team
I am always happy when Microsoft releases new tools, however I can't keep from wondering a bit about this statement in the blog: “Hope this tool helps you report the true state of encryption compliance in your environment by deleting the obsolete information
from the database.”
Do I somehow misread this or did MBAM have known problems reporting the compliance state before this tool got available? If so, do there happen to be other "well-known issues" pending fixes?
We are currently running a project to implement MBAM, but this just leaves me puzzled. One of the basic reasons for implenting MBAM is the compliance reporting; simple reimaging as it happens multiple times a day in a larger company should not cause inconsistancy
in the first place.