Share via

Upgrading to MBAM 2.5 from Previous Versions

  • Artikel

Gäller för: Microsoft BitLocker Administration and Monitoring 2.5

This topic describes the process for upgrading the Microsoft BitLocker Administration and Monitoring (MBAM) Server and the MBAM Client from earlier versions of MBAM.

Upgrade support for MBAM 2.5 Server infrastructure

This section lists the supported scenarios and high-level steps for upgrading to the MBAM 2.5 Server.

Supported version for upgrade Process for upgrading to the MBAM 2.5 Server

MBAM 1.0
  1. Uninstall all MBAM 1.0 Server features.

  2. On the database server, install MBAM 2.0 SP1, and select only the database features.

  3. From the database server, uninstall MBAM 2.0 SP1.

  4. Install MBAM 2.5 on each server where you want to configure an MBAM feature.

MBAM 2.0
ImportantViktigt
For the Configuration Manager Integration feature only, you upgrade MBAM from 2.0 to 2.5; do not upgrade this feature to 2.0 SP1 from 2.0. The Configuration Manager objects (baseline, MBAM Supported Computers collection, and reports) will be upgraded to MBAM 2.5 in place.

  1. Uninstall all MBAM 2.0 Server features.

  2. On the database server, install MBAM 2.0 SP1, and select only the database features.

  3. From the database server, uninstall MBAM 2.0 SP1.

  4. Install MBAM 2.5 on each server where you want to configure an MBAM feature.

MBAM 2.0 SP1
  1. Uninstall all MBAM 2.0 SP1 Server features.

  2. Install MBAM 2.5 on each server where you want to configure an MBAM feature.

Before you start the upgrade

Review the following information before you start the upgrade.

What to know before you start Details

After uninstalling all MBAM Server features from your current installation, you will install only the MBAM databases for each subsequent upgrade, until you are ready to install MBAM 2.5.

You don’t install the reports and web applications for each upgrade because you don’t need them until you install MBAM 2.5. When upgrading to MBAM 2.5, you will install and configure all MBAM 2.5 Server features.

If you are installing the MBAM websites on one server and the web services on another server, you have to use Windows PowerShell cmdlets to configure them.

The MBAM Server Configuration wizard does not support configuring the websites on one server and the web services on a different server.

If you are upgrading to MBAM 2.5 from MBAM 2.0 or MBAM 2.0 SP1 in Windows Server 2008 R2:

The Administration and Monitoring Website and the Self-Service Portal will not work if you install the required .NET Framework 4.5 software after Internet Information Services (IIS) is already installed.

This issue occurs because ASP.NET cannot be registered correctly with IIS if the .NET Framework is installed after IIS has already been installed.

To resolve this issue:

Run aspnet_regiis –i from the following location:

C:\windows\microsoft.net\Framework\v4.0.30319

For more information, see: ASP.NET IIS Registration Tool.

Register an SPN on the application pool account if all of the following are true:

  • You are upgrading from a previous version of MBAM.

  • Currently, you are not running the MBAM websites in a load-balanced or distributed configuration, but you would like to do so when you upgrade to MBAM 2.5.

For instructions, see Registering an SPN when you are upgrading from previous versions of MBAM.

 

What we recommend

Register a service principal name (SPN) for the application pool account, even though you may already have registered SPNs for the machine account.

Why we recommend it

Registering an SPN on the application pool account is required to configure the websites in a load-balanced or distributed configuration.

What happens if SPNs are already configured on a machine account?

MBAM will use the SPNs that you have already registered, and you don’t need to configure additional SPNs, but you are not able to configure the websites in a load-balanced or distributed configuration.

Steps to upgrade the MBAM Server infrastructure

Use the steps in the following sections to upgrade MBAM for the Stand-alone topology or the System Center Configuration Manager Integration topology.

To upgrade the MBAM Server infrastructure for Stand-alone topology

  1. Remove the web applications to ensure they cannot write information to the databases. For instructions, see Removing MBAM Server Features.

  2. Back up your databases.

  3. Uninstall the previous version of MBAM by using Windows Installer or through Programs and Features.

    noteAnm
    The databases will not be removed, and all compliance and recovery data is maintained in the database.

  4. Refer the table presented earlier in this topic, and follow the supported upgrade path to install MBAM 2.5. The databases are upgraded in place.

  5. Optionally, update the Group Policy Objects (GPOs), and edit the settings if you want to implement new features in MBAM 2.5, such as enforced encryption. If you do not update the GPOs, MBAM will continue to report against your current GPOs.

    After you upgrade the MBAM 2.5 Server infrastructure, the existing client computers continue to successfully report to the MBAM 2.5 Server, and recovery data continues to be stored.

  6. Deploy MBAM 2.5 Client. Client computers do not need to be rebooted after the deployment.

To upgrade the MBAM infrastructure for System Center Configuration Manager Integration topology

  1. Remove the web applications to ensure they cannot write information to the databases. For instructions, see Removing MBAM Server Features.

  2. Back up your databases.

  3. Uninstall the previous version of MBAM by using Windows Installer or through Programs and Features.

    noteAnm
    The databases and the Configuration Manager objects (baseline, MBAM supported computers collection, and Reports) will not be removed, and all compliance and recovery data is maintained in the database.

  4. Update the .mof files.

  5. Refer to the table presented earlier in this topic, and follow the supported upgrade path to install MBAM 2.5. The databases and Configuration Manager objects are upgraded in place.

  6. Optionally, update the Group Policy Objects (GPOs), and edit the settings if you want to implement new features in MBAM 2.5, such as enforced encryption. If you do not update the GPOs, MBAM will continue to report against your current GPOs.

    After you upgrade the MBAM 2.5 Server infrastructure, the existing client computers continue to report to the MBAM 2.5 Server successfully, and recovery data continues to be stored.

  7. Deploy the MBAM 2.5 Client. Client computers do not need to be rebooted after the deployment.

Upgrade support for the MBAM Client

MBAM supports upgrades to the MBAM 2.5 Client from any earlier version of the MBAM Client.

Ways to install the MBAM Client:

  • Upgrade the computers running MBAM Client all at once or gradually after you install the MBAM 2.5 Server infrastructure.

  • Install the MBAM Client through an electronic software distribution system or through tools such as Active Directory Domain Services or System Center Configuration Manager.

Got a suggestion for MBAM?

Add or vote on suggestions here. For MBAM issues, use the MBAM TechNet Forum.

Se även

Andra resurser

Deploying MBAM 2.5
Deploying the MBAM 2.5 Client
Configuring the MBAM 2.5 Server Features