From ea9f7e3c25bef6f6f92b52af9f840d4901b4c038 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 2 Nov 2016 07:11:02 -0700 Subject: [PATCH 01/10] Fixed broken formatting --- ...-configuring-uev-with-system-center-configuration-manager.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 ec06465c51..a0b3bf91d3 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 @@ -171,7 +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. From 78477ac908151ef260a6eea1b4bf61c468f86de5 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 2 Nov 2016 07:45:41 -0700 Subject: [PATCH 02/10] Fixed broken formatting --- mdop/mbam-v25/planning-for-mbam-25-groups-and-accounts.md | 2 +- ...-with-system-center-configuration-manager-2012-both-uevv2.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/mdop/mbam-v25/planning-for-mbam-25-groups-and-accounts.md b/mdop/mbam-v25/planning-for-mbam-25-groups-and-accounts.md index 6515783c38..e651abbd0b 100644 --- a/mdop/mbam-v25/planning-for-mbam-25-groups-and-accounts.md +++ b/mdop/mbam-v25/planning-for-mbam-25-groups-and-accounts.md @@ -103,7 +103,7 @@ Create the following accounts for the Reports feature.   -## Administration and Monitoring Website (Help Desk) accounts +## Administration and Monitoring Website (Help Desk) accounts Create the following accounts for the Administration and Monitoring Website. diff --git a/mdop/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 5806ca016a..cecf6f4ceb 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 @@ -191,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 3affd9be09fec4416b17fd15a015198b99be43cc Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 2 Nov 2016 08:28:20 -0700 Subject: [PATCH 03/10] Fixing broken bookmarks --- .../deploying-microsoft-office-2013-by-using-app-v.md | 9 +-------- ...eploying-microsoft-office-2013-by-using-app-v51.md | 3 +-- ...e-powershell-cmdlets-and-get-cmdlet-help-50-sp3.md | 10 ++-------- ...d-the-powershell-cmdlets-and-get-cmdlet-help-51.md | 11 +---------- 4 files changed, 5 insertions(+), 28 deletions(-) diff --git a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md b/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md index a0615d5921..dfb5138d48 100644 --- a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md +++ b/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md @@ -157,7 +157,6 @@ Complete the following steps to create an Office 2013 package for App-V 5.0 or l **Important**   In App-V 5.0 and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages. -  ### Review prerequisites for using the Office Deployment Tool @@ -189,11 +188,9 @@ The computer on which you are installing the Office Deployment Tool must have: -  **Note**   In this topic, the term “Office 2013 App-V package” refers to subscription licensing and volume licensing. -   ### Create Office 2013 App-V Packages Using Office Deployment Tool @@ -242,8 +239,6 @@ The XML file that is included in the Office Deployment Tool specifies the produc **Note**   The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. -   - The above XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file: @@ -300,8 +295,6 @@ The XML file that is included in the Office Deployment Tool specifies the produc
-   - After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2013 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml. 2. **Download the applications into the specified location:** Use an elevated command prompt and a 64 bit operating system to download the Office 2013 applications that will later be converted into an App-V package. Below is an example command with description of details: @@ -811,7 +804,7 @@ The following table describes the requirements and options for deploying Visio 2

How do I package and publish Visio 2013 and Project 2013 with Office?

You must include Visio 2013 and Project 2013 in the same package with Office.

-

If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the [Virtualizing Microsoft Office 2013 for Application Virtualization (App-V) 5.0](../solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions.md#bkmk-pkg-pub-reqs).

+

If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow [Deploying Microsoft Office 2010 by Using App-V](../appv-v5/deploying-microsoft-office-2010-by-using-app-v.md).

How can I deploy Visio 2013 and Project 2013 to specific users?

diff --git a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md b/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md index cc8b0e0899..f3fcc6f7b2 100644 --- a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md +++ b/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md @@ -62,7 +62,6 @@ Use the following table to get information about supported versions of Office an   - ### Packaging, publishing, and deployment requirements Before you deploy Office by using App-V, review the following requirements. @@ -811,7 +810,7 @@ The following table describes the requirements and options for deploying Visio 2

How do I package and publish Visio 2013 and Project 2013 with Office?

You must include Visio 2013 and Project 2013 in the same package with Office.

-

If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the [Virtualizing Microsoft Office 2013 for Application Virtualization (App-V) 5.0](../solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions.md#bkmk-pkg-pub-reqs).

+

If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow [Deploying Microsoft Office 2010 by Using App-V](../appv-v5/deploying-microsoft-office-2010-by-using-app-v.md).

How can I deploy Visio 2013 and Project 2013 to specific users?

diff --git a/mdop/appv-v5/how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-50-sp3.md b/mdop/appv-v5/how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-50-sp3.md index 766726e8e7..c4ee8b5811 100644 --- a/mdop/appv-v5/how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-50-sp3.md +++ b/mdop/appv-v5/how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-50-sp3.md @@ -93,7 +93,7 @@ Review the following requirements for using the App-V PowerShell cmdlets:

Enable the “Require publish as administrator” Group Policy setting for App-V Clients.

-

[How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md#bkmk-admin-pub-pkg-only-posh)

+

[How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md)

@@ -105,8 +105,6 @@ Review the following requirements for using the App-V PowerShell cmdlets:   ## Loading the PowerShell cmdlets - - To load the PowerShell cmdlet modules: 1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). @@ -143,8 +141,6 @@ To load the PowerShell cmdlet modules:   ## Getting help for the PowerShell cmdlets - - Starting in App-V 5.0 SP3, cmdlet help is available in two formats: @@ -204,15 +200,13 @@ Starting in App-V 5.0 SP3, cmdlet help is available in two formats:   ## Displaying the help for a PowerShell cmdlet - - To display help for a specific PowerShell cmdlet: 1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). 2. Type **Get-Help** <*cmdlet*>, for example, **Get-Help Publish-AppvClientPackage**. -**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). +**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 issue**? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).   diff --git a/mdop/appv-v5/how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-51.md b/mdop/appv-v5/how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-51.md index f3bec5b881..48ae9d7cf8 100644 --- a/mdop/appv-v5/how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-51.md +++ b/mdop/appv-v5/how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-51.md @@ -93,7 +93,7 @@ Review the following requirements for using the App-V PowerShell cmdlets: - +

Enable the “Require publish as administrator” Group Policy setting for App-V Clients.

[How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-51.md#bkmk-admin-pub-pkg-only-posh)

[How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-51.md)

@@ -106,7 +106,6 @@ Review the following requirements for using the App-V PowerShell cmdlets: ## Loading the PowerShell cmdlets - To load the PowerShell cmdlet modules: 1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). @@ -140,11 +139,7 @@ To load the PowerShell cmdlet modules: -  - ## Getting help for the PowerShell cmdlets - - Starting in App-V 5.0 SP3, cmdlet help is available in two formats: @@ -201,11 +196,7 @@ Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
-  - ## Displaying the help for a PowerShell cmdlet - - To display help for a specific PowerShell cmdlet: 1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). From 1e1a94221ebc6de7482861f6358dbf68e8a09b29 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 2 Nov 2016 08:35:14 -0700 Subject: [PATCH 04/10] Fixing broken bookmarks --- mdop/appv-v5/about-app-v-50-sp3.md | 4 ++-- .../using-windows-powershell-to-administer-mbam-25.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/mdop/appv-v5/about-app-v-50-sp3.md b/mdop/appv-v5/about-app-v-50-sp3.md index aeca744a26..4ea53c7fc1 100644 --- a/mdop/appv-v5/about-app-v-50-sp3.md +++ b/mdop/appv-v5/about-app-v-50-sp3.md @@ -109,7 +109,7 @@ Review the following information before you start the upgrade:

You must first upgrade to App-V 5.0. You cannot upgrade directly from App-V 4.x to App-V 5.0 SP3.

For more information, see:

    -
  • [About App-V 5.0](about-app-v-50.md#bkmk-diffs-46-50)

  • +
  • [About App-V 5.0](about-app-v-50.md)

  • [Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md)

@@ -521,7 +521,7 @@ You can manage connection groups more easily by using optional packages and othe

Management console

-

[How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md#bkmk-admin-pub-pkg-only-posh)

+

[How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md)

PowerShell

diff --git a/mdop/mbam-v25/using-windows-powershell-to-administer-mbam-25.md b/mdop/mbam-v25/using-windows-powershell-to-administer-mbam-25.md index 41833fc753..a10a065f72 100644 --- a/mdop/mbam-v25/using-windows-powershell-to-administer-mbam-25.md +++ b/mdop/mbam-v25/using-windows-powershell-to-administer-mbam-25.md @@ -66,7 +66,7 @@ Windows PowerShell Help for MBAM cmdlets is available in the following formats:

At a Windows PowerShell command prompt, type Get-Help <cmdlet>

-

To upload the latest Windows PowerShell cmdlets, follow the instructions in [Configuring MBAM 2.5 Server Features by Using Windows PowerShell](configuring-mbam-25-server-features-by-using-windows-powershell.md#bkmk-loadposhhelp)

+

To upload the latest Windows PowerShell cmdlets, follow the instructions in [Configuring MBAM 2.5 Server Features by Using Windows PowerShell](configuring-mbam-25-server-features-by-using-windows-powershell.md)

On TechNet as webpages

From a766bb298d924f67ede2daea7443e37c7076be7e Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 2 Nov 2016 09:08:31 -0700 Subject: [PATCH 05/10] Fixing broken bookmarks --- .../appv-deploying-the-appv-sequencer-and-client.md | 2 +- ...ppv-load-the-powershell-cmdlets-and-get-cmdlet-help.md | 4 ++-- .../appv-planning-for-sequencer-and-client-deployment.md | 2 +- .../uev-changing-the-frequency-of-scheduled-tasks.md | 2 +- windows/manage/uev-for-windows.md | 4 ++-- windows/manage/uev-prepare-for-deployment.md | 8 ++++---- .../manage/uev-synchronizing-microsoft-office-with-uev.md | 2 +- ...ng-uev-with-application-virtualization-applications.md | 2 +- 8 files changed, 13 insertions(+), 13 deletions(-) diff --git a/windows/manage/appv-deploying-the-appv-sequencer-and-client.md b/windows/manage/appv-deploying-the-appv-sequencer-and-client.md index ca8397a1fe..21632ad793 100644 --- a/windows/manage/appv-deploying-the-appv-sequencer-and-client.md +++ b/windows/manage/appv-deploying-the-appv-sequencer-and-client.md @@ -80,7 +80,7 @@ Set-AppvClientConfiguration -SharedContentStoreMode 1 The Sequencer is a tool that is used to convert standard applications into virtual packages for deployment to computers that run the App-V client. The Sequencer helps provide a simple and predictable conversion process with minimal changes to prior sequencing workflows. In addition, the Sequencer allows users to more easily configure applications to enable connections of virtualized applications. -For a list of changes in the App-V Sequencer, see [What's new in App-V](appv-about-appv.md#bkmk-seqimprove). +For a list of changes in the App-V Sequencer, see [What's new in App-V](appv-about-appv.md). To deploy the sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md). diff --git a/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index 2c29e70fd9..e9021103ab 100644 --- a/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -75,9 +75,9 @@ Review the following requirements for using the Windows PowerShell cmdlets:

To configure these cmdlets to require an elevated command prompt, use one of the following methods:

  • Run the Set-AppvClientConfiguration cmdlet with the -RequirePublishAsAdmin parameter.

    -

    For more information, see:
    [How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md#bkmk-admin-only-posh-topic-cg)
    [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).

  • +

    For more information, see:
    [How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)
    [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).

  • Enable the “Require publish as administrator” Group Policy setting for App-V Clients.

    -

    For more information, see [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md#bkmk-admin-pub-pkg-only-posh)

  • +

    For more information, see [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md)

diff --git a/windows/manage/appv-planning-for-sequencer-and-client-deployment.md b/windows/manage/appv-planning-for-sequencer-and-client-deployment.md index bd7f629151..07c1f7c438 100644 --- a/windows/manage/appv-planning-for-sequencer-and-client-deployment.md +++ b/windows/manage/appv-planning-for-sequencer-and-client-deployment.md @@ -21,7 +21,7 @@ Before you can use App-V, you must install the App-V Sequencer, enable the App-V App-V uses a process called sequencing to create virtualized applications and application packages. Sequencing requires the use of a computer that runs the App-V Sequencer. > [!NOTE] -> For information about the new functionality of App-V sequencer, see [What's new in App-V](appv-about-appv.md#bkmk-seqimprove). +> For information about the new functionality of App-V sequencer, see [What's new in App-V](appv-about-appv.md). The computer that runs the App-V sequencer must meet the minimum system requirements. For a list of these requirements, see [App-V Supported Configurations](appv-supported-configurations.md). diff --git a/windows/manage/uev-changing-the-frequency-of-scheduled-tasks.md b/windows/manage/uev-changing-the-frequency-of-scheduled-tasks.md index 888c3b7ee1..ea6d910cb6 100644 --- a/windows/manage/uev-changing-the-frequency-of-scheduled-tasks.md +++ b/windows/manage/uev-changing-the-frequency-of-scheduled-tasks.md @@ -246,4 +246,4 @@ Add or vote on suggestions on the [User Experience Virtualization feedback site] [Administering UE-V](uev-administering-uev.md) -[Deploy UE-V for Custom Applications](uev-deploy-uev-for-custom-applications.md#deploycatalogue) +[Deploy UE-V for Custom Applications](uev-deploy-uev-for-custom-applications.md) \ No newline at end of file diff --git a/windows/manage/uev-for-windows.md b/windows/manage/uev-for-windows.md index 1f4eaab35c..8702b65318 100644 --- a/windows/manage/uev-for-windows.md +++ b/windows/manage/uev-for-windows.md @@ -54,7 +54,7 @@ Use these UE-V components to create and manage custom templates for your third-p | Component | Description | |-------------------------------|---------------| | **UE-V template generator** | Use the **UE-V template generator** to create custom settings location templates that you can then distribute to user computers. The UE-V template generator also lets you edit an existing template or validate a template that was created with a different XML editor.
With the Windows 10, version 1607 release, the UE-V template generator is installed with the [Windows Assessment and Deployment kit for Windows 10, version 1607](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) (Windows ADK).
If you are upgrading from an existing UE-V installation, you’ll need to use the new generator to create new settings location templates. Application templates created with previous versions of the UE-V template generator are still supported, however. | -| **Settings template catalog** | The **settings template catalog** is a folder path on UE-V computers or a Server Message Block (SMB) network share that stores the custom settings location templates. The UE-V service checks this location once a day, retrieves new or updated templates, and updates its synchronization behavior.
If you use only the UE-V default settings location templates, then a settings template catalog is unnecessary. For more information about settings deployment catalogs, see [Deploy a UE-V settings template catalog](uev-deploy-uev-for-custom-applications.md#deploycatalogue). | +| **Settings template catalog** | The **settings template catalog** is a folder path on UE-V computers or a Server Message Block (SMB) network share that stores the custom settings location templates. The UE-V service checks this location once a day, retrieves new or updated templates, and updates its synchronization behavior.
If you use only the UE-V default settings location templates, then a settings template catalog is unnecessary. For more information about settings deployment catalogs, see [Deploy a UE-V settings template catalog](uev-deploy-uev-for-custom-applications.md).|