.
**Note**
- If you are using the Configuration Manager integration with App-V 5.1, most reports are generated from Configuration Manager rather than from App-V 5.1. See [Introduction to Application Management in Configuration Manager](77641e23-45d0-41d9-88ff-cac253ba1e26) and the "Virtualized Application" section of [List of Reports Supplied with Microsoft System Center 2012 R2 Configuration Manager](e3fd6dd4-f036-4913-a378-241c952e9bdf) for more information.
+ If you are using the Configuration Manager integration with App-V 5.1, most reports are generated from Configuration Manager rather than from App-V 5.1.
diff --git a/mdop/appv-v5/app-v-50-security-considerations.md b/mdop/appv-v5/app-v-50-security-considerations.md
index 81d4980b55..9f1fd684a1 100644
--- a/mdop/appv-v5/app-v-50-security-considerations.md
+++ b/mdop/appv-v5/app-v-50-security-considerations.md
@@ -144,11 +144,6 @@ During App-V 5.0 Setup, setup log files are created in the **%temp%** folder of
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
-## Related topics
-
-
-[Security and Privacy for App-V 5.0](2544bb39-007c-404b-b3cf-4c37128183bd)
-
diff --git a/mdop/appv-v5/application-publishing-and-client-interaction.md b/mdop/appv-v5/application-publishing-and-client-interaction.md
index 91b8b270b6..48db8b1c24 100644
--- a/mdop/appv-v5/application-publishing-and-client-interaction.md
+++ b/mdop/appv-v5/application-publishing-and-client-interaction.md
@@ -87,7 +87,7 @@ The Sequencer creates App-V packages and produces a virtualized application. The
-For information about sequencing, see [Application Virtualization 5.0 Sequencing Guide](www.microsoft.com/download/details.aspx?id=27760).
+For information about sequencing, see [Application Virtualization 5.0 Sequencing Guide](http://www.microsoft.com/download/details.aspx?id=27760).
## What’s in the appv file?
diff --git a/mdop/appv-v5/how-to-convert-a-package-created-in-a-previous-version-of-app-v.md b/mdop/appv-v5/how-to-convert-a-package-created-in-a-previous-version-of-app-v.md
index a5f109c2b1..c003923a1c 100644
--- a/mdop/appv-v5/how-to-convert-a-package-created-in-a-previous-version-of-app-v.md
+++ b/mdop/appv-v5/how-to-convert-a-package-created-in-a-previous-version-of-app-v.md
@@ -58,8 +58,6 @@ You must configure the package converter to always save the package ingredients
[Operations for App-V 5.0](operations-for-app-v-50.md)
-[How to Convert a Package Created in a Previous Version Using PowerShell \[Beta\]](b41d43f5-860e-476a-bd56-f37f25a78537)
-
diff --git a/mdop/appv-v5/how-to-create-a-connection-group.md b/mdop/appv-v5/how-to-create-a-connection-group.md
index 298beec08c..dfe81bdf23 100644
--- a/mdop/appv-v5/how-to-create-a-connection-group.md
+++ b/mdop/appv-v5/how-to-create-a-connection-group.md
@@ -10,7 +10,7 @@ author: MaggiePucciEvans
Use these steps to create a connection group by using the App-V Management Console. To use PowerShell to create connection groups, see [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell.md).
-When you place packages in a connection group, their package root paths are merged. If you remove packages, only the remaining packages maintain the merged root. For more information, see [About Merged Root Paths for Packages in Connection Groups](97b35683-9caf-4ce9-8ca5-43452d329b98).
+When you place packages in a connection group, their package root paths are merged. If you remove packages, only the remaining packages maintain the merged root.
**To create a connection group**
diff --git a/mdop/appv-v5/how-to-modify-client-configuration-by-using-powershell.md b/mdop/appv-v5/how-to-modify-client-configuration-by-using-powershell.md
index 5f988307b4..51bea473ff 100644
--- a/mdop/appv-v5/how-to-modify-client-configuration-by-using-powershell.md
+++ b/mdop/appv-v5/how-to-modify-client-configuration-by-using-powershell.md
@@ -12,7 +12,7 @@ Use the following procedure to configure the App-V 5.0 client configuration.
**To modify App-V 5.0 client configuration using PowerShell**
-1. To configure the client settings using PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing PowerShell, and a list of cmdlets see, [How to install PowerShell](be9fd867-8e37-467a-8a95-b421a1a49f39).
+1. To configure the client settings using PowerShell, use the **Set-AppvClientConfiguration** cmdlet.
2. To modify the client configuration, open a PowerShell Command prompt and run the following cmdlet **Set-AppvClientConfiguration** with any required parameters. For example:
diff --git a/mdop/dart-v7/deploying-the-dart-70-recovery-image-dart-7.md b/mdop/dart-v7/deploying-the-dart-70-recovery-image-dart-7.md
index 9079f5b4d7..716bc93b21 100644
--- a/mdop/dart-v7/deploying-the-dart-70-recovery-image-dart-7.md
+++ b/mdop/dart-v7/deploying-the-dart-70-recovery-image-dart-7.md
@@ -8,7 +8,7 @@ author: MaggiePucciEvans
# Deploying the DaRT 7.0 Recovery Image
-After you have created the International Organization for Standardization (ISO) file that contains the Microsoft Diagnostics and Recovery Toolset (DaRT) 7 recovery image, you can deploy the DaRT recovery image throughout your enterprise so that it is available to end users and helpdesk agents. There are four supported methods that you can use to deploy the DaRT recovery image (for more information about each method and the advantages and disadvantages of each, see [Planning How to Save and Deploy the DaRT Recovery Image](bc550da2-485f-4c6a-a56a-2a446b88e58c#bkmk-determinehowtosavedartimage)).
+After you have created the International Organization for Standardization (ISO) file that contains the Microsoft Diagnostics and Recovery Toolset (DaRT) 7 recovery image, you can deploy the DaRT recovery image throughout your enterprise so that it is available to end users and helpdesk agents. There are four supported methods that you can use to deploy the DaRT recovery image.
- Burn the ISO image file to a CD or DVD
diff --git a/mdop/dart-v7/how-to-ensure-that-crash-analyzer-can-access-symbol-files-dart-7.md b/mdop/dart-v7/how-to-ensure-that-crash-analyzer-can-access-symbol-files-dart-7.md
index 7ab9b8ead4..276181787c 100644
--- a/mdop/dart-v7/how-to-ensure-that-crash-analyzer-can-access-symbol-files-dart-7.md
+++ b/mdop/dart-v7/how-to-ensure-that-crash-analyzer-can-access-symbol-files-dart-7.md
@@ -23,7 +23,7 @@ The following is a list of options that are available for guaranteeing access to
- **Copy the dump file to another computer.** If the symbols cannot be downloaded because of a lack of an Internet connection, copy the crash dump file to a computer that does have an Internet connection and run the stand-alone **Crash Analyzer Wizard** on that computer.
-- **Access the symbol files from another computer.** If the symbols cannot be downloaded because of a lack of an Internet connection, you can download the symbols from a computer that does have an Internet connection and then copy them to the computer that does not have an Internet connection, or you can map a network drive to a location where the symbols are available on the local network. If you run the **Crash Analyzer** in a Windows Recovery Environment (Windows RE), you can include the symbol files on the DaRT recovery image. For more information about how to create a recovery image, see [Creating the DaRT 7.0 Recovery Image](84d7df0c-b80b-4370-8ce2-9fd5a0065c17).
+- **Access the symbol files from another computer.** If the symbols cannot be downloaded because of a lack of an Internet connection, you can download the symbols from a computer that does have an Internet connection and then copy them to the computer that does not have an Internet connection, or you can map a network drive to a location where the symbols are available on the local network. If you run the **Crash Analyzer** in a Windows Recovery Environment (Windows RE), you can include the symbol files on the DaRT recovery image. For more information about how to create a recovery image, see [Creating the DaRT 7.0 Recovery Image](creating-the-dart-70-recovery-image-dart-7.md).
- **Access symbol files through an HTTP proxy server.** If the symbols cannot be downloaded because an HTTP proxy server must be accessed, use the following steps to access an HTTP proxy server. In DaRT 7, the **Crash Analyzer Wizard** has a setting available on the **Specify Symbol Files Location** dialog page, marked with the label **Proxy server (optional, using the format "server:port")**. You can use this text box to specify a proxy server. Enter the proxy address in the form **<hostname>:<port>**, where the <**hostname**> is a DNS name or IP address, and the <**port**> is a TCP port number, usually 80. There are two modes in which the **Crash Analyzer** can be run. Following is how you use the proxy setting in each of these modes:
diff --git a/mdop/dart-v7/index.md b/mdop/dart-v7/index.md
index 2e4f34d02a..3d28a83520 100644
--- a/mdop/dart-v7/index.md
+++ b/mdop/dart-v7/index.md
@@ -32,8 +32,6 @@ DaRT is an important part of the Microsoft Desktop Optimization Pack (MDOP), a d
[Technical Reference for DaRT 7.0](technical-reference-for-dart-70-new-ia.md)
-[Microsoft Diagnostics and Recovery Toolset (DaRT) users should use Windows Defender Offline (WDO) for malware detection](59678283-4b44-4d02-ba8f-0e7315efd5d1)
-
### More Information
[Release Notes for DaRT 7.0](release-notes-for-dart-70-new-ia.md)
diff --git a/mdop/dart-v7/overview-of-the-tools-in-dart-70-new-ia.md b/mdop/dart-v7/overview-of-the-tools-in-dart-70-new-ia.md
index 7fd365dec0..03b7db08de 100644
--- a/mdop/dart-v7/overview-of-the-tools-in-dart-70-new-ia.md
+++ b/mdop/dart-v7/overview-of-the-tools-in-dart-70-new-ia.md
@@ -112,7 +112,7 @@ The **Search** tool opens a **File Search** window that you can use to find docu
### Standalone System Sweeper
**Important**
-Environments with the Standalone System Sweeper deployed should instead use the Windows Defender Offline (WDO) protection image for malware detection. Because of how the Standalone System Sweeper tool integrates into DaRT, all supported DaRT version deployments cannot apply these anti-malware updates to their DaRT images. For more information, see [Microsoft Diagnostics and Recovery Toolset (DaRT) users should use Windows Defender Offline (WDO) for malware detection](59678283-4b44-4d02-ba8f-0e7315efd5d1).
+Environments with the Standalone System Sweeper deployed should instead use the Windows Defender Offline (WDO) protection image for malware detection. Because of how the Standalone System Sweeper tool integrates into DaRT, all supported DaRT version deployments cannot apply these anti-malware updates to their DaRT images.
diff --git a/mdop/dart-v7/technical-reference-for-dart-70-new-ia.md b/mdop/dart-v7/technical-reference-for-dart-70-new-ia.md
index d4660c69b1..94bf926ca2 100644
--- a/mdop/dart-v7/technical-reference-for-dart-70-new-ia.md
+++ b/mdop/dart-v7/technical-reference-for-dart-70-new-ia.md
@@ -10,13 +10,6 @@ author: MaggiePucciEvans
This section includes technical reference information about Microsoft Diagnostics and Recovery Toolset (DaRT) 8.0 that provide additional information an administrator.
-## Technical reference
-
-
-- [Microsoft Diagnostics and Recovery Toolset (DaRT) users should use Windows Defender Offline (WDO) for malware detection](59678283-4b44-4d02-ba8f-0e7315efd5d1)
-
- Environments with the Microsoft Diagnostics and Recovery Toolset (DaRT) Defender tool deployed should instead use the Windows Defender Offline (WDO) protection image for malware detection.
-
## Other resources for DaRT operations
diff --git a/mdop/index.md b/mdop/index.md
index 7502bc96f1..9d0706404a 100644
--- a/mdop/index.md
+++ b/mdop/index.md
@@ -98,7 +98,7 @@ The following table provides links to the product documentation for the MDOP pro
MED-V 1.0 SP1 - Windows 7, Windows Vista, Windows XP
MED-V 1.0 - Windows Vista, Windows XP
[Microsoft Enterprise Desktop Virtualization 2.0](medv-v2/index.md)
-[About MED-V 1.0 SP1](p_mdop_medv_1/about-med-v-10-sp1.md)
+[About MED-V 1.0 SP1](medv-v1/about-med-v-10-sp1.md)
[Microsoft Enterprise Desktop Virtualization 1.0](74a9483e-87a1-4394-a4d5-50cff5c07297)
[MED-V Whitepapers on the Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=231903) (http://go.microsoft.com/fwlink/p/?LinkId=231903) |
diff --git a/mdop/mbam-v1/how-to-install-and-configure-mbam-on-distributed-servers-mbam-1.md b/mdop/mbam-v1/how-to-install-and-configure-mbam-on-distributed-servers-mbam-1.md
index 4f26106d85..e72d1ae8fc 100644
--- a/mdop/mbam-v1/how-to-install-and-configure-mbam-on-distributed-servers-mbam-1.md
+++ b/mdop/mbam-v1/how-to-install-and-configure-mbam-on-distributed-servers-mbam-1.md
@@ -10,7 +10,7 @@ author: MaggiePucciEvans
The procedures in this topic describe the full installation of the Microsoft BitLocker Administration and Monitoring (MBAM) features on distributed servers.
-Each server feature has certain prerequisites. To verify that you have met the prerequisites and hardware and software requirements, see [MBAM 1.0 Deployment Prerequisites](mbam-10-deployment-prerequisites.md) and [MBAM 1.0 Supported Configurations](mbam-10-supported-configurations.md). In addition, some features require that you provide certain information during the installation process to successfully deploy the feature. You should also review [Planning the Server Infrastructure for MBAM](962f2f48-e800-43f2-ab25-664a8a6298ee) before you begin the MBAM deployment.
+Each server feature has certain prerequisites. To verify that you have met the prerequisites and hardware and software requirements, see [MBAM 1.0 Deployment Prerequisites](mbam-10-deployment-prerequisites.md) and [MBAM 1.0 Supported Configurations](mbam-10-supported-configurations.md). In addition, some features require that you provide certain information during the installation process to successfully deploy the feature.
**Note**
To obtain the setup log files, you have to install MBAM by using the **msiexec** package and the **/l <location>** option. Log files are created in the location that you specify.
diff --git a/mdop/mbam-v2/about-mbam-20-mbam-2.md b/mdop/mbam-v2/about-mbam-20-mbam-2.md
index 353cc937e9..9f504d5c2a 100644
--- a/mdop/mbam-v2/about-mbam-20-mbam-2.md
+++ b/mdop/mbam-v2/about-mbam-20-mbam-2.md
@@ -94,8 +94,6 @@ This technology is a part of the Microsoft Desktop Optimization Pack (MDOP). Ent
## Related topics
-[Administrator's Guide for Microsoft BitLocker Administration and Monitoring 2](b5e62c77-f365-4492-8c30-95c55304b760)
-
[Getting Started with MBAM 2.0](getting-started-with-mbam-20-mbam-2.md)
diff --git a/mdop/mbam-v2/mbam-20-privacy-statement-mbam-2.md b/mdop/mbam-v2/mbam-20-privacy-statement-mbam-2.md
index 9e495cb86a..7304415b6e 100644
--- a/mdop/mbam-v2/mbam-20-privacy-statement-mbam-2.md
+++ b/mdop/mbam-v2/mbam-20-privacy-statement-mbam-2.md
@@ -47,7 +47,7 @@ We will occasionally update this privacy statement to reflect changes in our pro
### For More Information
-Microsoft welcomes your comments regarding this privacy statement. If you have questions about this statement or believe that we have not adhered to it, please [contact us](contact us).
+Microsoft welcomes your comments regarding this privacy statement. If you have questions about this statement or believe that we have not adhered to it, please contact us.
Microsoft Privacy Microsoft Corporation One Microsoft Way Redmond, Washington 98052 USA
diff --git a/mdop/mbam-v25/planning-to-deploy-mbam-25.md b/mdop/mbam-v25/planning-to-deploy-mbam-25.md
index 89b19e4939..d3c92e313c 100644
--- a/mdop/mbam-v25/planning-to-deploy-mbam-25.md
+++ b/mdop/mbam-v25/planning-to-deploy-mbam-25.md
@@ -8,7 +8,7 @@ author: MaggiePucciEvans
# Planning to Deploy MBAM 2.5
-You should consider a number of different deployment configurations and prerequisites before you create your deployment plan for Microsoft BitLocker Administration and Monitoring (MBAM). This section includes information that can help you gather the necessary information to formulate a deployment plan that best meets your business requirements. If you are installing MBAM with the Configuration Manager topology, see [Planning to Deploy MBAM with Configuration Manager](68672830-e2c8-455b-971a-067c40c1333d) for additional planning information.
+You should consider a number of different deployment configurations and prerequisites before you create your deployment plan for Microsoft BitLocker Administration and Monitoring (MBAM). This section includes information that can help you gather the necessary information to formulate a deployment plan that best meets your business requirements.
## Review the MBAM 2.5 supported configurations
diff --git a/mdop/medv-v1/how-to-apply-virtual-machine-settings-to-a-med-v-workspace.md b/mdop/medv-v1/how-to-apply-virtual-machine-settings-to-a-med-v-workspace.md
index 07019556aa..f3d2a09b72 100644
--- a/mdop/medv-v1/how-to-apply-virtual-machine-settings-to-a-med-v-workspace.md
+++ b/mdop/medv-v1/how-to-apply-virtual-machine-settings-to-a-med-v-workspace.md
@@ -132,7 +132,7 @@ Trim Transfer requires indexing the hard drive, which might take a considerable
## Related topics
-[Creating a MED-V Image](86bd1301-0d0b-448a-a37c-b606d839aa0e)
+[Creating a MED-V Image](creating-a-med-v-image.md)
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
diff --git a/mdop/solutions/creating-app-v-45-databases-using-sql-scripting.md b/mdop/solutions/creating-app-v-45-databases-using-sql-scripting.md
index 270786cc15..31f9673788 100644
--- a/mdop/solutions/creating-app-v-45-databases-using-sql-scripting.md
+++ b/mdop/solutions/creating-app-v-45-databases-using-sql-scripting.md
@@ -146,7 +146,7 @@ The two sample batch files must be placed in the same directory where the rest o
- Run the create schema.bat file from the directory where it was copied to. Syntax is: “Create\_schema.bat `SQLSERVERNAME`”
- 
+ 
- If this script fails during the creation of the new “APPVIRTDB” database, check the log as indicated to correct the issue. It will be necessary to delete the database that was created with a partial running of the scripts in order to ensure that subsequent attempts will work properly.
diff --git a/mdop/uev-v1/ue-v-checklist.md b/mdop/uev-v1/ue-v-checklist.md
index d95eb13edd..136063da74 100644
--- a/mdop/uev-v1/ue-v-checklist.md
+++ b/mdop/uev-v1/ue-v-checklist.md
@@ -50,8 +50,7 @@ Use this checklist to plan for preparing your computing environment for Microsof
Custom settings templates only – deploy the features that are required to create and store applications other than the UE-V default applications. |
[Deploying the Settings Template Catalog for UE-V 1.0](deploying-the-settings-template-catalog-for-ue-v-10.md)
-[Installing the UE-V Generator](installing-the-ue-v-generator.md)
-[Using the UE-V Generator](4ee6e2f1-35ee-426e-9aaa-528c3f04a305) |
+[Installing the UE-V Generator](installing-the-ue-v-generator.md)
Familiarize yourself with the administration and management tasks for UE-V. |
diff --git a/mdop/uev-v2/configuring-the-company-settings-center-for-ue-v-2x-both-uevv2.md b/mdop/uev-v2/configuring-the-company-settings-center-for-ue-v-2x-both-uevv2.md
index 835ac17b06..08ac798e44 100644
--- a/mdop/uev-v2/configuring-the-company-settings-center-for-ue-v-2x-both-uevv2.md
+++ b/mdop/uev-v2/configuring-the-company-settings-center-for-ue-v-2x-both-uevv2.md
@@ -69,17 +69,6 @@ The Company Settings Center can include a hyperlink that users can click to get
3. Deploy settings to users’ computers by using the management tool.
-## Other resources for Company Settings Center
-
-
-Users can find the following links in the Company Settings Center:
-
-- [What is settings synchronization?](../uev-v2/what-is-settings-synchronization-uevv2.md)
-
-- [Why won't my application settings sync?](../uev-v2/why-wont-my-application-settings-sync-uevv2.md)
-
-- [Why won't my Windows settings sync?](../uev-v2/why-wont-my-windows-settings-sync-uevv2.md)
-
## Got a suggestion for UE-V?