Table of contents
TOC
Collapse the table of content
Expand the table of content

MBAM 1.0 Deployment Prerequisites

jamiejdt|Last Updated: 6/16/2016
|
1 Contributor

Before you begin the Microsoft BitLocker Administration and Monitoring (MBAM) Setup, make sure that you meet the necessary prerequisites to install the product. This section contains information to help you successfully prepare your computing environment before you deploy the MBAM Clients and Server features.

Installation prerequisites for MBAM Server features

Each of the MBAM server features has specific prerequisites that must be met before they can be successfully installed. MBAM Setup verifies if all prerequisites are met before the installation starts.

Installation prerequisites for Administration and Monitoring Server

The following table contains the installation prerequisites for the MBAM Administration and Monitoring Server:

PrerequisiteDetails

Windows ServerWeb Server Role

This role must be added to a server operating system supported for the mbam Administration and Monitoring Server feature.

Web Server (IIS) Management Tools

IIS Management Scripts and Tools

Web Server Role Services

Common HTTP Features:

  • Static Content

  • Default Document

Application Development:

  • ASP.NET

  • .NET Extensibility

  • ISAPI Extensions

  • ISAPI Filters

Security:

  • Windows Authentication

  • Request Filtering

Windows Server Features

Microsoft .NET Framework 3.5.1 features:

  • .NET Framework 3.5.1

  • WCF Activation

    • HTTP Activation

    • Non-HTTP Activation

Windows Process Activation Service

  • Process Model

  • .NET Environment

  • Configuration APIs

Note
For a list of supported operating systems, see MBAM 1.0 Supported Configurations.

Installation prerequisites for the Compliance and Audit Reports

The Compliance and Audit Reports must be installed on a supported version of SQL Server. Installation prerequisites for this feature include SQL Server Reporting Services (SSRS).

SSRS must be installed and running during MBAM server installation. SSRS should also be configured in “native” mode, not in the “unconfigured” or “SharePoint” mode.

Note
For a list of supported operating systems and SQL Server versions, see MBAM 1.0 Supported Configurations.

Installation prerequisites for the Recovery and Hardware Database

The Recovery and Hardware Database must be installed on a supported version of SQL Server.

SQL Server must have Database Engine Services installed and running during the MBAM server installation. The Transparent Data Encryption (TDE) feature must be enabled.

Note
For a list of supported operating systems and SQL Server versions, see MBAM 1.0 Supported Configurations.

The TDE SQL Server feature performs real-time input/output (I/O) encryption and decryption of the data and log files. TDE protects data that is "at rest,” which include the data and the log files. It provides the ability to comply with many laws, regulations, and guidelines that are established in various industries.

Note
Because TDE performs real-time decryption of database information, the recovery key information will be visible if the account under which you are logged in has permissions to the database when you view the recovery key information SQL tables.

Installation prerequisites for the Compliance and Audit Database

The Compliance and Audit Database must be installed on a supported version of SQL Server.

SQL Server must have Database Engine Services installed and running during MBAM server installation.

Note
For a list of supported operating systems and SQL Server versions, see MBAM 1.0 Supported Configurations.

Installation prerequisites for MBAM Clients

The necessary prerequisites that you must meet before you begin the MBAM Client installation are the following:

  • Trusted Platform Module (TPM) v1.2 capability

  • The TPM chip must be turned on in the BIOS and it must be resettable from the operating system. For more information, see the BIOS documentation.

Warning
Ensure that the keyboard, mouse, and video are directly connected to the computer, instead of to a keyboard, video, mouse (KVM) switch. A KVM switch can interfere with the ability of the computer to detect the physical presence of hardware.

Planning to Deploy MBAM 1.0

MBAM 1.0 Supported Configurations

© 2016 Microsoft