From c7b5a886b0396fa6fe0a38ebd026f11bcb7cd108 Mon Sep 17 00:00:00 2001 From: JanKeller1 Date: Fri, 12 Aug 2016 14:21:55 -0700 Subject: [PATCH] Link fixes, plus a few fixes to typos --- ...ation-publishing-and-client-interaction.md | 2 +- windows/manage/appv-deploy-the-appv-server.md | 2 +- ...eploying-microsoft-office-2010-wth-appv.md | 4 ++-- ...ploying-microsoft-office-2013-with-appv.md | 22 +++++-------------- ...ctronic-software-distribution-solutions.md | 2 +- windows/manage/appv-planning-checklist.md | 2 +- .../manage/appv-planning-to-deploy-appv.md | 4 ++-- .../manage/appv-security-considerations.md | 4 ++-- .../manage/appv-sequence-a-new-application.md | 18 +++++---------- 9 files changed, 21 insertions(+), 39 deletions(-) diff --git a/windows/manage/appv-application-publishing-and-client-interaction.md b/windows/manage/appv-application-publishing-and-client-interaction.md index d9e5931749..fdec3fdd21 100644 --- a/windows/manage/appv-application-publishing-and-client-interaction.md +++ b/windows/manage/appv-application-publishing-and-client-interaction.md @@ -1059,7 +1059,7 @@ For situations where there is more than one application that could register the The AppPath extension point supports calling App-V applications directly from the operating system. This is typically accomplished from the Run or Start Screen, depending on the operating system, which enables administrators to provide access to App-V applications from operating system commands or scripts without calling the specific path to the executable. It therefore avoids modifying the system path environment variable on all systems, as it is accomplished during publishing. -The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: [App Paths ? A Virtual Application Extension in App-V 5.0](https://blogs.technet.microsoft.com/virtualworld/2012/12/12/app-paths-a-virtual-application-extension-in-app-v-5-0/). +The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: [App Paths - A Virtual Application Extension in App-V 5.0](https://blogs.technet.microsoft.com/virtualworld/2012/12/12/app-paths-a-virtual-application-extension-in-app-v-5-0/). ### Virtual application diff --git a/windows/manage/appv-deploy-the-appv-server.md b/windows/manage/appv-deploy-the-appv-server.md index c85f273c6c..16d49c34e8 100644 --- a/windows/manage/appv-deploy-the-appv-server.md +++ b/windows/manage/appv-deploy-the-appv-server.md @@ -8,7 +8,7 @@ ms.sitesec: library ms.prod: w10 --- -# How to Deploy the App-V Server (new installataion) +# How to Deploy the App-V Server (new installation) >**Important**
If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released. diff --git a/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md b/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md index 87112ed665..fe452de031 100644 --- a/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md @@ -72,9 +72,9 @@ Sequencing Office 2010 is one of the main methods for creating an Office 2010 pa Office 2010 App-V packages can be created through package accelerators. Microsoft has provided package accelerators for creating Office 2010 on Windows 10, Windows 8 and Windows 7. To create Office 2010 packages on App-V using Package accelerators, refer to the following pages to access the appropriate package accelerator: -- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](http://go.microsoft.com/fwlink/p/?LinkId=330677) +- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](https://gallery.technet.microsoft.com/App-V-50-Package-a29410db) -- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](http://go.microsoft.com/fwlink/p/?LinkId=330678) +- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](https://gallery.technet.microsoft.com/App-V-50-Package-e7ef536b) For detailed instructions on how to create virtual application packages using App-V package accelerators, see [How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md). diff --git a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md index 1664333c9f..f441e4af00 100644 --- a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md @@ -133,7 +133,7 @@ The following table describes the recommended methods for excluding specific Off

Use the ExcludeApp setting when you create the package by using the Office Deployment Tool.

@@ -205,7 +205,7 @@ Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the Office 2013 App-V Packages are created using the Office Deployment Tool, which generates an Office 2013 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation: -1. Download the [Office Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778). +1. Download the [Office 2013 Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778). 2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved. @@ -810,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](https://technet.microsoft.com/en-us/itpro/mdop/solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions#bkmk-pkg-pub-reqs).

+

If you aren’t deploying Office, you can create a package that contains Visio and/or Project.

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

@@ -841,7 +841,7 @@ The following table describes the requirements and options for deploying Visio 2

  1. Create a package that contains Office, Visio, and Project.

  2. Deploy the package to all users.

    3. -

  3. Use [Microsoft AppLocker](http://technet.microsoft.com/library/dd723678.aspx) to prevent specific users from using Visio and Project.

    4. +

  4. Use [AppLocker](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/applocker-overview) to prevent specific users from using Visio and Project.

@@ -858,13 +858,13 @@ The following table describes the requirements and options for deploying Visio 2 **Office 2013 App-V Packages Additional Resources** -[Office Deployment Tool for Click-to-Run](http://go.microsoft.com/fwlink/p/?LinkID=330672) +[Office 2013 Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778) [Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://support.microsoft.com/en-us/kb/2772509) **Office 2010 App-V Packages** -[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://www.microsoft.com/en-us/download/details.aspx?id=38399) +[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://www.microsoft.com/download/details.aspx?id=38399) [Known issues when you create or use an App-V 5.0 Office 2010 package](https://support.microsoft.com/en-us/kb/2828619) @@ -882,14 +882,4 @@ The following table describes the requirements and options for deploying Visio 2 ## Have a suggestion for App-V? - 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/en-US/home?forum=mdopappv). - -  - -  - - - - - diff --git a/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md b/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md index 67811c04b2..ca135a0bea 100644 --- a/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md +++ b/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md @@ -19,7 +19,7 @@ To deploy App-V packages with Microsoft System Center 2012 Configuration Manage ## How to deploy virtualized packages using an ESD -Describes the methods you can use to deploy App-V packages by using an ESD +Describes the methods you can use to deploy App-V packages by using an ESD. [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md) diff --git a/windows/manage/appv-planning-checklist.md b/windows/manage/appv-planning-checklist.md index 91d7f0fe4e..b059e11863 100644 --- a/windows/manage/appv-planning-checklist.md +++ b/windows/manage/appv-planning-checklist.md @@ -60,7 +60,7 @@ This checklist can be used to help you plan for preparing your organization for Checklist box

If applicable, review the options and steps for migrating from a previous version of App-V.

-

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

+

[Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)

diff --git a/windows/manage/appv-planning-to-deploy-appv.md b/windows/manage/appv-planning-to-deploy-appv.md index 997ba3e4e0..292322be4f 100644 --- a/windows/manage/appv-planning-to-deploy-appv.md +++ b/windows/manage/appv-planning-to-deploy-appv.md @@ -9,7 +9,7 @@ ms.prod: w10 --- -# Planning to Deploy App-V for Windows 0 +# Planning to Deploy App-V for Windows 10 Applies to: Windows 10, version 1607 @@ -55,7 +55,7 @@ Describes the planning considerations for the App-V Client and for the Sequencer Describes the recommended path for migrating from previous versions of App-V, while ensuring that existing server configurations, packages and clients continue to work in your new App-V environment. -[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md) +[Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) ## Planning for using App-V with Office diff --git a/windows/manage/appv-security-considerations.md b/windows/manage/appv-security-considerations.md index 79d71d971a..944d707b04 100644 --- a/windows/manage/appv-security-considerations.md +++ b/windows/manage/appv-security-considerations.md @@ -31,9 +31,9 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that wa **Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver. -**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, subscribe to the Security Notification service (). +**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, see the [Microsoft Security TechCenter](https://technet.microsoft.com/en-us/security/bb291012). -**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see the “Account Passwords and Policies” white paper on TechNet (). +**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see [Password Policy](https://technet.microsoft.com/library/hh994572.aspx). ## Accounts and groups in App-V diff --git a/windows/manage/appv-sequence-a-new-application.md b/windows/manage/appv-sequence-a-new-application.md index a860b731e8..c9d6937c78 100644 --- a/windows/manage/appv-sequence-a-new-application.md +++ b/windows/manage/appv-sequence-a-new-application.md @@ -53,11 +53,9 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD > [!NOTE] > If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package. - - + If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then click **Next**. - 6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console. Click **Next**. @@ -66,8 +64,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD > [!IMPORTANT] > You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring. - - + Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**. 8. On the **Installation** page, wait while the sequencer configures the virtualized application package. @@ -76,8 +73,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD > [!NOTE] > To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step. - - + Click **Next**. 10. On the **Installation Report** page, you can review information about the virtualized application package you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**. @@ -109,9 +105,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD > [!IMPORTANT] > The system does not support non-printable characters in **Comments** and **Descriptions**. - -   - +   The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**. 15. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory where the package was created. @@ -179,9 +173,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD > [!IMPORTANT]    > The system does not support non-printable characters in Comments and Descriptions. - -   - + The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**. **To sequence a middleware application**