mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 11:53:37 +00:00
Merge branch 'master' into metadata-fixes
This commit is contained in:
@ -240,5 +240,6 @@
|
||||
###### [AGPM Server Connection Settings](agpm-server-connection-settings.md)
|
||||
###### [Feature Visibility Settings](feature-visibility-settings.md)
|
||||
##### [Other Enhancements to the GPMC](other-enhancements-to-the-gpmc.md)
|
||||
## [Troubleshooting AGPM Upgrades](troubleshooting-agpm40-upgrades.md)
|
||||
## [Resources for AGPM](resources-for-agpm.md)
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Advanced Group Policy Management
|
||||
description: Advanced Group Policy Management
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: 493ca3c3-c3d6-4bb1-9430-dc1e43c86bb0
|
||||
ms.pagetype: mdop
|
||||
ms.mktglfcycl: manage
|
||||
|
41
mdop/agpm/troubleshooting-agpm40-upgrades.md
Normal file
41
mdop/agpm/troubleshooting-agpm40-upgrades.md
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Troubleshooting AGPM Upgrades
|
||||
description: Troubleshooting AGPM Upgrades
|
||||
author: jedodson
|
||||
ms.assetid: 1abbf0c1-fd32-46a8-a3ba-c005f066523d
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: jedodson
|
||||
ms.pagetype: mdop
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
# Troubleshooting AGPM Upgrades
|
||||
|
||||
This section lists common issues that you may encounter when you upgrade your Advanced Group Policy Management (AGPM) server to a newer version (e.g. AGPM 4.0 to AGPM 4.3). To diagnose issues not listed here, it may be helpful to view the [Troubleshooting AGPM](troubleshooting-agpm-agpm40.md) or for an AGPM Administrator (Full Control) to use logging and tracing. For more information, see [Configure Logging and Tracing](configure-logging-and-tracing-agpm40.md).
|
||||
|
||||
## What problems are you having?
|
||||
|
||||
- [Failed to generate a HTML GPO difference report (Error code 80004003)](#bkmk-error-80004003)
|
||||
|
||||
### <a href="" id="bkmk-error-80004003"></a>Failed to generate a HTML GPO difference report (Error code 80004003)
|
||||
|
||||
- **Cause**: You have installed the AGPM upgrade package with an incorrect account.
|
||||
|
||||
- **Solution**: You will need to be an AGPM administrator in order to fix this issue.
|
||||
|
||||
- Ensure you know the username & password of your **AGPM service account**.
|
||||
|
||||
- Log onto your AGPM server interactively as your AGPM service account.
|
||||
|
||||
- This is critically important, as the install will fail if you use a different account.
|
||||
|
||||
- Shutdown the AGPM service.
|
||||
|
||||
- Install the required hotfix.
|
||||
|
||||
- Connect to AGPM using an AGPM client to test that your difference reports are now functioning.
|
@ -73,11 +73,11 @@ When this has been completed, install the App-V 4.5 SP2 Clients by using Setup.m
|
||||
|
||||
When installing Microsoft Application Error Reporting, use the following command if you are installing or upgrading to the App-V 4.5 SP2 Desktop Client:
|
||||
|
||||
** msiexec /i dw20shared.msi APPGUID={C6FC75B9-7D86-4C44-8BDB-EAFE1F0E200D} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus**
|
||||
**msiexec /i dw20shared.msi APPGUID={C6FC75B9-7D86-4C44-8BDB-EAFE1F0E200D} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus**
|
||||
|
||||
Alternatively, if you are installing or upgrading to the App-V 4.5 SP2 Client for Remote Desktop Services (formerly Terminal Services), use the following command:
|
||||
|
||||
** msiexec /i dw20shared.msi APPGUID={ECF80BBA-CA07-4A74-9ED6-E064F38AF1F5} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus**
|
||||
**msiexec /i dw20shared.msi APPGUID={ECF80BBA-CA07-4A74-9ED6-E064F38AF1F5} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus**
|
||||
|
||||
**Note**
|
||||
- The APPGUID parameter references the product code of the App-V Clients that you install or upgrade. The product code is unique for each Setup.msi. You can use the Orca Database Editor or a similar tool to examine Windows Installer files and determine the product code. This step is required for all installations or upgrades to App-V 4.5 SP2.
|
||||
|
@ -156,7 +156,7 @@ Instead of changing the AppFS key FILENAME value every time that a new cache fil
|
||||
|
||||
3. On the VDI Master VM Image, open a Command Prompt window by using the **Run as administrator** option and grant remote link permissions so that the VM can access the symbolic link on the VDI Host operating system. By default, remote link permissions are disabled.
|
||||
|
||||
** fsutil behavior set SymlinkEvaluation R2R:1**
|
||||
**fsutil behavior set SymlinkEvaluation R2R:1**
|
||||
|
||||
**Note**
|
||||
On the storage server, appropriate link permissions must be enabled. Depending on the location of link and the Sftfs.fsd file, the permissions are **L2L:1** or **L2R:1** or **R2L:1** or **R2R:1**.
|
||||
|
@ -167,7 +167,7 @@ Instead of modifying the AppFS key FILENAME value every time that a new cache fi
|
||||
|
||||
3. On the VDI Master VM Image, open a Command Prompt window by using the **Run as administrator** option and grant remote link permissions so that the VM can access the symbolic link on the VDI Host operating system. By default, remote link permissions are disabled.
|
||||
|
||||
** fsutil behavior set SymlinkEvaluation R2R:1**
|
||||
**fsutil behavior set SymlinkEvaluation R2R:1**
|
||||
|
||||
**Note**
|
||||
On the storage server, appropriate link permissions must be enabled. Depending on the location of link and the Sftfs.fsd file, the permissions are **L2L:1** or **L2R:1** or **R2L:1** or **R2R:1**.
|
||||
|
@ -13,52 +13,42 @@ ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
# How to Manually Install the Application Virtualization Client
|
||||
|
||||
|
||||
There are two types of Application Virtualization Client components: the Application Virtualization Desktop Client, which is designed for installation on desktop computers, and the Application Virtualization Client for Remote Desktop Services (formerly Terminal Services), which you can install on Remote Desktop Session Host (RD Session Host) servers . Although the two client installer programs are different, you can use the following procedure to manually install either the Application Virtualization Desktop Client on a single desktop computer or the Application Virtualization Client for Remote Desktop Services on a single RD Session Host server. In a production environment, you most likely will install the Application Virtualization Desktop Client on multiple desktop computers with an automated scripted installation process. For information about how to install multiple clients by using a scripted installation process, see [How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md).
|
||||
|
||||
**Note**
|
||||
1. If you are installing the Application Virtualization Client for Remote Desktop Services software on a RD Session Host server, advise users who have an open RDP or ICA client session with the RD Session Host server that they must save their work and close their sessions. In a Remote Desktop session, you can install the client the client manually. For more information about upgrading the client, see [How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md).
|
||||
|
||||
2. If you have any configuration on the user’s computer that depends on the client install path, note that the Application Virtualization (App-V) 4.5 client uses a different install folder than previous versions. By default, a new install of the Application Virtualization (App-V) 4.5 client will install to the \\Program Files\\Microsoft Application Virtualization Client folder. If an earlier version of the client is already installed, installing the App-V client will perform an upgrade into the existing installation folder.
|
||||
|
||||
1. If you are installing the Application Virtualization Client for Remote Desktop Services software on a RD Session Host server, advise users who have an open RDP or ICA client session with the RD Session Host server that they must save their work and close their sessions. In a Remote Desktop session, you can install the client the client manually. For more information about upgrading the client, see [How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md).
|
||||
|
||||
2. If you have any configuration on the user’s computer that depends on the client install path, note that the Application Virtualization (App-V) 4.5 client uses a different install folder than previous versions. By default, a new install of the Application Virtualization (App-V) 4.5 client will install to the \\Program Files\\Microsoft Application Virtualization Client folder. If an earlier version of the client is already installed, installing the App-V client will perform an upgrade into the existing installation folder.
|
||||
|
||||
**Note**
|
||||
For App-V version 4.6 and later, when the App-V client is installed, SFTLDR.DLL is installed in the Windows\\system32 directory. If the App-V client is installed on a 64-bit system, SFTLDR\_WOW64.DLL is installed in the Windows\\SysWOW64 directory.
|
||||
|
||||
|
||||
|
||||
**To manually install Application Virtualization Desktop Client**
|
||||
|
||||
1. After you have obtained the correct installer archive file and saved it to your computer, make sure you are logged on with an account having administrator rights on the computer and double-click the file to expand the archive.
|
||||
1. After you have obtained the correct installer archive file and saved it to your computer, make sure you are logged on with an account having administrator rights on the computer and double-click the file to expand the archive.
|
||||
|
||||
2. Choose the folder in which to save the files, and then open the folder after the files have been copied to it.
|
||||
2. Choose the folder in which to save the files, and then open the folder after the files have been copied to it.
|
||||
|
||||
3. Review the Release Notes if appropriate.
|
||||
3. Review the Release Notes if appropriate.
|
||||
|
||||
4. Browse to find the setup.exe file, and double-click setup.exe to start the installation.
|
||||
4. Browse to find the setup.exe file, and double-click setup.exe to start the installation.
|
||||
|
||||
5. The wizard checks the system to ensure that all prerequisite software is installed, and if any of the following are missing, the wizard will automatically prompt you to install them:
|
||||
5. The wizard checks the system to ensure that all prerequisite software is installed, and if any of the following are missing, the wizard will automatically prompt you to install them:
|
||||
|
||||
- Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
|
||||
- Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
|
||||
|
||||
- Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)
|
||||
- Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)
|
||||
|
||||
- Microsoft Application Error Reporting
|
||||
- Microsoft Application Error Reporting
|
||||
|
||||
**Note**
|
||||
For App-V version 4.6 and later, the wizard will also install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86).
|
||||
|
||||
For more information about installing Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), see <https://go.microsoft.com/fwlink/?LinkId=150700> (https://go.microsoft.com/fwlink/?LinkId=150700).
|
||||
For more information about installing Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), see [https://go.microsoft.com/fwlink/?LinkId=150700](https://go.microsoft.com/fwlink/?LinkId=150700).
|
||||
|
||||
|
||||
|
||||
~~~
|
||||
If prompted, click **Install**. Installation progress is displayed, and the status changes from **Pending** to **Installing**. Installation status changes to **Succeeded** as each step is completed successfully.
|
||||
~~~
|
||||
If prompted, click **Install**. Installation progress is displayed, and the status changes from **Pending** to **Installing**. Installation status changes to **Succeeded** as each step is completed successfully.
|
||||
|
||||
6. When the **Microsoft Application Virtualization Desktop Client – InstallShield Wizard** is displayed, click **Next**.
|
||||
|
||||
@ -76,88 +66,66 @@ If prompted, click **Install**. Installation progress is displayed, and the stat
|
||||
|
||||
12. On the **Application Virtualization Data Location** screen, click **Next** to accept the default data locations or complete the following actions to change where the data is stored:
|
||||
|
||||
1. Click **Change**, and then browse to or, in the **Global Data Location** field, enter the destination folder for the global data location, and click **OK**. The Global Data Directory is where the Application Virtualization Desktop Client caches data shared by all users on the computer, like OSD files and SFT file data.
|
||||
1. Click **Change**, and then browse to or, in the **Global Data Location** field, enter the destination folder for the global data location, and click **OK**. The Global Data Directory is where the Application Virtualization Desktop Client caches data shared by all users on the computer, like OSD files and SFT file data.
|
||||
|
||||
2. If you want to change the drive letter to be used, select the preferred drive letter from the drop-down list.
|
||||
2. If you want to change the drive letter to be used, select the preferred drive letter from the drop-down list.
|
||||
|
||||
3. Enter a new path to store the user-specific data in the **User-specific Data Location** field if you want to change the data location. The User Data Directory is where the Application Virtualization Desktop Client stores user-specific information, like personal settings for virtualized applications.
|
||||
3. Enter a new path to store the user-specific data in the **User-specific Data Location** field if you want to change the data location. The User Data Directory is where the Application Virtualization Desktop Client stores user-specific information, like personal settings for virtualized applications.
|
||||
|
||||
**Note**
|
||||
This path must be different for every user, so it should include a user-specific environment variable or a mapped drive or something else that will resolve to a unique path for each user.
|
||||
|
||||
|
||||
|
||||
4. When you have finished making the changes, click **Next**.
|
||||
4. When you have finished making the changes, click **Next**.
|
||||
|
||||
13. On the **Cache Size Settings** screen, you can accept or change the default cache size. Click one of the following radio buttons to choose how to manage the cache space:
|
||||
|
||||
1. **Use maximum cache size**. Enter a numeric value from 100–1,048,576 (1 TB) in the **Maximum size (MB)** field to specify the maximum size of the cache.
|
||||
1. **Use maximum cache size**. Enter a numeric value from 100–1,048,576 (1 TB) in the **Maximum size (MB)** field to specify the maximum size of the cache.
|
||||
|
||||
2. **Use free disk space threshold**. Enter a numeric value to specify the amount of free disk space, in MB, that the Application Virtualization Client must leave available on the disk. This allows the cache to grow until the amount of free disk space reaches this limit. The value shown in **Free disk space remaining** indicates how much disk space is currently unused.
|
||||
2. **Use free disk space threshold**. Enter a numeric value to specify the amount of free disk space, in MB, that the Application Virtualization Client must leave available on the disk. This allows the cache to grow until the amount of free disk space reaches this limit. The value shown in **Free disk space remaining** indicates how much disk space is currently unused.
|
||||
|
||||
**Important**
|
||||
To ensure that the cache has sufficient space allocated for all packages that might be deployed, use the **Use free disk space threshold** setting when you configure the client so that the cache can grow as needed. Alternatively, determine in advance how much disk space will be needed for the App-V cache, and at installation time, set the cache size accordingly. For more information about the cache space management feature, in the Microsoft Application Virtualization (App-V) Operations Guide, see **How to Use the Cache Space Management Feature**.
|
||||
**Important**
|
||||
To ensure that the cache has sufficient space allocated for all packages that might be deployed, use the **Use free disk space threshold** setting when you configure the client so that the cache can grow as needed. Alternatively, determine in advance how much disk space will be needed for the App-V cache, and at installation time, set the cache size accordingly. For more information about the cache space management feature, in the Microsoft Application Virtualization (App-V) Operations Guide, see **How to Use the Cache Space Management Feature**.
|
||||
|
||||
|
||||
|
||||
~~~
|
||||
Click **Next** to continue.
|
||||
~~~
|
||||
Click **Next** to continue.
|
||||
|
||||
14. In the following sections of the **Runtime Package Policy Configuration** screen, you can change the parameters that affect how the Application Virtualization client behaves during runtime:
|
||||
|
||||
1. **Application Source Root**. Specifies the location of SFT files. If used, overrides the protocol, server, and port portions of the CODEBASE HREF URL in the OSD file.
|
||||
1. **Application Source Root**. Specifies the location of SFT files. If used, overrides the protocol, server, and port portions of the CODEBASE HREF URL in the OSD file.
|
||||
|
||||
2. **Application Authorization**. When **Require User authorization even when cached** is checked, users are required to connect to a server and validate their credentials at least once before they are allowed to start each virtual application.
|
||||
2. **Application Authorization**. When **Require User authorization even when cached** is checked, users are required to connect to a server and validate their credentials at least once before they are allowed to start each virtual application.
|
||||
|
||||
3. **Allow streaming from file**. Indicates whether streaming from file will be enabled, regardless of how the **Application Source Root** field is used. If not checked, streaming from files is disabled. This must be checked if **Application Source Root** contains a UNC path in the form \\\\server\\share.
|
||||
3. **Allow streaming from file**. Indicates whether streaming from file will be enabled, regardless of how the **Application Source Root** field is used. If not checked, streaming from files is disabled. This must be checked if **Application Source Root** contains a UNC path in the form \\\\server\\share.
|
||||
|
||||
4. **Automatically Load Application**. Controls when and how automatic background loading of applications occurs.
|
||||
4. **Automatically Load Application**. Controls when and how automatic background loading of applications occurs.
|
||||
|
||||
**Note**
|
||||
When you install the App-V client to use with a read-only cache, for example, with a VDI server implementation, set **What applications to Auto Load** to **Do not automatically load applications** to prevent the client from trying to update applications in the read-only cache.
|
||||
|
||||
|
||||
|
||||
~~~
|
||||
Click **Next** to continue.
|
||||
~~~
|
||||
Click **Next** to continue.
|
||||
|
||||
15. On the **Publishing Server** screen, select the **Set up a Publishing Server now** check box if you want to define a publishing server, or click **Next** if you want to complete this later. To define a publishing server, specify the following information:
|
||||
|
||||
1. **Display Name**—Enter the name you want to display for the server.
|
||||
1. **Display Name**—Enter the name you want to display for the server.
|
||||
|
||||
2. **Type**—Select the server type from the drop-down list of server types.
|
||||
2. **Type**—Select the server type from the drop-down list of server types.
|
||||
|
||||
3. **Host Name** and **Port**—Enter the host name and the port in the corresponding fields. When you select a server type in the drop-down list, the port field will automatically fill with the standard port numbers. To change a port number, click the server type in the list and change the port number according to your needs.
|
||||
3. **Host Name** and **Port**—Enter the host name and the port in the corresponding fields. When you select a server type in the drop-down list, the port field will automatically fill with the standard port numbers. To change a port number, click the server type in the list and change the port number according to your needs.
|
||||
|
||||
4. **Path**—If you have selected either **Standard HTTP Server** or **Enhanced Security HTTP Server**, you must enter the complete path to the XML file containing publishing data in this field. If you select either **Application Virtualization Server** or **Enhanced Security Application Virtualization Server**, this field is not active.
|
||||
4. **Path**—If you have selected either **Standard HTTP Server** or **Enhanced Security HTTP Server**, you must enter the complete path to the XML file containing publishing data in this field. If you select either **Application Virtualization Server** or **Enhanced Security Application Virtualization Server**, this field is not active.
|
||||
|
||||
5. **Automatically contact this server to update settings when a user logs in**—Select this check box if you want this server to be queried automatically when users log in to their account on the Application Virtualization Client.
|
||||
5. **Automatically contact this server to update settings when a user logs in**—Select this check box if you want this server to be queried automatically when users log in to their account on the Application Virtualization Client.
|
||||
|
||||
6. When finished with the configuration steps, click **Next**.
|
||||
6. When finished with the configuration steps, click **Next**.
|
||||
|
||||
16. On the **Ready to Install the Program** screen, click **Install**. A screen is displayed that shows the progress of the installation.
|
||||
|
||||
17. On the **Install Wizard Completed** screen, click **Finish**.
|
||||
|
||||
**Note**
|
||||
If the installation fails for any reason, you might need to restart the computer before trying the install again.
|
||||
|
||||
|
||||
**Note**
|
||||
If the installation fails for any reason, you might need to restart the computer before trying the install again.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
|
||||
|
||||
[Stand-Alone Delivery Scenario Overview](stand-alone-delivery-scenario-overview.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Application Virtualization 4
|
||||
description: Application Virtualization 4
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: 9da557bc-f433-47d3-8af7-68ec4ff9bd3f
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
@ -76,7 +76,7 @@ This section is divided into two parts: (1) features in all versions of App-V an
|
||||
|
||||
Microsoft Error Reporting provides a service that allows you to report problems you may be having with App-V to Microsoft and to receive information that may help you avoid or solve such problems.
|
||||
|
||||
**Information Collected, Processed, or Transmitted: **
|
||||
**Information Collected, Processed, or Transmitted:**
|
||||
|
||||
For information about the information collected, processed, or transmitted by Microsoft Error Reporting, see the Microsoft Error Reporting privacy statement at <https://go.microsoft.com/fwlink/?linkid=50293>.
|
||||
|
||||
@ -84,7 +84,7 @@ For information about the information collected, processed, or transmitted by Mi
|
||||
|
||||
We use the error reporting data to solve customer problems and improve our software and services.
|
||||
|
||||
**Choice/Control: **
|
||||
**Choice/Control:**
|
||||
|
||||
App-V does not change your Microsoft Error Reporting settings. If you previously turned on error reporting, it will send Microsoft the information about the errors you encountered. When Microsoft needs additional data to analyze the problem, you will be prompted to review the data and choose whether or not to send it. App-V will always respect your Microsoft Error Reporting settings.
|
||||
|
||||
@ -98,7 +98,7 @@ Enterprise customers can use Group Policy to configure how Microsoft Error Repor
|
||||
|
||||
Microsoft Update is a service that provides Windows updates as well as updates for other Microsoft software, including App-V. For details about what information is collected, how it is used and how to change your settings, see the Update Services Privacy Statement at <https://go.microsoft.com/fwlink/?linkid=50142>.
|
||||
|
||||
**Choice/Control: **
|
||||
**Choice/Control:**
|
||||
|
||||
If Microsoft Update is not enabled, you can opt-in during setup and subsequent checks for updates will follow the machine-wide schedule. You can update this option from the Microsoft Update Control Panel item.
|
||||
|
||||
@ -108,7 +108,7 @@ If Microsoft Update is not enabled, you can opt-in during setup and subsequent c
|
||||
|
||||
The product will collect various configuration items, including UserID, MachineID and SecurityGroup details, to be able to enforce settings on managed nodes. The data is stored in the App-V SQL database and transmitted across the App-V server and client components to enforce the configuration on the managed node.
|
||||
|
||||
**Information Collected, Processed, or Transmitted: **
|
||||
**Information Collected, Processed, or Transmitted:**
|
||||
|
||||
User and machine information and configuration content
|
||||
|
||||
@ -116,7 +116,7 @@ User and machine information and configuration content
|
||||
|
||||
The information is used to enforce the application access configuration on the managed nodes within the enterprise. The information does not leave the enterprise.
|
||||
|
||||
**Choice/Control: **
|
||||
**Choice/Control:**
|
||||
|
||||
By default, the product does not have any data. All data is entered and enabled by the admin and can be viewed in the Management console. The feature cannot be disabled as this is the product functionality. To disable this, App-V will need to be uninstalled.
|
||||
|
||||
@ -130,7 +130,7 @@ None of this information is sent out of the enterprise.
|
||||
|
||||
It captures package history and asset information as part of the package.
|
||||
|
||||
**Information Collected, Processed, or Transmitted: **
|
||||
**Information Collected, Processed, or Transmitted:**
|
||||
|
||||
Information about the package and the sequencing environment is collected and stored in the package manifest during sequencing.
|
||||
|
||||
@ -138,7 +138,7 @@ Information about the package and the sequencing environment is collected and st
|
||||
|
||||
The information will be used by the admin to track the updates done to a package during its lifecycle. It will also be used by software deployment systems to track the package deployments within the organization.
|
||||
|
||||
**Choice/Control: **
|
||||
**Choice/Control:**
|
||||
|
||||
This feature is always enabled and cannot be turned off.
|
||||
|
||||
@ -152,7 +152,7 @@ This administrator information will be stored in the package and can be viewed b
|
||||
|
||||
The product will collect a variety of reporting data points, including the username, to allow reporting on the usage of the product.
|
||||
|
||||
**Information Collected, Processed, or Transmitted: **
|
||||
**Information Collected, Processed, or Transmitted:**
|
||||
|
||||
Information about the machine, package and application usage are collected from every machine that reporting is enabled on.
|
||||
|
||||
@ -160,7 +160,7 @@ Information about the machine, package and application usage are collected from
|
||||
|
||||
The information is used to report on application usage within the enterprise. The information does not leave the enterprise.
|
||||
|
||||
**Choice/Control: **
|
||||
**Choice/Control:**
|
||||
|
||||
By default, the product does not have any data. Data is only collected once the reporting feature is enabled on the App-V Client. To disable the collection of reporting data, the reporting feature must be disabled on all clients.
|
||||
|
||||
@ -178,7 +178,7 @@ This section addresses specific features available in App-V 4.6 SP1 and later.
|
||||
|
||||
The Customer Experience Improvement Program (“CEIP”) collects basic information about your hardware configuration and how you use our software and services in order to identify trends and usage patterns. CEIP also collects the type and number of errors you encounter, software and hardware performance, and the speed of services. We will not collect your name, address, or other contact information.
|
||||
|
||||
**Information Collected, Processed, or Transmitted: **
|
||||
**Information Collected, Processed, or Transmitted:**
|
||||
|
||||
For more information about the information collected, processed, or transmitted by CEIP, see the CEIP privacy statement at <https://go.microsoft.com/fwlink/?LinkID=52097>.
|
||||
|
||||
@ -186,7 +186,7 @@ For more information about the information collected, processed, or transmitted
|
||||
|
||||
We use this information to improve the quality, reliability, and performance of Microsoft software and services.
|
||||
|
||||
**Choice/Control: **
|
||||
**Choice/Control:**
|
||||
|
||||
CEIP is optional and the opt-in status can be updated during install or post install from the GUI.
|
||||
|
||||
@ -196,7 +196,7 @@ CEIP is optional and the opt-in status can be updated during install or post ins
|
||||
|
||||
Customers can use Application Package Accelerators to automatically package complex applications without installing the application. The App-V sequencer allows you to create package accelerators for each virtual package. You can then use these package accelerators to automatically re-create the same virtual package in the future. You may also use package accelerators released by Microsoft or other third parties to simplify and automate packaging of complex applications.
|
||||
|
||||
**Information Collected, Processed, or Transmitted: **
|
||||
**Information Collected, Processed, or Transmitted:**
|
||||
|
||||
Application Package Accelerators may contain information such as computer names, user account information, and information about applications included in the Package Accelerator file.
|
||||
|
||||
|
@ -34,7 +34,7 @@ By default, at installation the App-V client is configured with the minimum perm
|
||||
|
||||
By default, the installation of the client registers file type associations (FTAs) for OSD files, which enables users to start applications directly from OSD files instead of the published shortcuts. If a user with local administrator rights receives an OSD file containing malicious code, either in e-mail or downloaded from a Web site, the user can open the OSD file and start the application even if the client has been set to restrict the **Add Application** permission. You can unregister the FTAs for the OSD to reduce this risk. Also, consider blocking this extension in the e-mail system and at the firewall. For more information about configuring Outlook to block extensions, see <https://go.microsoft.com/fwlink/?LinkId=133278>.
|
||||
|
||||
**Security Note: **
|
||||
**Security Note:**
|
||||
|
||||
Starting with App-V version 4.6, the file type association is no longer created for OSD files during a new installation of the client, although the existing settings will be maintained during an upgrade from version 4.2 or 4.5 of the App-V client. If for any reason it is essential to create the file type association, you can create the following registry keys and set their values as shown:
|
||||
|
||||
@ -50,7 +50,7 @@ During installation, you can use the **RequireAuthorizationIfCached** parameter
|
||||
|
||||
Antivirus software running on an App-V Client computer can detect and report an infected file in the virtual environment. However, it cannot disinfect the file. If a virus is detected in the virtual environment, the antivirus software would perform the configured quarantine or repair operation in the cache, not in the actual package. Configure the antivirus software with an exception for the sftfs.fsd file. This file is the cache file that stores packages on the App-V Client.
|
||||
|
||||
**Security Note: **
|
||||
**Security Note:**
|
||||
|
||||
If a virus is detected in an application or package deployed in the production environment, replace the application or package with a virus-free version.
|
||||
|
||||
|
@ -21,7 +21,7 @@ Microsoft Application Virtualization 4.5 provides the following enhanced securi
|
||||
|
||||
- Application Virtualization now supports Transport Layer Security (TLS) using X.509 V3 certificates. Provided that a server certificate has been provisioned to the planned Application Virtualization Management or Streaming Server, the installation will default to secure, using the RTSPS protocol over port 322. Using RTSPS ensures that communication between the Application Virtualization Servers and the Application Virtualization Clients is signed and encrypted. If no certificate is assigned to the server during the Application Virtualization Server installation, the communication will be set to RTSP over port 554.
|
||||
|
||||
**Security Note: **
|
||||
**Security Note:**
|
||||
|
||||
To help provide a secure setup of the server, you must make sure that RTSP ports are disabled even if you have all packages configured to use RTSPS.
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Application Virtualization 5
|
||||
description: Application Virtualization 5
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: e82eb44b-9ccd-41aa-923b-71400230ad23
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Diagnostics and Recovery Toolset 10
|
||||
description: Diagnostics and Recovery Toolset 10
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: 64403eca-ff05-4327-ac33-bdcc96e706c8
|
||||
ms.pagetype: mdop
|
||||
ms.mktglfcycl: support
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Diagnostics and Recovery Toolset 7 Administrator's Guide
|
||||
description: Diagnostics and Recovery Toolset 7 Administrator's Guide
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: bf89eccd-fc03-48ff-9019-a8640e11dd99
|
||||
ms.pagetype: mdop
|
||||
ms.mktglfcycl: support
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Diagnostics and Recovery Toolset 8 Administrator's Guide
|
||||
description: Diagnostics and Recovery Toolset 8 Administrator's Guide
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: 33685dd7-844f-4864-b504-3ef384ef01de
|
||||
ms.pagetype: mdop
|
||||
ms.mktglfcycl: support
|
||||
|
@ -2,7 +2,7 @@
|
||||
title: MDOP Information Experience
|
||||
description: MDOP Information Experience
|
||||
ms.assetid: 12b8ab56-3267-450d-bb22-1c7e44cb8e52
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.pagetype: mdop
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Microsoft BitLocker Administration and Monitoring 1 Administrator's Guide
|
||||
description: Microsoft BitLocker Administration and Monitoring 1 Administrator's Guide
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: 4086e721-db24-4439-bdcd-ac5ef901811f
|
||||
ms.pagetype: mdop, security
|
||||
ms.mktglfcycl: manage
|
||||
@ -10,46 +10,36 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
# Microsoft BitLocker Administration and Monitoring 1 Administrator's Guide
|
||||
|
||||
|
||||
Microsoft BitLocker Administration and Monitoring (MBAM) provides a simplified administrative interface that you can use to manage BitLocker drive encryption. With MBAM, you can select BitLocker encryption policy options that are appropriate to your enterprise and then use them to monitor client compliance with those policies. You can also report on the encryption status of an individual computer and on the entire enterprise. In addition, you can access recovery key information when users forget their PIN or password, or when their BIOS or boot record changes.
|
||||
|
||||
<a href="" id="getting-started-with-mbam-1-0"></a>[Getting Started with MBAM 1.0](getting-started-with-mbam-10.md)
|
||||
|
||||
[About MBAM 1.0](about-mbam-10.md)**|**[Evaluating MBAM 1.0](evaluating-mbam-10.md)**|**[High Level Architecture for MBAM 1.0](high-level-architecture-for-mbam-10.md)**|**[Accessibility for MBAM 1.0](accessibility-for-mbam-10.md)**|**[Privacy Statement for MBAM 1.0](privacy-statement-for-mbam-10.md)
|
||||
|
||||
<a href="" id="planning-for-mbam-1-0"></a>[Planning for MBAM 1.0](planning-for-mbam-10.md)
|
||||
|
||||
[Preparing your Environment for MBAM 1.0](preparing-your-environment-for-mbam-10.md)**|**[MBAM 1.0 Deployment Prerequisites](mbam-10-deployment-prerequisites.md)**|**[Planning to Deploy MBAM 1.0](planning-to-deploy-mbam-10.md)**|**[MBAM 1.0 Supported Configurations](mbam-10-supported-configurations.md)**|**[MBAM 1.0 Planning Checklist](mbam-10-planning-checklist.md)
|
||||
|
||||
<a href="" id="deploying-mbam-1-0"></a>[Deploying MBAM 1.0](deploying-mbam-10.md)
|
||||
|
||||
[Deploying the MBAM 1.0 Server Infrastructure](deploying-the-mbam-10-server-infrastructure.md)**|**[Deploying MBAM 1.0 Group Policy Objects](deploying-mbam-10-group-policy-objects.md)**|**[Deploying the MBAM 1.0 Client](deploying-the-mbam-10-client.md)**|**[Deploying the MBAM 1.0 Language Release Update](deploying-the-mbam-10-language-release-update.md)**|**[MBAM 1.0 Deployment Checklist](mbam-10-deployment-checklist.md)
|
||||
|
||||
<a href="" id="operations-for-mbam-1-0"></a>[Operations for MBAM 1.0](operations-for-mbam-10.md)
|
||||
|
||||
[Administering MBAM 1.0 Features](administering-mbam-10-features.md)**|**[Monitoring and Reporting BitLocker Compliance with MBAM 1.0](monitoring-and-reporting-bitlocker-compliance-with-mbam-10.md)**|**[Performing BitLocker Management with MBAM](performing-bitlocker-management-with-mbam.md)**|**[Administering MBAM 1.0 by Using PowerShell](administering-mbam-10-by-using-powershell.md)
|
||||
|
||||
<a href="" id="troubleshooting-mbam-1-0"></a>[Troubleshooting MBAM 1.0](troubleshooting-mbam-10.md)
|
||||
|
||||
### More Information
|
||||
|
||||
<a href="" id="release-notes-for-mbam-1-0"></a>[Release Notes for MBAM 1.0](release-notes-for-mbam-10.md)
|
||||
View updated product information and known issues for MBAM 1.0.
|
||||
|
||||
<a href="" id="mdop-techcenter-page"></a>[MDOP TechCenter Page](https://go.microsoft.com/fwlink/p/?LinkId=225286)
|
||||
Learn about the latest MDOP information and resources.
|
||||
|
||||
<a href="" id="mdop-information-experience"></a>[MDOP Information Experience](https://go.microsoft.com/fwlink/p/?LinkId=236032)
|
||||
Find documentation, videos, and other resources for MDOP technologies. You can also [send us feedback](mailto:MDOPDocs@microsoft.com) or learn about updates by following us on [Facebook](https://go.microsoft.com/fwlink/p/?LinkId=242445) or [Twitter](https://go.microsoft.com/fwlink/p/?LinkId=242447).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Getting Started with MBAM 1.0](getting-started-with-mbam-10.md)
|
||||
- [About MBAM 1.0](about-mbam-10.md)
|
||||
- [Release Notes for MBAM 1.0](release-notes-for-mbam-10.md)
|
||||
- [Evaluating MBAM 1.0](evaluating-mbam-10.md)
|
||||
- [High Level Architecture for MBAM 1.0](high-level-architecture-for-mbam-10.md)
|
||||
- [Accessibility for MBAM 1.0](accessibility-for-mbam-10.md)
|
||||
- [Privacy Statement for MBAM 1.0](privacy-statement-for-mbam-10.md)
|
||||
- [Planning for MBAM 1.0](planning-for-mbam-10.md)
|
||||
- [Preparing your Environment for MBAM 1.0](preparing-your-environment-for-mbam-10.md)
|
||||
- [MBAM 1.0 Deployment Prerequisites](mbam-10-deployment-prerequisites.md)
|
||||
- [Planning to Deploy MBAM 1.0](planning-to-deploy-mbam-10.md)
|
||||
- [MBAM 1.0 Supported Configurations](mbam-10-supported-configurations.md)
|
||||
- [MBAM 1.0 Planning Checklist](mbam-10-planning-checklist.md)
|
||||
- [Deploying MBAM 1.0](deploying-mbam-10.md)
|
||||
- [Deploying the MBAM 1.0 Server Infrastructure](deploying-the-mbam-10-server-infrastructure.md)
|
||||
- [Deploying MBAM 1.0 Group Policy Objects](deploying-mbam-10-group-policy-objects.md)
|
||||
- [Deploying the MBAM 1.0 Client](deploying-the-mbam-10-client.md)
|
||||
- [Deploying the MBAM 1.0 Language Release Update](deploying-the-mbam-10-language-release-update.md)
|
||||
- [MBAM 1.0 Deployment Checklist](mbam-10-deployment-checklist.md)
|
||||
- [Operations for MBAM 1.0](operations-for-mbam-10.md)
|
||||
- [Administering MBAM 1.0 Features](administering-mbam-10-features.md)
|
||||
- [Monitoring and Reporting BitLocker Compliance with MBAM 1.0](monitoring-and-reporting-bitlocker-compliance-with-mbam-10.md)
|
||||
- [Performing BitLocker Management with MBAM](performing-bitlocker-management-with-mbam.md)
|
||||
- [Administering MBAM 1.0 by Using PowerShell](administering-mbam-10-by-using-powershell.md)
|
||||
- [Troubleshooting MBAM 1.0](troubleshooting-mbam-10.md)
|
||||
|
||||
## More Information
|
||||
- [MDOP Information Experience](https://go.microsoft.com/fwlink/p/?LinkId=236032)
|
||||
Find documentation, videos, and other resources for MDOP technologies.
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Microsoft BitLocker Administration and Monitoring 2 Administrator's Guide
|
||||
description: Microsoft BitLocker Administration and Monitoring 2 Administrator's Guide
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: fdb43f62-960a-4811-8802-50efdf04b4af
|
||||
ms.pagetype: mdop, security
|
||||
ms.mktglfcycl: manage
|
||||
@ -10,43 +10,47 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
# Microsoft BitLocker Administration and Monitoring 2 Administrator's Guide
|
||||
|
||||
|
||||
Microsoft BitLocker Administration and Monitoring (MBAM) 2.0 provides a simplified administrative interface that you can use to manage BitLocker drive encryption. In BitLocker Administration and Monitoring 2.0, you can select BitLocker drive encryption policy options that are appropriate for your enterprise, and then use them to monitor client compliance with those policies. You can also report on the encryption status of an individual computer and on the enterprise as a whole. In addition, you can access recovery key information when users forget their PIN or password or when their BIOS or boot record changes.
|
||||
|
||||
<a href="" id="getting-started-with-mbam-2-0"></a>[Getting Started with MBAM 2.0](getting-started-with-mbam-20-mbam-2.md)
|
||||
## Outline
|
||||
|
||||
[About MBAM 2.0](about-mbam-20-mbam-2.md)**|**[Release Notes for MBAM 2.0](release-notes-for-mbam-20-mbam-2.md)**|**[About MBAM 2.0 SP1](about-mbam-20-sp1.md)**|**[Release Notes for MBAM 2.0 SP1](release-notes-for-mbam-20-sp1.md)**|**[Evaluating MBAM 2.0](evaluating-mbam-20-mbam-2.md)**|**[High-Level Architecture for MBAM 2.0](high-level-architecture-for-mbam-20-mbam-2.md)**|**[Accessibility for MBAM 2.0](accessibility-for-mbam-20-mbam-2.md)
|
||||
- [Getting Started with MBAM 2.0](getting-started-with-mbam-20-mbam-2.md)
|
||||
- [About MBAM 2.0](about-mbam-20-mbam-2.md)
|
||||
- [Release Notes for MBAM 2.0](release-notes-for-mbam-20-mbam-2.md)
|
||||
- [About MBAM 2.0 SP1](about-mbam-20-sp1.md)
|
||||
- [Release Notes for MBAM 2.0 SP1](release-notes-for-mbam-20-sp1.md)
|
||||
- [Evaluating MBAM 2.0](evaluating-mbam-20-mbam-2.md)
|
||||
- [High-Level Architecture for MBAM 2.0](high-level-architecture-for-mbam-20-mbam-2.md)
|
||||
- [Accessibility for MBAM 2.0](accessibility-for-mbam-20-mbam-2.md)
|
||||
- [Planning for MBAM 2.0](planning-for-mbam-20-mbam-2.md)
|
||||
- [Preparing your Environment for MBAM 2.0](preparing-your-environment-for-mbam-20-mbam-2.md)
|
||||
- [MBAM 2.0 Deployment Prerequisites](mbam-20-deployment-prerequisites-mbam-2.md)
|
||||
- [Planning to Deploy MBAM 2.0](planning-to-deploy-mbam-20-mbam-2.md)
|
||||
- [MBAM 2.0 Supported Configurations](mbam-20-supported-configurations-mbam-2.md)
|
||||
- [MBAM 2.0 Planning Checklist](mbam-20-planning-checklist-mbam-2.md)
|
||||
- [Deploying MBAM 2.0](deploying-mbam-20-mbam-2.md)
|
||||
- [Deploying the MBAM 2.0 Server Infrastructure](deploying-the-mbam-20-server-infrastructure-mbam-2.md)
|
||||
- [Deploying MBAM 2.0 Group Policy Objects](deploying-mbam-20-group-policy-objects-mbam-2.md)
|
||||
- [Deploying the MBAM 2.0 Client](deploying-the-mbam-20-client-mbam-2.md)
|
||||
- [MBAM 2.0 Deployment Checklist](mbam-20-deployment-checklist-mbam-2.md)
|
||||
- [Upgrading from Previous Versions of MBAM](upgrading-from-previous-versions-of-mbam.md)
|
||||
- [Operations for MBAM 2.0](operations-for-mbam-20-mbam-2.md)
|
||||
- [Using MBAM with Configuration Manager](using-mbam-with-configuration-manager.md)
|
||||
- [Administering MBAM 2.0 Features](administering-mbam-20-features-mbam-2.md)
|
||||
- [Monitoring and Reporting BitLocker Compliance with MBAM 2.0](monitoring-and-reporting-bitlocker-compliance-with-mbam-20-mbam-2.md)
|
||||
- [Performing BitLocker Management with MBAM](performing-bitlocker-management-with-mbam-mbam-2.md)
|
||||
- [Maintaining MBAM 2.0](maintaining-mbam-20-mbam-2.md)
|
||||
- [Security and Privacy for MBAM 2.0](security-and-privacy-for-mbam-20-mbam-2.md)
|
||||
- [Administering MBAM 2.0 Using PowerShell](administering-mbam-20-using-powershell-mbam-2.md)
|
||||
- [Troubleshooting MBAM 2.0](troubleshooting-mbam-20-mbam-2.md)
|
||||
|
||||
<a href="" id="planning-for-mbam-2-0"></a>[Planning for MBAM 2.0](planning-for-mbam-20-mbam-2.md)
|
||||
## More Information
|
||||
|
||||
[Preparing your Environment for MBAM 2.0](preparing-your-environment-for-mbam-20-mbam-2.md)**|**[MBAM 2.0 Deployment Prerequisites](mbam-20-deployment-prerequisites-mbam-2.md)**|**[Planning to Deploy MBAM 2.0](planning-to-deploy-mbam-20-mbam-2.md)**|**[MBAM 2.0 Supported Configurations](mbam-20-supported-configurations-mbam-2.md)**|**[MBAM 2.0 Planning Checklist](mbam-20-planning-checklist-mbam-2.md)
|
||||
- [MDOP Information Experience](index.md)
|
||||
|
||||
<a href="" id="deploying-mbam-2-0"></a>[Deploying MBAM 2.0](deploying-mbam-20-mbam-2.md)
|
||||
|
||||
[Deploying the MBAM 2.0 Server Infrastructure](deploying-the-mbam-20-server-infrastructure-mbam-2.md)**|**[Deploying MBAM 2.0 Group Policy Objects](deploying-mbam-20-group-policy-objects-mbam-2.md)**|**[Deploying the MBAM 2.0 Client](deploying-the-mbam-20-client-mbam-2.md)**|**[MBAM 2.0 Deployment Checklist](mbam-20-deployment-checklist-mbam-2.md)**|**[Upgrading from Previous Versions of MBAM](upgrading-from-previous-versions-of-mbam.md)
|
||||
|
||||
<a href="" id="operations-for-mbam-2-0"></a>[Operations for MBAM 2.0](operations-for-mbam-20-mbam-2.md)
|
||||
|
||||
[Using MBAM with Configuration Manager](using-mbam-with-configuration-manager.md)**|**[Administering MBAM 2.0 Features](administering-mbam-20-features-mbam-2.md)**|**[Monitoring and Reporting BitLocker Compliance with MBAM 2.0](monitoring-and-reporting-bitlocker-compliance-with-mbam-20-mbam-2.md)**|**[Performing BitLocker Management with MBAM](performing-bitlocker-management-with-mbam-mbam-2.md)**|**[Maintaining MBAM 2.0](maintaining-mbam-20-mbam-2.md)**|**[Security and Privacy for MBAM 2.0](security-and-privacy-for-mbam-20-mbam-2.md)**|** [Administering MBAM 2.0 Using PowerShell](administering-mbam-20-using-powershell-mbam-2.md)
|
||||
|
||||
<a href="" id="troubleshooting-mbam-2-0"></a>[Troubleshooting MBAM 2.0](troubleshooting-mbam-20-mbam-2.md)
|
||||
|
||||
### More Information
|
||||
|
||||
- [Release Notes for MBAM 2.0](release-notes-for-mbam-20-mbam-2.md)
|
||||
|
||||
View updated product information and known issues for MBAM 2.0.
|
||||
|
||||
- [MDOP TechCenter Page](https://go.microsoft.com/fwlink/p/?LinkId=225286)
|
||||
|
||||
Learn about the latest MDOP information and resources.
|
||||
|
||||
- [MDOP Information Experience](https://go.microsoft.com/fwlink/p/?LinkId=236032)
|
||||
|
||||
Find documentation, videos, and other resources for MDOP technologies. You can also [send us feedback](mailto:MDOPDocs@microsoft.com) or learn about updates by following us on [Facebook](https://go.microsoft.com/fwlink/p/?LinkId=242445) or [Twitter](https://go.microsoft.com/fwlink/p/?LinkId=242447).
|
||||
Find documentation, videos, and other resources for MDOP technologies.
|
||||
|
||||
|
||||
|
||||
|
@ -19,7 +19,7 @@ author: shortpatti
|
||||
This topic describes the process for applying the hotfixes for Microsoft BitLocker Administration and Monitoring (MBAM) Server 2.5 SP1
|
||||
|
||||
### Before you begin, download the latest hotfix of Microsoft BitLocker Administration and Monitoring (MBAM) Server 2.5 SP1
|
||||
[Desktop Optimization Pack](https://www.microsoft.com/en-us/download/details.aspx?id=57157)
|
||||
[Desktop Optimization Pack](https://www.microsoft.com/en-us/download/details.aspx?id=58345)
|
||||
|
||||
#### Steps to update the MBAM Server for existing MBAM environment
|
||||
1. Remove MBAM server feature (do this by opening the MBAM Server Configuration Tool, then selecting Remove Features).
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Microsoft BitLocker Administration and Monitoring 2.5
|
||||
description: Microsoft BitLocker Administration and Monitoring 2.5
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: fd81d7de-b166-47e8-b6c7-d984830762b6
|
||||
ms.pagetype: mdop, security
|
||||
ms.mktglfcycl: manage
|
||||
@ -10,67 +10,61 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
# Microsoft BitLocker Administration and Monitoring 2.5
|
||||
|
||||
|
||||
Microsoft BitLocker Administration and Monitoring (MBAM) 2.5 provides a simplified administrative interface that you can use to manage BitLocker Drive Encryption. You configure MBAM Group Policy Templates that enable you to set BitLocker Drive Encryption policy options that are appropriate for your enterprise, and then use them to monitor client compliance with those policies. You can also report on the encryption status of an individual computer and on the enterprise as a whole. In addition, you can access recovery key information when users forget their PIN or password or when their BIOS or boot record changes. For a more detailed description of MBAM, see [About MBAM 2.5](about-mbam-25.md).
|
||||
|
||||
To get the MBAM software, see [How Do I Get MDOP](https://go.microsoft.com/fwlink/?LinkId=322049) (https://go.microsoft.com/fwlink/?LinkId=322049).
|
||||
To obtain MBAM, see [How Do I Get MDOP](index.md#how-to-get-mdop).
|
||||
|
||||
<a href="" id="getting-started-with-mbam-2-5"></a>[Getting Started with MBAM 2.5](getting-started-with-mbam-25.md)
|
||||
## Outline
|
||||
|
||||
[About MBAM 2.5](about-mbam-25.md)**|**[Release Notes for MBAM 2.5](release-notes-for-mbam-25.md)**|**[About MBAM 2.5 SP1](about-mbam-25-sp1.md)**|**[Release Notes for MBAM 2.5 SP1](release-notes-for-mbam-25-sp1.md)**|**[Evaluating MBAM 2.5 in a Test Environment](evaluating-mbam-25-in-a-test-environment.md)**|**[High-Level Architecture for MBAM 2.5](high-level-architecture-for-mbam-25.md)**|**[Accessibility for MBAM 2.5](accessibility-for-mbam-25.md)
|
||||
- <a href="" id="getting-started-with-mbam-2-5"></a>[Getting Started with MBAM 2.5](getting-started-with-mbam-25.md)
|
||||
- [About MBAM 2.5](about-mbam-25.md)
|
||||
- [Release Notes for MBAM 2.5](release-notes-for-mbam-25.md)
|
||||
- [About MBAM 2.5 SP1](about-mbam-25-sp1.md)
|
||||
- [Release Notes for MBAM 2.5 SP1](release-notes-for-mbam-25-sp1.md)
|
||||
- [Evaluating MBAM 2.5 in a Test Environment](evaluating-mbam-25-in-a-test-environment.md)
|
||||
- [High-Level Architecture for MBAM 2.5](high-level-architecture-for-mbam-25.md)
|
||||
- [Accessibility for MBAM 2.5](accessibility-for-mbam-25.md)
|
||||
- <a href="" id="planning-for-mbam-2-5"></a>[Planning for MBAM 2.5](planning-for-mbam-25.md)
|
||||
- [Preparing your Environment for MBAM 2.5](preparing-your-environment-for-mbam-25.md)
|
||||
- [MBAM 2.5 Deployment Prerequisites](mbam-25-deployment-prerequisites.md)
|
||||
- [Planning for MBAM 2.5 Group Policy Requirements](planning-for-mbam-25-group-policy-requirements.md)
|
||||
- [Planning for MBAM 2.5 Groups and Accounts](planning-for-mbam-25-groups-and-accounts.md)
|
||||
- [Planning How to Secure the MBAM Websites](planning-how-to-secure-the-mbam-websites.md)
|
||||
- [Planning to Deploy MBAM 2.5](planning-to-deploy-mbam-25.md)
|
||||
- [MBAM 2.5 Supported Configurations](mbam-25-supported-configurations.md)
|
||||
- [Planning for MBAM 2.5 High Availability](planning-for-mbam-25-high-availability.md)
|
||||
- [MBAM 2.5 Security Considerations](mbam-25-security-considerations.md)
|
||||
- [MBAM 2.5 Planning Checklist](mbam-25-planning-checklist.md)
|
||||
- <a href="" id="deploying-mbam-2-5"></a>[Deploying MBAM 2.5](deploying-mbam-25.md)
|
||||
- [Deploying the MBAM 2.5 Server Infrastructure](deploying-the-mbam-25-server-infrastructure.md)
|
||||
- [Deploying MBAM 2.5 Group Policy Objects](deploying-mbam-25-group-policy-objects.md)
|
||||
- [Deploying the MBAM 2.5 Client](deploying-the-mbam-25-client.md)
|
||||
- [MBAM 2.5 Deployment Checklist](mbam-25-deployment-checklist.md)
|
||||
- [Upgrading to MBAM 2.5 or MBAM 2.5 SP1 from Previous Versions](upgrading-to-mbam-25-or-mbam-25-sp1-from-previous-versions.md)
|
||||
- [Removing MBAM Server Features or Software](removing-mbam-server-features-or-software.md)
|
||||
- <a href="" id="operations-for-mbam-2-5"></a>[Operations for MBAM 2.5](operations-for-mbam-25.md)
|
||||
- [Administering MBAM 2.5 Features](administering-mbam-25-features.md)
|
||||
- [Monitoring and Reporting BitLocker Compliance with MBAM 2.5](monitoring-and-reporting-bitlocker-compliance-with-mbam-25.md)
|
||||
- [Performing BitLocker Management with MBAM 2.5](performing-bitlocker-management-with-mbam-25.md)
|
||||
- [Maintaining MBAM 2.5](maintaining-mbam-25.md)
|
||||
- [Using Windows PowerShell to Administer MBAM 2.5](using-windows-powershell-to-administer-mbam-25.md)
|
||||
- <a href="" id="troubleshooting-mbam-2-5"></a>[Troubleshooting MBAM 2.5](troubleshooting-mbam-25.md)
|
||||
- <a href="" id="technical-reference-for-mbam-2-5"></a>[Technical Reference for MBAM 2.5](technical-reference-for-mbam-25.md)
|
||||
- [Client Event Logs](client-event-logs.md)
|
||||
- [Server Event Logs](server-event-logs.md)
|
||||
|
||||
<a href="" id="planning-for-mbam-2-5"></a>[Planning for MBAM 2.5](planning-for-mbam-25.md)
|
||||
|
||||
[Preparing your Environment for MBAM 2.5](preparing-your-environment-for-mbam-25.md)**|**[MBAM 2.5 Deployment Prerequisites](mbam-25-deployment-prerequisites.md)**|**[Planning for MBAM 2.5 Group Policy Requirements](planning-for-mbam-25-group-policy-requirements.md)**|**[Planning for MBAM 2.5 Groups and Accounts](planning-for-mbam-25-groups-and-accounts.md)**|**[Planning How to Secure the MBAM Websites](planning-how-to-secure-the-mbam-websites.md)**|**[Planning to Deploy MBAM 2.5](planning-to-deploy-mbam-25.md)**|**[MBAM 2.5 Supported Configurations](mbam-25-supported-configurations.md)**|**[Planning for MBAM 2.5 High Availability](planning-for-mbam-25-high-availability.md)**|**[MBAM 2.5 Security Considerations](mbam-25-security-considerations.md)**|**[MBAM 2.5 Planning Checklist](mbam-25-planning-checklist.md)
|
||||
|
||||
<a href="" id="deploying-mbam-2-5"></a>[Deploying MBAM 2.5](deploying-mbam-25.md)
|
||||
|
||||
[Deploying the MBAM 2.5 Server Infrastructure](deploying-the-mbam-25-server-infrastructure.md)**|**[Deploying MBAM 2.5 Group Policy Objects](deploying-mbam-25-group-policy-objects.md)**|**[Deploying the MBAM 2.5 Client](deploying-the-mbam-25-client.md)**|**[MBAM 2.5 Deployment Checklist](mbam-25-deployment-checklist.md)**|**[Upgrading to MBAM 2.5 or MBAM 2.5 SP1 from Previous Versions](upgrading-to-mbam-25-or-mbam-25-sp1-from-previous-versions.md)**|**[Removing MBAM Server Features or Software](removing-mbam-server-features-or-software.md)
|
||||
|
||||
<a href="" id="operations-for-mbam-2-5"></a>[Operations for MBAM 2.5](operations-for-mbam-25.md)
|
||||
|
||||
[Administering MBAM 2.5 Features](administering-mbam-25-features.md)**|**[Monitoring and Reporting BitLocker Compliance with MBAM 2.5](monitoring-and-reporting-bitlocker-compliance-with-mbam-25.md)**|**[Performing BitLocker Management with MBAM 2.5](performing-bitlocker-management-with-mbam-25.md)**|**[Maintaining MBAM 2.5](maintaining-mbam-25.md)**|**[Using Windows PowerShell to Administer MBAM 2.5](using-windows-powershell-to-administer-mbam-25.md)
|
||||
|
||||
<a href="" id="troubleshooting-mbam-2-5"></a>[Troubleshooting MBAM 2.5](troubleshooting-mbam-25.md)
|
||||
|
||||
<a href="" id="technical-reference-for-mbam-2-5"></a>[Technical Reference for MBAM 2.5](technical-reference-for-mbam-25.md)
|
||||
|
||||
[Client Event Logs](client-event-logs.md)**|**[Server Event Logs](server-event-logs.md)
|
||||
|
||||
### More Information
|
||||
|
||||
- [Release Notes for MBAM 2.5](release-notes-for-mbam-25.md)
|
||||
|
||||
View updated product information and known issues for MBAM 2.5.
|
||||
|
||||
- [MDOP TechCenter Page](https://go.microsoft.com/fwlink/p/?LinkId=225286)
|
||||
|
||||
Learn about the latest MDOP information and resources.
|
||||
|
||||
- [MDOP Information Experience](https://go.microsoft.com/fwlink/p/?LinkId=236032)
|
||||
|
||||
Find documentation, videos, and other resources for MDOP technologies. You can also [send us feedback](mailto:MDOPDocs@microsoft.com) or learn about updates by following us on [Facebook](https://go.microsoft.com/fwlink/p/?LinkId=242445) or [Twitter](https://go.microsoft.com/fwlink/p/?LinkId=242447).
|
||||
|
||||
- [MBAM Deployment Guide](https://www.microsoft.com/download/details.aspx?id=38398)
|
||||
|
||||
Get help in choosing a deployment method for MBAM, including step-by-step instructions for each method.
|
||||
|
||||
- [Apply Hotfixes on MBAM 2.5 SP1 Server](apply-hotfix-for-mbam-25-sp1.md)
|
||||
|
||||
Guide of how to apply MBAM 2.5 SP1 Server hotfixes
|
||||
|
||||
## Got a suggestion for MBAM?
|
||||
- Add or vote on suggestions [here](http://mbam.uservoice.com/forums/268571-microsoft-bitlocker-administration-and-monitoring).
|
||||
- For MBAM issues, use the [MBAM TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopmbam).
|
||||
|
||||
|
||||
|
||||
|
||||
## More Information
|
||||
|
||||
- [MDOP Information Experience](index.md)
|
||||
|
||||
Find documentation, videos, and other resources for MDOP technologies.
|
||||
|
||||
- [MBAM Deployment Guide](https://www.microsoft.com/download/details.aspx?id=38398)
|
||||
|
||||
Get help in choosing a deployment method for MBAM, including step-by-step instructions for each method.
|
||||
|
||||
- [Apply Hotfixes on MBAM 2.5 SP1 Server](apply-hotfix-for-mbam-25-sp1.md)
|
||||
|
||||
Guide of how to apply MBAM 2.5 SP1 Server hotfixes
|
||||
|
@ -72,17 +72,17 @@ Image pre-staging is useful only for the initial image download. It is not suppo
|
||||
|
||||
**NT AUTHORITY\\Authenticated Users:(OI)(CI)(special access:)**
|
||||
|
||||
** READ\_CONTROL**
|
||||
**READ\_CONTROL**
|
||||
|
||||
** SYNCHRONIZE**
|
||||
**SYNCHRONIZE**
|
||||
|
||||
** FILE\_GENERIC\_READ**
|
||||
**FILE\_GENERIC\_READ**
|
||||
|
||||
** FILE\_READ\_DATA**
|
||||
**FILE\_READ\_DATA**
|
||||
|
||||
** FILE\_READ\_EA**
|
||||
**FILE\_READ\_EA**
|
||||
|
||||
** FILE\_READ\_ATTRIBUTES**
|
||||
**FILE\_READ\_ATTRIBUTES**
|
||||
|
||||
**NT AUTHORITY\\SYSTEM:(OI)(CI)F**
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Microsoft Enterprise Desktop Virtualization Planning, Deployment, and Operations Guide
|
||||
description: Microsoft Enterprise Desktop Virtualization Planning, Deployment, and Operations Guide
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: 7bc3e120-df77-4f4c-bc8e-7aaa4c2a6525
|
||||
ms.pagetype: mdop, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Microsoft Enterprise Desktop Virtualization 2.0
|
||||
description: Microsoft Enterprise Desktop Virtualization 2.0
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: 84109be0-4613-42e9-85fc-fcda8de6e4c4
|
||||
ms.pagetype: mdop, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: MDOP Solutions and Scenarios
|
||||
description: MDOP Solutions and Scenarios
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: 1cb18bef-fbae-4e96-a4f1-90cf111c3b5f
|
||||
ms.pagetype: mdop
|
||||
ms.mktglfcycl: deploy
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Microsoft User Experience Virtualization (UE-V) 1.0
|
||||
description: Microsoft User Experience Virtualization (UE-V) 1.0
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: 7c2b59f6-bbe9-4373-8b08-c1738665a37b
|
||||
ms.pagetype: mdop, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
@ -193,7 +193,7 @@ You’ll need to deploy a settings storage location, a standard network share wh
|
||||
|
||||
|
||||
|
||||
**Security Note: **
|
||||
**Security Note:**
|
||||
|
||||
If you create the settings storage share on a computer running a Windows Server operating system, configure UE-V to verify that either the local Administrators group or the current user is the owner of the folder where settings packages are stored. To enable this additional security, specify this setting in the Windows Server Registry Editor:
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Microsoft User Experience Virtualization (UE-V) 2.x
|
||||
description: Microsoft User Experience Virtualization (UE-V) 2.x
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: b860fed0-b846-415d-bdd6-ba60231a64be
|
||||
ms.pagetype: mdop, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
Reference in New Issue
Block a user