Difference between revisions of "Microsoft Bitlocker Administration and Monitoring"
From RiceFamily Wiki
(→Documentation) |
(→Important Request Numbers) |
||
| Line 2: | Line 2: | ||
* RITM1029531 | * RITM1029531 | ||
* RITM1029532 | * RITM1029532 | ||
| + | * TASK1461055 (Firewall Rules) | ||
= Documentation = | = Documentation = | ||
Revision as of 15:01, 17 March 2016
Contents
Important Request Numbers
- RITM1029531
- RITM1029532
- TASK1461055 (Firewall Rules)
Documentation
- MBAM 2.5 Server Prerequesites for Stand-alone and Configuration Manager Integration Topologies
- MBAM 2.5 Supported Configurations
- Deploying MBAM 2.5 in a stand-alone configuration
- How to Deploy the MBAM Client to Desktop or Laptop Computers
- YouTube video - Deploying Microsoft BitLocker Administration and Monitoring (MBAM) 2.5
- MBAM YouTube Play List
Installation Process
Request Servers
- MBAM Server (RITM1029531)
- MS-SQL Server (RITM1029532)
- MBAM Test Environment Installation Process
Install Pre-Requesites
- Install Powershell 3.0
- Install Microsoft Server 2008R2 or later with Service Packs
- Need to include SQL_Latin1_General_CP1_CI_AS collation.
- Install Database Engine
- Install Reporting Services
- Install Client Tools Connectivity
- Install Management Tools - Complete
MBAM Installation and Configuration
Client Installation
Important Notes
- According to How to Deploy the MBAM Client to Desktop or Laptop Computers
- "The MBAM Client does not start BitLocker Drive Encryption actions if a remote desktop protocol connection is active. All remote console connections must be closed and a user must be logged on to a physical console session before BitLocker Drive Encryption begins."
- MBAM Clients will communicate with the server via port 443
