deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-27 16:23:36 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update upgrading-to-mbam-25-sp1-from-mbam-25.md

Browse Source 
updated article and links to point to the July 2018 hotfix release. Some minor language revisions.
This commit is contained in:
Jan Kulbe
2019-01-15 18:59:23 +01:00
committed by GitHub
parent b492888a82
commit 1eb19fd0e8
1 changed files with 16 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
mdop/mbam-v25/upgrading-to-mbam-25-sp1-from-mbam-25.md
View File

@ -13,32 +13,37 @@ ms.date: 2/16/2018
# Upgrading to MBAM 2.5 SP1 from MBAM 2.5
This topic describes the process for upgrading the Microsoft BitLocker Administration and Monitoring (MBAM) Server 2.5 and the MBAM Client from 2.5 to MBAM 2.5 SP1.
### Before you begin, download the September 2017 servicing release
[Desktop Optimization Pack](https://www.microsoft.com/en-us/download/details.aspx?id=56126)
### Before you begin
#### Download the July 2018 servicing release
[Desktop Optimization Pack](https://www.microsoft.com/en-us/download/details.aspx?id=57157)
#### Verify the installation documentaion
Verify you have a current documentation of your MBAM environment, including all server names, database names, service accounts and their passwords.
### Upgrade steps
#### Steps to upgrade the MBAM Database (SQL Server)
1. Using the MBAM Configurator; remove the Reports roll from the SQL server, or wherever the SSRS database is housed (Could be on the same server or different one, depending on your environment)
1. Using the MBAM Configurator; remove the Reports role from the SQL server, or wherever the SSRS database is hosted. Depending on your environment, this can be the same server or a separate one.
Note: You will not see an option to remove the Databases; this is expected.  
2. Install 2.5 SP1 (Located with MDOP - Microsoft Desktop Optimization Pack 2015 from the Volume Licensing Service Center site: <https://www.microsoft.com/Licensing/servicecenter/default.aspx>
3. Do not configure it at this time 
4. Install the September Rollup: https://www.microsoft.com/en-us/download/details.aspx?id=56126
5. Using the MBAM Configurator; re-add the Reports rollup
4. Install the July 2018 Rollup: https://www.microsoft.com/en-us/download/details.aspx?id=57157
5. Using the MBAM Configurator; re-add the Reports role
6. This will configure the SSRS connection using the latest MBAM code from the rollup 
7. Using the MBAM Configurator; re-add the SQL Database roll on the SQL Server.
- At the end, you will be warned that the DBs already exist and weren’t created, but this is  expected.
7. Using the MBAM Configurator; re-add the SQL Database role on the SQL Server.
- At the end, you will be warned that the DBs already exist and weren’t created, but this is expected.
- This process updates the existing databases to the current version being installed      
#### Steps to upgrade the MBAM Server (Running MBAM and IIS)
1. Using the MBAM Configurator; remove the Admin and Self Service Portals from the IIS server
2. Install MBAM 2.5 SP1
3. Do not configure it at this time  
4. Install the September 2017 Rollup on the IIS server(https://www.microsoft.com/en-us/download/details.aspx?id=56126)
4. Install the July 2018 Rollup on the IIS server(https://www.microsoft.com/en-us/download/details.aspx?id=57157)
5. Using the MBAM Configurator; re-add the Admin and Self Service Portals to the IIS server 
6. This will configure the sites using the latest MBAM code from the June Rollup
6. This will configure the sites using the latest MBAM code from the July 2018 Rollup
- Open an elevated command prompt, Type: **IISRESET** and Hit Enter.
#### Steps to upgrade the MBAM Clients/Endpoints
1. Uninstall the 2.5 Agent from client endpoints
2. Install the 2.5 SP1 Agent on the client endpoints
3. Push out the September Rollup Client update to clients running the 2.5 SP1 Agent 
4. There is no need to uninstall existing client prior to installing the September Rollup.  
3. Push out the July 2018 Rollup Client update to clients running the 2.5 SP1 Agent 
4. There is no need to uninstall the existing client prior to installing the July 2018 Rollup.