Difference between revisions of "MBAM Architecture"
From RiceFamily Wiki
| Line 6: | Line 6: | ||
: https://technet.microsoft.com/en-us/library/dn645312.aspx | : https://technet.microsoft.com/en-us/library/dn645312.aspx | ||
: The Monitoring Web Service is no longer available in Microsoft BitLocker Administration and Monitoring (MBAM) 2.5 SP1 since the MBAM Client and the websites communicate directly with the Recovery Database. | : The Monitoring Web Service is no longer available in Microsoft BitLocker Administration and Monitoring (MBAM) 2.5 SP1 since the MBAM Client and the websites communicate directly with the Recovery Database. | ||
| − | : I wonder if this means that all the MBAM Client machines need access to the MBAM Database server. If so it will require a new Firewall Rule be implemented for the VRF that the server is in. | + | : ''I wonder if this means that all the MBAM Client machines need access to the MBAM Database server. If so it will require a new Firewall Rule be implemented for the VRF that the server is in.'' |
Revision as of 12:02, 6 April 2016
Overview
We are going to be setting up a "Stand-Alone" MBAM environment and using BigFix in place of Microsoft's SCCM to deploy the clients and gather status from endpoints.
Notes
- MBAM Monitoring Web Service no longer available
- https://technet.microsoft.com/en-us/library/dn645312.aspx
- The Monitoring Web Service is no longer available in Microsoft BitLocker Administration and Monitoring (MBAM) 2.5 SP1 since the MBAM Client and the websites communicate directly with the Recovery Database.
- I wonder if this means that all the MBAM Client machines need access to the MBAM Database server. If so it will require a new Firewall Rule be implemented for the VRF that the server is in.
