From 9678b88507c9690da210c821c15e1e6d46cb4e62 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 1 Nov 2016 12:35:44 -0700 Subject: [PATCH 1/3] Fixing broken bookmarks --- ...-with-user-published-and-globally-published-packages.md | 7 ++----- ...ith-user-published-and-globally-published-packages51.md | 6 ++---- mdop/appv-v5/how-to-deploy-the-app-v-client-51gb18030.md | 4 +--- mdop/appv-v5/how-to-deploy-the-app-v-client-gb18030.md | 2 +- mdop/mbam-v25/how-to-recover-a-moved-drive-mbam-25.md | 3 --- ...-system-center-configuration-manager-2012-both-uevv2.md | 2 +- 6 files changed, 7 insertions(+), 17 deletions(-) diff --git a/mdop/appv-v5/how-to-create-a-connection-group-with-user-published-and-globally-published-packages.md b/mdop/appv-v5/how-to-create-a-connection-group-with-user-published-and-globally-published-packages.md index 446346aa98..5794aa6c8a 100644 --- a/mdop/appv-v5/how-to-create-a-connection-group-with-user-published-and-globally-published-packages.md +++ b/mdop/appv-v5/how-to-create-a-connection-group-with-user-published-and-globally-published-packages.md @@ -11,8 +11,6 @@ ms.prod: w10 # How to Create a Connection Group with User-Published and Globally Published Packages - - You can create user-entitled connection groups that contain both user-published and globally published packages, using either of the following methods: - [How to use PowerShell cmdlets to create the user-entitled connection groups](#bkmk-posh-userentitled-cg) @@ -46,8 +44,7 @@ You can create user-entitled connection groups that contain both user-published   - -**How to use PowerShell cmdlets to create user-entitled connection groups** +**How to use PowerShell cmdlets to create user-entitled connection groups** 1. Add and publish packages by using the following commands: @@ -67,7 +64,7 @@ You can create user-entitled connection groups that contain both user-published **Enable-AppvClientConnectionGroup  -GroupId CG\_Group\_ID -VersionId CG\_Version\_ID** -**How to use the App-V Server to create user-entitled connection groups** +**How to use the App-V Server to create user-entitled connection groups** 1. Open the App-V 5.0 Management Console. diff --git a/mdop/appv-v5/how-to-create-a-connection-group-with-user-published-and-globally-published-packages51.md b/mdop/appv-v5/how-to-create-a-connection-group-with-user-published-and-globally-published-packages51.md index e69999a07a..8f5736d581 100644 --- a/mdop/appv-v5/how-to-create-a-connection-group-with-user-published-and-globally-published-packages51.md +++ b/mdop/appv-v5/how-to-create-a-connection-group-with-user-published-and-globally-published-packages51.md @@ -45,9 +45,7 @@ You can create user-entitled connection groups that contain both user-published -  - -**How to use PowerShell cmdlets to create user-entitled connection groups** +**How to use PowerShell cmdlets to create user-entitled connection groups** 1. Add and publish packages by using the following commands: @@ -67,7 +65,7 @@ You can create user-entitled connection groups that contain both user-published **Enable-AppvClientConnectionGroup  -GroupId CG\_Group\_ID -VersionId CG\_Version\_ID** -**How to use the App-V Server to create user-entitled connection groups** +**How to use the App-V Server to create user-entitled connection groups** 1. Open the App-V 5.1 Management Console. diff --git a/mdop/appv-v5/how-to-deploy-the-app-v-client-51gb18030.md b/mdop/appv-v5/how-to-deploy-the-app-v-client-51gb18030.md index 37f02d475b..e80df8bb75 100644 --- a/mdop/appv-v5/how-to-deploy-the-app-v-client-51gb18030.md +++ b/mdop/appv-v5/how-to-deploy-the-app-v-client-51gb18030.md @@ -15,7 +15,7 @@ ms.prod: w10 Use the following procedure to install the Microsoft Application Virtualization (App-V) 5.1 client and Remote Desktop Services client. You must install the version of the client that matches the operating system of the target computer. -**What to do before you start** +**What to do before you start** 1. Review and install the software prerequisites: @@ -143,8 +143,6 @@ Use the following procedure to install the Microsoft Application Virtualization **Note**   The client Windows Installer (.msi) supports the same set of switches, except for the **/LOG** parameter. -   - diff --git a/mdop/appv-v5/how-to-deploy-the-app-v-client-gb18030.md b/mdop/appv-v5/how-to-deploy-the-app-v-client-gb18030.md index 5210d0f706..a3e6644896 100644 --- a/mdop/appv-v5/how-to-deploy-the-app-v-client-gb18030.md +++ b/mdop/appv-v5/how-to-deploy-the-app-v-client-gb18030.md @@ -15,7 +15,7 @@ ms.prod: w10 Use the following procedure to install the Microsoft Application Virtualization (App-V) 5.0 client and Remote Desktop Services client. You must install the version of the client that matches the operating system of the target computer. -**What to do before you start** +**What to do before you start** 1. Review and install the software prerequisites: 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 a0d1d62844..e1b330088f 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 @@ -15,9 +15,6 @@ This topic explains how to use the Administration and Monitoring Website (also r 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). -**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). diff --git a/mdop/uev-v2/configuring-ue-v-2x-with-system-center-configuration-manager-2012-both-uevv2.md b/mdop/uev-v2/configuring-ue-v-2x-with-system-center-configuration-manager-2012-both-uevv2.md index 036cada1cc..637c1fbc36 100644 --- a/mdop/uev-v2/configuring-ue-v-2x-with-system-center-configuration-manager-2012-both-uevv2.md +++ b/mdop/uev-v2/configuring-ue-v-2x-with-system-center-configuration-manager-2012-both-uevv2.md @@ -195,7 +195,7 @@ The UE-V template baseline is created using the UevTemplateBaselineGenerator.exe The result is a baseline CAB file that is ready for import into Configuration Manager. If at a future date, you update or add a template, you can rerun the command using the same baseline name. Importing the CAB results in CI version updates on the changed templates. -### Create the First UE-V Template Baseline +### Create the First UE-V Template Baseline 1. Create a “master” set of UE-V templates in a stable folder location visible to the machine running your ConfigMgr Admin Console. As templates are added or updated, this folder is where they are pulled for distribution. The initial list of templates can be copied from a machine with UE-V installed. The default template location is C:\\Program Files\\Microsoft User Experience Virtualization\\Templates. From dbe2533393a3b890cf548a4c07ac964c0fc01a78 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 1 Nov 2016 13:06:55 -0700 Subject: [PATCH 2/3] Fixing broken links --- ...tand-alone-computer-by-using-powershell.md | 12 ++++------ ...nd-alone-computer-by-using-powershell51.md | 10 ++++---- ...existing-virtual-application-package-51.md | 23 ++++--------------- ...isting-virtual-application-package-beta.md | 21 +++-------------- ...ng-a-windows-virtual-pc-image-for-med-v.md | 2 +- ...r-configuration-manager-2012-both-uevv2.md | 8 ++----- 6 files changed, 18 insertions(+), 58 deletions(-) diff --git a/mdop/appv-v5/how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell.md b/mdop/appv-v5/how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell.md index cc477758ac..780141e3d7 100644 --- a/mdop/appv-v5/how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell.md +++ b/mdop/appv-v5/how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell.md @@ -27,7 +27,7 @@ This topic explains the following procedures: - [To allow only administrators to enable connection groups](#bkmk-admin-only-posh-topic-cg) -**To add and publish the App-V packages in the connection group** +**To add and publish the App-V packages in the connection group** 1. To add and publish the App-V 5.0 packages to the computer running the App-V client, type the following command: @@ -35,7 +35,7 @@ This topic explains the following procedures: 2. Repeat **step 1** of this procedure for each package in the connection group. -**To add and enable the connection group on the App-V client** +**To add and enable the connection group on the App-V client** 1. Add the connection group by typing the following command: @@ -47,7 +47,7 @@ This topic explains the following procedures: When any virtual applications that are in the member packages are run on the target computer, they will run inside the connection group’s virtual environment and will be available to all the virtual applications in the other packages in the connection group. -**To enable or disable a connection group for a specific user** +**To enable or disable a connection group for a specific user** 1. Review the parameter description and requirements: @@ -88,9 +88,7 @@ This topic explains the following procedures:
-   - -**To allow only administrators to enable connection groups** +**To allow only administrators to enable connection groups** 1. Review the description and requirement for using this cmdlet: @@ -126,8 +124,6 @@ This topic explains the following procedures: -   - **Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issu**e? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv). ## Related topics diff --git a/mdop/appv-v5/how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell51.md b/mdop/appv-v5/how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell51.md index 695e3e6d58..c78817a012 100644 --- a/mdop/appv-v5/how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell51.md +++ b/mdop/appv-v5/how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell51.md @@ -27,7 +27,7 @@ This topic explains the following procedures: - [To allow only administrators to enable connection groups](#bkmk-admin-only-posh-topic-cg) -**To add and publish the App-V packages in the connection group** +*To add and publish the App-V packages in the connection group** 1. To add and publish the App-V 5.1 packages to the computer running the App-V client, type the following command: @@ -35,7 +35,7 @@ This topic explains the following procedures: 2. Repeat **step 1** of this procedure for each package in the connection group. -**To add and enable the connection group on the App-V client** +**To add and enable the connection group on the App-V client** 1. Add the connection group by typing the following command: @@ -47,7 +47,7 @@ This topic explains the following procedures: When any virtual applications that are in the member packages are run on the target computer, they will run inside the connection group’s virtual environment and will be available to all the virtual applications in the other packages in the connection group. -**To enable or disable a connection group for a specific user** +**To enable or disable a connection group for a specific user** 1. Review the parameter description and requirements: @@ -88,9 +88,7 @@ This topic explains the following procedures: -   - -**To allow only administrators to enable connection groups** +**To allow only administrators to enable connection groups** 1. Review the description and requirement for using this cmdlet: diff --git a/mdop/appv-v5/how-to-modify-an-existing-virtual-application-package-51.md b/mdop/appv-v5/how-to-modify-an-existing-virtual-application-package-51.md index deb1811f39..0d98c22478 100644 --- a/mdop/appv-v5/how-to-modify-an-existing-virtual-application-package-51.md +++ b/mdop/appv-v5/how-to-modify-an-existing-virtual-application-package-51.md @@ -31,7 +31,7 @@ This topic explains how to: - If you click **Modify an Existing Virtual Application Package** in the Sequencer in order to edit a package, but then make no changes and close the package, the streaming behavior of the package is changed. The primary feature block is removed from the StreamMap.xml file, and any files that were listed in the publishing feature block are removed. Users who receive the edited package experience that package as if it were stream-faulted, regardless of how the original package was configured. -**Update an application in an existing virtual application package** +**Update an application in an existing virtual application package** 1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. @@ -46,8 +46,6 @@ This topic explains how to: **Important**   If you are required to disable virus scanning software, first scan the computer that runs the sequencer to ensure that no unwanted or malicious files are added to the package. -   - 6. On the **Select Installer** page, click **Browse** and specify the update installation file for the application. If the update does not have an associated installer file, and if you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**. 7. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the application update so the sequencer can monitor the installation process. If additional installation files must be run as part of the installation, click **Run**, and then locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**. @@ -55,16 +53,12 @@ This topic explains how to: **Note**   The sequencer monitors all changes and installations that occur on the computer that runs the sequencer. This includes any changes and installations that are performed outside of the sequencing wizard. -   - 8. On the **Installation Report** page, you can review information about the updated virtual application. In **Additional Information**, double-click the event to obtain more detailed information. To proceed, click **Next**. 9. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all of the applications to run. After all applications have run, close each of the applications, and then click **Next**. **Note**   - You can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop**, and then select either **Stop all applications** or **Stop this application only**. - -   + You can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop**, and then select either **Stop all applications** or **Stop this application only**.   10. On the **Create Package** page, to modify the package without saving it, select the check box for **Continue to modify package without saving using the package editor**. When you select this option, the package opens in the App-V Sequencer console, where you can modify the package before it is saved. Click **Next**. @@ -72,7 +66,7 @@ This topic explains how to: 11. On the **Completion** page, click **Close** to close the wizard. The package is now available in the sequencer. -**Modify the properties associated with an existing virtual application package** +**Modify the properties associated with an existing virtual application package** 1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. @@ -111,11 +105,9 @@ This topic explains how to: **Note**   To edit shortcuts or file type associations, you must first open the package for upgrade to add a new application, and then proceed to the final editing page. -   - 6. When you finish changing the package properties, click **File** > **Save** to save the package. -**Add a new application to an existing virtual application package** +**Add a new application to an existing virtual application package** 1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. @@ -130,8 +122,6 @@ This topic explains how to: **Important**   If you are required to disable virus scanning software, first scan the computer that runs the sequencer to ensure that no unwanted or malicious files can be added to the package. -   - 6. On the **Select Installer** page, click **Browse** and specify the installation file for the application. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**. 7. On the **Installation** page, when the sequencer and application installer are ready, install the application so that the sequencer can monitor the installation process. If additional installation files must be run as part of the installation, click **Run**, and locate and run the additional installation files. When you finish the installation, select **I am finished installing** > **Next**. In the **Browse for Folder** dialog box, specify the primary directory where the application will be installed. Ensure that this is a new location so that you don’t overwrite the existing version of the virtual application package. @@ -139,8 +129,6 @@ This topic explains how to: **Note**   The sequencer monitors all changes and installations that occur on the computer that runs the sequencer. This includes any changes and installations that are performed outside of the sequencing wizard. -   - 8. On the **Configure Software** page, optionally run the programs contained in the package. This step completes any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at the same time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs you want to run, and then click **Run Selected**. Complete the required configuration tasks and then close the applications. It can take several minutes for all programs to run. Click **Next**. 9. On the **Installation Report** page, you can review information about the updated virtual application. In **Additional Information**, double-click the event to obtain more detailed information, and then click **Next** to open the **Customize** page. @@ -154,8 +142,6 @@ This topic explains how to: **Note**   You can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and then select either **Stop all applications** or **Stop this application only**. -   - 12. On the **Create Package** page, to modify the package without saving it, select the **Continue to modify package without saving using the package editor** check box. Selecting this option opens the package in the App-V Sequencer console, where you can modify the package before saving it. Click **Next**. To save the package immediately, select the default **Save the package now**. Add optional **Comments** to associate with the package. Comments are useful for providing application versions and other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. The uncompressed package size is displayed. Click **Create**. @@ -166,7 +152,6 @@ This topic explains how to: ## Related topics - [Operations for App-V 5.1](operations-for-app-v-51.md)   diff --git a/mdop/appv-v5/how-to-modify-an-existing-virtual-application-package-beta.md b/mdop/appv-v5/how-to-modify-an-existing-virtual-application-package-beta.md index bb5bf4b894..a1e697e16a 100644 --- a/mdop/appv-v5/how-to-modify-an-existing-virtual-application-package-beta.md +++ b/mdop/appv-v5/how-to-modify-an-existing-virtual-application-package-beta.md @@ -31,7 +31,7 @@ This topic explains how to: - If you click **Modify an Existing Virtual Application Package** in the Sequencer in order to edit a package, but then make no changes and close the package, the streaming behavior of the package is changed. The primary feature block is removed from the StreamMap.xml file, and any files that were listed in the publishing feature block are removed. Users who receive the edited package experience that package as if it were stream-faulted, regardless of how the original package was configured. -**Update an application in an existing virtual application package** +**Update an application in an existing virtual application package** 1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. @@ -46,8 +46,6 @@ This topic explains how to: **Important**   If you are required to disable virus scanning software, first scan the computer that runs the sequencer to ensure that no unwanted or malicious files are added to the package. -   - 6. On the **Select Installer** page, click **Browse** and specify the update installation file for the application. If the update does not have an associated installer file, and if you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**. 7. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the application update so the sequencer can monitor the installation process. If additional installation files must be run as part of the installation, click **Run**, and then locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**. @@ -55,8 +53,6 @@ This topic explains how to: **Note**   The sequencer monitors all changes and installations that occur on the computer that runs the sequencer. This includes any changes and installations that are performed outside of the sequencing wizard. -   - 8. On the **Installation Report** page, you can review information about the updated virtual application. In **Additional Information**, double-click the event to obtain more detailed information. To proceed, click **Next**. 9. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all of the applications to run. After all applications have run, close each of the applications, and then click **Next**. @@ -64,15 +60,13 @@ This topic explains how to: **Note**   You can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop**, and then select either **Stop all applications** or **Stop this application only**. -   - 10. On the **Create Package** page, to modify the package without saving it, select the check box for **Continue to modify package without saving using the package editor**. When you select this option, the package opens in the App-V Sequencer console, where you can modify the package before it is saved. Click **Next**. To save the package immediately, select the default **Save the package now**. Add optional **Comments** to associate with the package. Comments are useful to identify the application version and provide other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. Click **Create**. 11. On the **Completion** page, click **Close** to close the wizard. The package is now available in the sequencer. -**Modify the properties associated with an existing virtual application package** +**Modify the properties associated with an existing virtual application package** 1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. @@ -101,11 +95,9 @@ This topic explains how to: **Note**   To edit shortcuts or file type associations, you must first open the package for upgrade to add a new application, and then proceed to the final editing page. -   - 6. When you finish changing the package properties, click **File** > **Save** to save the package. -**Add a new application to an existing virtual application package** +**Add a new application to an existing virtual application package** 1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**. @@ -120,8 +112,6 @@ This topic explains how to: **Important**   If you are required to disable virus scanning software, first scan the computer that runs the sequencer to ensure that no unwanted or malicious files can be added to the package. -   - 6. On the **Select Installer** page, click **Browse** and specify the installation file for the application. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**. 7. On the **Installation** page, when the sequencer and application installer are ready, install the application so that the sequencer can monitor the installation process. If additional installation files must be run as part of the installation, click **Run**, and locate and run the additional installation files. When you finish the installation, select **I am finished installing** > **Next**. In the **Browse for Folder** dialog box, specify the primary directory where the application will be installed. Ensure that this is a new location so that you don’t overwrite the existing version of the virtual application package. @@ -129,8 +119,6 @@ This topic explains how to: **Note**   The sequencer monitors all changes and installations that occur on the computer that runs the sequencer. This includes any changes and installations that are performed outside of the sequencing wizard. -   - 8. On the **Configure Software** page, optionally run the programs contained in the package. This step completes any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at the same time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs you want to run, and then click **Run Selected**. Complete the required configuration tasks and then close the applications. It can take several minutes for all programs to run. Click **Next**. 9. On the **Installation Report** page, you can review information about the updated virtual application. In **Additional Information**, double-click the event to obtain more detailed information, and then click **Next** to open the **Customize** page. @@ -144,8 +132,6 @@ This topic explains how to: **Note**   You can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and then select either **Stop all applications** or **Stop this application only**. -   - 12. On the **Create Package** page, to modify the package without saving it, select the **Continue to modify package without saving using the package editor** check box. Selecting this option opens the package in the App-V Sequencer console, where you can modify the package before saving it. Click **Next**. To save the package immediately, select the default **Save the package now**. Add optional **Comments** to associate with the package. Comments are useful for providing application versions and other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. The uncompressed package size is displayed. Click **Create**. @@ -156,7 +142,6 @@ This topic explains how to: ## Related topics - [Operations for App-V 5.0](operations-for-app-v-50.md)   diff --git a/mdop/medv-v2/configuring-a-windows-virtual-pc-image-for-med-v.md b/mdop/medv-v2/configuring-a-windows-virtual-pc-image-for-med-v.md index c4a9a942e4..548d28f073 100644 --- a/mdop/medv-v2/configuring-a-windows-virtual-pc-image-for-med-v.md +++ b/mdop/medv-v2/configuring-a-windows-virtual-pc-image-for-med-v.md @@ -51,7 +51,7 @@ Follow these steps to configure your MED-V image for running first time setup: After you have completed customization of your MED-V image, you are ready to seal the image by using Sysprep. -**Sealing the MED-V Image by Using Sysprep** +**Sealing the MED-V Image by Using Sysprep** 1. The System Preparation tool (Sysprep) is a technology that you can use to perform image-based installations throughout the network with minimal intervention by an administrator or IT-Professional. diff --git a/mdop/uev-v2/configuring-ue-v-2x-with-system-center-configuration-manager-2012-both-uevv2.md b/mdop/uev-v2/configuring-ue-v-2x-with-system-center-configuration-manager-2012-both-uevv2.md index 637c1fbc36..acfc53f384 100644 --- a/mdop/uev-v2/configuring-ue-v-2x-with-system-center-configuration-manager-2012-both-uevv2.md +++ b/mdop/uev-v2/configuring-ue-v-2x-with-system-center-configuration-manager-2012-both-uevv2.md @@ -103,9 +103,7 @@ It might be necessary to change the PowerShell execution policy to allow these s 2. In the **User Agent** tab, set the **PowerShell Execution Policy** to **Bypass** -  - -**Create the First UE-V Policy Configuration Item** +**Create the First UE-V Policy Configuration Item** 1. Copy the default settings configuration file from the UE-V Config Pack installation directory to a location visible to your ConfigMgr Admin Console: @@ -173,8 +171,6 @@ It might be necessary to change the PowerShell execution policy to allow these s 3. Reimport the CAB file. The version in ConfigMgr will be updated. ## Generate a UE-V Template Baseline - - UE-V templates are distributed using a baseline containing multiple configuration items. Each configuration item contains the discovery and remediation scripts needed to install one UE-V template. The actual UE-V template is embedded within the remediation script for distribution using standard Configuration Item functionality. The UE-V template baseline is created using the UevTemplateBaselineGenerator.exe command line tool, which has these parameters: @@ -195,7 +191,7 @@ The UE-V template baseline is created using the UevTemplateBaselineGenerator.exe The result is a baseline CAB file that is ready for import into Configuration Manager. If at a future date, you update or add a template, you can rerun the command using the same baseline name. Importing the CAB results in CI version updates on the changed templates. -### Create the First UE-V Template Baseline +### Create the First UE-V Template Baseline 1. Create a “master” set of UE-V templates in a stable folder location visible to the machine running your ConfigMgr Admin Console. As templates are added or updated, this folder is where they are pulled for distribution. The initial list of templates can be copied from a machine with UE-V installed. The default template location is C:\\Program Files\\Microsoft User Experience Virtualization\\Templates. From ea0a02fe9f9eeaf3bdff21857341f8d4870a9d98 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Tue, 1 Nov 2016 13:17:42 -0700 Subject: [PATCH 3/3] Fixing broken bookmarks --- mdop/medv-v2/how-to-test-application-publishing.md | 7 +------ mdop/medv-v2/how-to-test-url-redirection.md | 9 +-------- ...uring-uev-with-system-center-configuration-manager.md | 7 ++----- windows/manage/uev-prepare-for-deployment.md | 2 -- 4 files changed, 4 insertions(+), 21 deletions(-) diff --git a/mdop/medv-v2/how-to-test-application-publishing.md b/mdop/medv-v2/how-to-test-application-publishing.md index ad7c458632..7791f99e06 100644 --- a/mdop/medv-v2/how-to-test-application-publishing.md +++ b/mdop/medv-v2/how-to-test-application-publishing.md @@ -15,7 +15,7 @@ ms.prod: w7 After your test of first time setup finishes, you can verify that the application publishing functionality is working as expected by performing the following tasks. -**To test application publishing** +**To test application publishing** 1. Verify that the applications that you specified for publishing are visible. @@ -34,8 +34,6 @@ After your test of first time setup finishes, you can verify that the applicatio **Important**   Because Windows Virtual PC does not support creating a share from a folder that is already shared, redirection does not occur for any documents that open from a shared folder, such as a My Documents folder that is located on the network. For more information, see [Operations Troubleshooting](operations-troubleshooting-medv2.md). -   - After you have verified that published applications are installed and functioning correctly, you can test whether applications can be added or removed from the MED-V workspace. **To test that an application can be added or removed** @@ -51,15 +49,12 @@ After you have verified that published applications are installed and functionin **Note**   If you encounter any problems when verifying your application publication settings, see [Operations Troubleshooting](operations-troubleshooting-medv2.md). -  - After you have completed testing application publishing, you can test other MED-V workspace configurations to verify that they function as intended. After you have completed testing your MED-V workspace package and have verified that it is functioning as intended, you can deploy the MED-V workspace to your enterprise. ## Related topics - [How to Test URL Redirection](how-to-test-url-redirection.md) [How to Verify First Time Setup Settings](how-to-verify-first-time-setup-settings.md) diff --git a/mdop/medv-v2/how-to-test-url-redirection.md b/mdop/medv-v2/how-to-test-url-redirection.md index 292c86b05c..21781c9cab 100644 --- a/mdop/medv-v2/how-to-test-url-redirection.md +++ b/mdop/medv-v2/how-to-test-url-redirection.md @@ -18,9 +18,7 @@ After your test of first time setup finishes, you can verify that the URL redire **Important**   The MED-V Host Agent must be running for URL redirection to function correctly. -  - -**To test URL Redirection** +**To test URL Redirection** 1. Open an Internet Explorer browser in the host computer and enter a URL that you specified for redirection. @@ -45,20 +43,15 @@ The MED-V Host Agent must be running for URL redirection to function correctly. **Note**   It can take several seconds for the URL redirection changes to take place. -   - **Note**   If you encounter any problems when verifying your URL redirection settings, see [Operations Troubleshooting](operations-troubleshooting-medv2.md). -  - After you have completed testing URL redirection in your MED-V workspace, you can test other configurations to verify that they function as intended. After you have completed testing your MED-V workspace package and have verified that it is functioning as intended, you can deploy the MED-V workspace to your enterprise. ## Related topics - [How to Test Application Publishing](how-to-test-application-publishing.md) [How to Verify First Time Setup Settings](how-to-verify-first-time-setup-settings.md) diff --git a/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md b/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md index e18bff1e74..c81a7384be 100644 --- a/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md +++ b/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md @@ -18,7 +18,6 @@ After you deploy User Experience Virtualization (UE-V) and its required features ## UE-V Configuration Pack supported features - The UE-V Configuration Pack includes tools to: - Create or update UE-V settings location template distribution baselines @@ -103,10 +102,9 @@ It might be necessary to change the PowerShell execution policy to allow these s 1. Select **Administration > Client Settings > Properties** 2. In the **User Agent** tab, set the **PowerShell Execution Policy** to **Bypass** -   -**Create the first UE-V policy configuration item** +**Create the first UE-V policy configuration item** 1. Copy the default settings configuration file from the UE-V Config Pack installation directory to a location visible to your ConfigMgr Admin Console: @@ -173,8 +171,7 @@ It might be necessary to change the PowerShell execution policy to allow these s 3. Reimport the CAB file. The version in ConfigMgr will be updated. -## Generate a UE-V Template Baseline - +## Generate a UE-V Template Baseline UE-V templates are distributed using a baseline containing multiple configuration items. Each configuration item contains the discovery and remediation scripts needed to install one UE-V template. The actual UE-V template is embedded within the remediation script for distribution using standard Configuration Item functionality. diff --git a/windows/manage/uev-prepare-for-deployment.md b/windows/manage/uev-prepare-for-deployment.md index 0fa6f10ff2..b66d90a0ce 100644 --- a/windows/manage/uev-prepare-for-deployment.md +++ b/windows/manage/uev-prepare-for-deployment.md @@ -25,8 +25,6 @@ Whether you want to synchronize settings for only default Windows applications o - [Define a settings storage location](uev-deploy-required-features.md#ssl) -- [Decide how to manage UE-V configurations](#config) - - [Enable the UE-V service](uev-deploy-required-features.md#enable-the-ue-v-service) on user computers If you want to use UE-V to synchronize user-defined settings for custom applications (third-party or line-of-business), you’ll need to install and configure these optional additional UE-V features: