diff --git a/mdop/mbam-v25/generating-mbam-25-stand-alone-reports.md b/mdop/mbam-v25/generating-mbam-25-stand-alone-reports.md index 7d9df908fd..13ae4fd9fb 100644 --- a/mdop/mbam-v25/generating-mbam-25-stand-alone-reports.md +++ b/mdop/mbam-v25/generating-mbam-25-stand-alone-reports.md @@ -30,7 +30,7 @@ To run the reports, you must be a member of the **MBAM Report Users** group, whi   -**To open the Administration and Monitoring Website** +**To open the Administration and Monitoring Website** 1. Open a web browser and navigate to the Administration and Monitoring Website. The default URL for the Administration and Monitoring Website is: @@ -47,7 +47,7 @@ To run the reports, you must be a member of the **MBAM Report Users** group, whi   -**To generate an Enterprise Compliance Report** +**To generate an Enterprise Compliance Report** 1. From the Administration and Monitoring Website, select the **Reports** node from the left navigation pane, select **Enterprise Compliance Report**, and select the filters that you want to use. The available filters for the Enterprise Compliance Report are: @@ -61,7 +61,7 @@ To run the reports, you must be a member of the **MBAM Report Users** group, whi 4. Select the plus sign (+) next to the computer name to view information about the volumes on the computer. -**To generate a Computer Compliance Report** +**To generate a Computer Compliance Report** 1. From the Administration and Monitoring Website, select the **Report** node from the left navigation pane, and then select **Computer Compliance Report**. Use the Computer Compliance Report to search for **User name** or **Computer name**. @@ -74,9 +74,7 @@ To run the reports, you must be a member of the **MBAM Report Users** group, whi **Note**   An MBAM client computer is considered compliant if the computer matches or exceeds the requirements of the MBAM Group Policy settings. -   - -**To generate a Recovery Key Audit Report** +**To generate a Recovery Key Audit Report** 1. From the Administration and Monitoring Website, select the **Report** node in the left navigation pane, and then select **Recovery Audit Report**. Select the filters for your Recovery Key Audit Report. The available filters for recovery key audits are as follows: diff --git a/mdop/mbam-v25/how-to-recover-a-moved-drive-mbam-25.md b/mdop/mbam-v25/how-to-recover-a-moved-drive-mbam-25.md index 609ec18b52..a0d1d62844 100644 --- a/mdop/mbam-v25/how-to-recover-a-moved-drive-mbam-25.md +++ b/mdop/mbam-v25/how-to-recover-a-moved-drive-mbam-25.md @@ -11,8 +11,6 @@ ms.prod: w10 # How to Recover a Moved Drive - - This topic explains how to use the Administration and Monitoring Website (also referred to as the Help Desk) to recover an operating system drive that was moved after being encrypted by Microsoft BitLocker Administration and Monitoring (MBAM). When a drive is moved, it no longer accepts the PIN that was used in the previous computer because the Trusted Platform Module (TPM) chip has changed. To recover the moved drive, you must obtain the recovery key ID to retrieve the recovery password. To recover a moved drive, you must use the **Drive Recovery** area of the Administration and Monitoring Website. To access the **Drive Recovery** area, you must be assigned the MBAM Helpdesk Users role or the MBAM Advanced Helpdesk Users role. For more information about these roles, see [Planning for MBAM 2.5 Groups and Accounts](planning-for-mbam-25-groups-and-accounts.md#bkmk-helpdesk-roles). @@ -20,10 +18,7 @@ To recover a moved drive, you must use the **Drive Recovery** area of the Admini **Note**   You may have given these roles different names when you created them. For more information, see [Access accounts for the Administration and Monitoring Website (Help Desk)](#bkmk-helpdesk-roles). -  - **To recover a moved drive** - 1. On the computer that contains the moved drive, start the computer in Windows Recovery Environment (WinRE) mode, or start the computer by using the Microsoft Diagnostic and Recovery Toolset (DaRT). 2. After the computer has been started with WinRE or DaRT, MBAM will treat the moved operating system drive as a fixed data drive. MBAM will then display the drive’s recovery password ID and ask for the recovery password. diff --git a/mdop/mbam-v25/planning-for-mbam-25-groups-and-accounts.md b/mdop/mbam-v25/planning-for-mbam-25-groups-and-accounts.md index e651abbd0b..6515783c38 100644 --- a/mdop/mbam-v25/planning-for-mbam-25-groups-and-accounts.md +++ b/mdop/mbam-v25/planning-for-mbam-25-groups-and-accounts.md @@ -103,7 +103,7 @@ Create the following accounts for the Reports feature.   -## Administration and Monitoring Website (Help Desk) accounts +## Administration and Monitoring Website (Help Desk) accounts Create the following accounts for the Administration and Monitoring Website. diff --git a/mdop/medv-v2/how-to-add-or-remove-url-redirection-information-in-a-deployed-med-v-workspace.md b/mdop/medv-v2/how-to-add-or-remove-url-redirection-information-in-a-deployed-med-v-workspace.md index 544141d6d3..51bf199255 100644 --- a/mdop/medv-v2/how-to-add-or-remove-url-redirection-information-in-a-deployed-med-v-workspace.md +++ b/mdop/medv-v2/how-to-add-or-remove-url-redirection-information-in-a-deployed-med-v-workspace.md @@ -29,7 +29,7 @@ You can add and remove URL redirection information by performing one of the foll - [Edit the URL Redirection Text File and Rebuild the MED-V Workspace](#bkmk-edittext) -**To update URL Redirection information by using Group Policy** +**To update URL Redirection information by using Group Policy** 1. Edit the registry key multi-string value that is named `RedirectUrls`. This value is typically located at: @@ -44,7 +44,7 @@ This method of editing URL redirection information is a MED-V best practice.   -**To rebuild the MED-V workspace by using an updated URL text file** +**To rebuild the MED-V workspace by using an updated URL text file** - Another method of adding and removing URLs from the redirection list is to update the URL redirection text file and then use it to build a new MED-V workspace. You can then redeploy the MED-V workspace as before, by using your standard process of deployment, such as an ESD system. diff --git a/mdop/medv-v2/how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system.md b/mdop/medv-v2/how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system.md index 171a89953e..202fcf0954 100644 --- a/mdop/medv-v2/how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system.md +++ b/mdop/medv-v2/how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system.md @@ -47,21 +47,15 @@ You must install the MED-V workspace packager and build your MED-V workspaces be 3. **MED-V Host Agent Installation File** – installs the Host Agent (MED-V\_HostAgent\_Setup installation file). For more information, see [How to Manually Install the MED-V Host Agent](how-to-manually-install-the-med-v-host-agent.md). **Warning**   - Close Internet Explorer before you install the MED-V Host Agent, otherwise conflicts can occur later with URL redirection. You can also do this by specifying a computer restart during a distribution. - -   + Close Internet Explorer before you install the MED-V Host Agent, otherwise conflicts can occur later with URL redirection. You can also do this by specifying a computer restart during a distribution.   4. **MED-V Workspace Installer, VHD, and Setup Executable** – created in the **MED-V Workspace Packager**. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). **Important**   The compressed virtual hard disk file (.medv) and the Setup executable program (setup.exe) must be in the same folder as the MED-V workspace installer. Then, install the MED-V workspace installer by running setup.exe. -   - **Tip**   - Because problems that can occur when you install MED-V from a network location, we recommend that you copy the MED-V workspace setup files locally and then run setup.exe. - -   + Because problems that can occur when you install MED-V from a network location, we recommend that you copy the MED-V workspace setup files locally and then run setup.exe.   3. Configure the packages to run in silent mode (no user interaction is required). @@ -70,15 +64,11 @@ You must install the MED-V workspace packager and build your MED-V workspaces be **Note**   Installation of Windows Virtual PC requires you to restart the computer. You can create a single installation process and install all the components at the same time if you suppress the restart and ignore the prerequisites necessary for MED-V to install. You can also do this by using command-line arguments. For an example of these arguments, see [To install the MED-V components by using a batch file](#bkmk-batch). MED-V automatically starts when the computer is restarted. -   - 4. Install MED-V and its components before installing Windows Virtual PC. See the example batch file later in this topic. **Important**   Select the **IGNORE\_PREREQUISITES** option as shown in the example batch file so that the MED-V components can be installed prior to the required VPC components. Install the MED-V components in this order to allow for the single restart. -   - 5. Identify any other requirements necessary for the installation and for your software distribution system, such as target platforms and the free disk space. 6. Assign the packages to the target set of computers/users. @@ -91,7 +81,7 @@ You must install the MED-V workspace packager and build your MED-V workspaces be First time setup starts and might take several minutes to finish, depending on the size of the virtual hard disk that you specified and the number of policies applied to the MED-V workspace on startup. The end user can track the progress by watching the MED-V icon in the notification area. For more information about first time setup, see [MED-V 2.0 Deployment Overview](med-v-20-deployment-overview.md). -**To install the MED-V components by using a batch file** +**To install the MED-V components by using a batch file** 1. Run the installation at a command prompt with administrative credentials. diff --git a/mdop/uev-v2/prepare-a-ue-v-2x-deployment-new-uevv2.md b/mdop/uev-v2/prepare-a-ue-v-2x-deployment-new-uevv2.md index a97b55540e..886b343e52 100644 --- a/mdop/uev-v2/prepare-a-ue-v-2x-deployment-new-uevv2.md +++ b/mdop/uev-v2/prepare-a-ue-v-2x-deployment-new-uevv2.md @@ -45,7 +45,7 @@ This workflow diagram provides a high-level understanding of a UE-V deployment a ![deploymentworkflow](images/deploymentworkflow.png) -**Planning a UE-V deployment:** First, you want to do a little bit of planning so that you can determine which UE-V components you’ll be deploying. Planning a UE-V deployment involves these things: +**Planning a UE-V deployment:** First, you want to do a little bit of planning so that you can determine which UE-V components you’ll be deploying. Planning a UE-V deployment involves these things: - [Decide whether to synchronize settings for custom applications](#deciding)