diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index 8e17a52ca5..2943be7560 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -110,18 +110,18 @@ ##### [How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md) #### [Maintaining App-V](appv-maintaining-appv.md) ##### [How to Move the App-V Server to Another Computer](appv-move-the-appv-server-to-another-computer.md) -#### [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md) -##### [How to Load the PowerShell Cmdlets and Get Cmdlet Help ](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md) -##### [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md) -##### [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md) -##### [How to Modify Client Configuration by Using PowerShell](appv-modify-client-configuration-with-powershell.md) +#### [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md) +##### [How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help ](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.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) +##### [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 Modify Client Configuration by Using Windows PowerShell](appv-modify-client-configuration-with-powershell.md) ##### [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md) -##### [How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md) -##### [How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md) -##### [How to Sequence a Package by Using PowerShell ](appv-sequence-a-package-with-powershell.md) -##### [How to Create a Package Accelerator by Using PowerShell](appv-create-a-package-accelerator-with-powershell.md) -##### [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md) -##### [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md) +##### [How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md) +##### [How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md) +##### [How to Sequence a Package by Using Windows PowerShell ](appv-sequence-a-package-with-powershell.md) +##### [How to Create a Package Accelerator by Using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md) +##### [How to Enable Reporting on the App-V Client by Using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md) +##### [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md) ### [Troubleshooting App-V](appv-troubleshooting.md) ### [Technical Reference for App-V](appv-technical-reference.md) #### [Performance Guidance for Application Virtualization](appv-performance-guidance.md) diff --git a/windows/manage/appv-administering-appv-with-powershell.md b/windows/manage/appv-administering-appv-with-powershell.md index ebf327d6fb..1465d8003c 100644 --- a/windows/manage/appv-administering-appv-with-powershell.md +++ b/windows/manage/appv-administering-appv-with-powershell.md @@ -33,15 +33,15 @@ Use the following Windows PowerShell procedures to perform various App-V tasks. -

[How to Load the PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md)

+

[How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md)

Describes how to install the Windows PowerShell cmdlets and find cmdlet help and examples.

-

[How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-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)

Describes how to manage the client package lifecycle on a stand-alone computer by using Windows PowerShell.

-

[How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)

+

[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)

Describes how to manage connection groups by using Windows PowerShell.

@@ -49,27 +49,27 @@ Use the following Windows PowerShell procedures to perform various App-V tasks.

Describes how to modify the client by using Windows PowerShell.

-

[How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)

+

[How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)

Describes how to apply a user configuration file by using Windows PowerShell.

-

[How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)

+

[How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)

Describes how to apply a deployment configuration file by using Windows PowerShell.

-

[How to Sequence a Package by Using PowerShell](appv-sequence-a-package-with-powershell.md)

+

[How to Sequence a Package by Using Windows PowerShell](appv-sequence-a-package-with-powershell.md)

Describes how to create a new package by using Windows PowerShell.

-

[How to Create a Package Accelerator by Using PowerShell](appv-create-a-package-accelerator-with-powershell.md)

+

[How to Create a Package Accelerator by Using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md)

Describes how to create a package accelerator by using Windows PowerShell. You can use package accelerators automatically sequence large, complex applications.

-

[How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)

+

[How to Enable Reporting on the App-V Client by Using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)

Describes how to enable the computer running the App-V to send reporting information.

-

[How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)

+

[How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)

Describes how to take an array of account names and to convert each of them to the corresponding SID in standard and hexadecimal formats.

@@ -90,7 +90,7 @@ Make sure that any script you execute with your App-V packages matches the execu ## Windows PowerShell Error Handling -Use the following table for information about App-V PowerShell error handling. +Use the following table for information about Windows PowerShell error handling for App-V. @@ -116,8 +116,8 @@ Use the following table for information about App-V PowerShell error handling. - +

Package name contains $

If a package name contains the character ( $ ), you must use a single-quote ( ‘ ), for example,

-

Add-AppvClientPackage ‘Contoso$App.appv’

If a package name contains the character ( $ ), you must use a single-quote ( ' ), for example,

+

Add-AppvClientPackage 'Contoso$App.appv'
diff --git a/windows/manage/appv-allow-administrators-to-enable-connection-groups.md b/windows/manage/appv-allow-administrators-to-enable-connection-groups.md index 0084b4a351..22b2aa8250 100644 --- a/windows/manage/appv-allow-administrators-to-enable-connection-groups.md +++ b/windows/manage/appv-allow-administrators-to-enable-connection-groups.md @@ -15,10 +15,8 @@ Applies to: Windows 10, version 1607 You can configure the App-V client so that only administrators (not end users) can enable or disable connection groups. In earlier versions of App-V, you could not prevent end users from performing these tasks. -**Note**   -**This feature is supported starting in App-V 5.0 SP3.** - -  +**Note**
+This feature is supported starting in App-V 5.0 SP3. Use one of the following methods to allow only administrators to enable or disable connection groups. @@ -40,32 +38,22 @@ Use one of the following methods to allow only administrators to enable or disab

Computer Configuration > Administrative Templates > System > App-V > Publishing

-

PowerShell cmdlet

-

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

+

Windows PowerShell cmdlet

+

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

Parameter values:

-

Example:: Set-AppvClientConfiguration –RequirePublishAsAdmin1

+

Example: Set-AppvClientConfiguration -RequirePublishAsAdmin 1

-  +## Have a suggestion for App-V? -**Have 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/en-US/home?forum=mdopappv). +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). ## Related topics - [Managing Connection Groups](appv-managing-connection-groups.md) - -  - -  - - - - - diff --git a/windows/manage/appv-application-publishing-and-client-interaction.md b/windows/manage/appv-application-publishing-and-client-interaction.md index ffbb6bd6bb..be46e08fd4 100644 --- a/windows/manage/appv-application-publishing-and-client-interaction.md +++ b/windows/manage/appv-application-publishing-and-client-interaction.md @@ -384,7 +384,7 @@ App-V Packages are staged upon addition to the computer with the App-V Client. T ### Mounting packages -Packages can be explicitly loaded using the PowerShell `Mount-AppVClientPackage` or by using the **App-V Client UI** to download a package. This operation completely loads the entire package into the package store. +Packages can be explicitly loaded using the Windows PowerShell `Mount-AppVClientPackage` or by using the **App-V Client UI** to download a package. This operation completely loads the entire package into the package store. ### Streaming packages @@ -442,7 +442,7 @@ These settings affect the behavior of streaming App-V package assets to the clie ### Background streaming -The PowerShell cmdlet `Get-AppvClientConfiguration` can be used to determine the current mode for background streaming with the AutoLoad setting and modified with the cmdlet Set-AppvClientConfiguration or from the registry (HKLM\\SOFTWARE\\Microsoft\\AppV\\ClientStreaming key). Background streaming is a default setting where the Autoload setting is set to download previously used packages. The behavior based on default setting (value=1) downloads App-V data blocks in the background after the application has been launched. This setting can be disabled all together (value=0) or enabled for all packages (value=2), whether they have been launched. +The Windows PowerShell cmdlet `Get-AppvClientConfiguration` can be used to determine the current mode for background streaming with the AutoLoad setting and modified with the cmdlet Set-AppvClientConfiguration or from the registry (HKLM\\SOFTWARE\\Microsoft\\AppV\\ClientStreaming key). Background streaming is a default setting where the Autoload setting is set to download previously used packages. The behavior based on default setting (value=1) downloads App-V data blocks in the background after the application has been launched. This setting can be disabled all together (value=0) or enabled for all packages (value=2), whether they have been launched. ### Optimized streaming @@ -458,7 +458,7 @@ App-V Packages require updating throughout the lifecycle of the application. App ### Package removal -The behavior of the App-V Client when packages are removed depends on the method used for removal. Using an App-V full infrastructure to unpublish the application, the user catalog files (machine catalog for globally published applications) are removed, but retains the package store location and COW locations. When the PowerShell cmdlet `Remove-AppVClientPackge` is used to remove an App-V Package, the package store location is cleaned. Remember that unpublishing an App-V Package from the Management Server does not perform a Remove operation. Neither operation will remove the Package Store package files. +The behavior of the App-V Client when packages are removed depends on the method used for removal. Using an App-V full infrastructure to unpublish the application, the user catalog files (machine catalog for globally published applications) are removed, but retains the package store location and COW locations. When the Windows PowerShell cmdlet `Remove-AppVClientPackge` is used to remove an App-V Package, the package store location is cleaned. Remember that unpublishing an App-V Package from the Management Server does not perform a Remove operation. Neither operation will remove the Package Store package files. ## Roaming registry and data @@ -599,11 +599,11 @@ This process will re-create both the local and network locations for AppData and ## App-V client application lifecycle management -In an App-V Full Infrastructure, after applications are sequenced they are managed and published to users or computers via the App-V Management and Publishing servers. This section details the operations that occur during the common App-V application lifecycle operations (Add, publishing, launch, upgrade, and removal) and the file and registry locations that are changed and modified from the App-V Client perspective. The App-V Client operations are performed as a series of PowerShell commands initiated on the computer running the App-V Client. +In an App-V Full Infrastructure, after applications are sequenced they are managed and published to users or computers via the App-V Management and Publishing servers. This section details the operations that occur during the common App-V application lifecycle operations (Add, publishing, launch, upgrade, and removal) and the file and registry locations that are changed and modified from the App-V Client perspective. The App-V Client operations are performed as a series of Windows PowerShell commands initiated on the computer running the App-V Client. This document focuses on App-V Full Infrastructure solutions. For specific information on App-V Integration with Configuration Manager 2012, see [Integrating Virtual Application Management with App-V 5 and Configuration Manager 2012 SP1](https://www.microsoft.com/en-us/download/details.aspx?id=38177). -The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with PowerShell commands. See [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md) or use Windows PowerShell: +The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with Windows PowerShell commands. See [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md) or use Windows PowerShell: ``` syntax get-command *appv* @@ -611,7 +611,7 @@ get-command *appv* ### Publishing refresh -The publishing refresh process is comprised of several smaller operations that are performed on the App-V Client. Since App-V is an application virtualization technology and not a task scheduling technology, the Windows Task Scheduler is utilized to enable the process at user logon, machine startup, and at scheduled intervals. The configuration of the client during setup listed above is the preferred method when distributing the client to a large group of computers with the correct settings. These client settings can be configured with the following PowerShell cmdlets: +The publishing refresh process is comprised of several smaller operations that are performed on the App-V Client. Since App-V is an application virtualization technology and not a task scheduling technology, the Windows Task Scheduler is utilized to enable the process at user logon, machine startup, and at scheduled intervals. The configuration of the client during setup listed above is the preferred method when distributing the client to a large group of computers with the correct settings. These client settings can be configured with the following Windows PowerShell cmdlets: - **Add-AppVPublishingServer:** Configures the client with an App-V Publishing Server that provides App-V packages. @@ -629,7 +629,7 @@ The focus of the following sections is to detail the operations that occur durin ### Adding an App-V package -Adding an App-V package to the client is the first step of the publishing refresh process. The end result is the same as the `Add-AppVClientPackage` cmdlet in PowerShell, except during the publishing refresh add process, the configured publishing server is contacted and passes a high-level list of applications back to the client to pull more detailed information and not a single package add operation. The process continues by configuring the client for package or connection group additions or updates, then accesses the appv file. Next, the contents of the appv file are expanded and placed on the local operating system in the appropriate locations. The following is a detailed workflow of the process, assuming the package is configured for Fault Streaming. +Adding an App-V package to the client is the first step of the publishing refresh process. The end result is the same as the `Add-AppVClientPackage` cmdlet in Windows PowerShell, except during the publishing refresh add process, the configured publishing server is contacted and passes a high-level list of applications back to the client to pull more detailed information and not a single package add operation. The process continues by configuring the client for package or connection group additions or updates, then accesses the appv file. Next, the contents of the appv file are expanded and placed on the local operating system in the appropriate locations. The following is a detailed workflow of the process, assuming the package is configured for Fault Streaming. **How to add an App-V package** diff --git a/windows/manage/appv-apply-the-deployment-configuration-file-with-powershell.md b/windows/manage/appv-apply-the-deployment-configuration-file-with-powershell.md index 013e318c2a..7497f65796 100644 --- a/windows/manage/appv-apply-the-deployment-configuration-file-with-powershell.md +++ b/windows/manage/appv-apply-the-deployment-configuration-file-with-powershell.md @@ -1,6 +1,6 @@ --- -title: How to Apply the Deployment Configuration File by Using PowerShell (Windows 10) -description: How to Apply the Deployment Configuration File by Using PowerShell +title: How to Apply the Deployment Configuration File by Using Windows PowerShell (Windows 10) +description: How to Apply the Deployment Configuration File by Using Windows PowerShell author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,7 +9,7 @@ ms.prod: w10 --- -# How to Apply the Deployment Configuration File by Using PowerShell +# How to Apply the Deployment Configuration File by Using Windows PowerShell Applies to: Windows 10, version 1607 @@ -19,31 +19,22 @@ The dynamic deployment configuration file is applied when a package is added or **c:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml** -**To Apply the Deployment Configuration File Using PowerShell** +**To Apply the Deployment Configuration File Using Windows PowerShell** -- To specify a new default set of configurations for all users who will run the package on a specific computer, using a PowerShell console type the following: +- To specify a new default set of configurations for all users who will run the package on a specific computer, in a Windows PowerShell console, type the following: - **Add-AppVClientPackage –Path c:\\Packages\\Contoso\\MyApp.appv -DynamicDeploymentConfiguration c:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml** + `Add-AppVClientPackage -Path c:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration c:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml` - **Note**   + **Note**
This command captures the resulting object into $pkg. If the package is already present on the computer, the **Set-AppVclientPackage** cmdlet can be used to apply the deployment configuration document: - **Set-AppVClientPackage –Name Myapp –Path c:\\Packages\\Contoso\\MyApp.appv -DynamicDeploymentConfiguration c:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml** + `Set-AppVClientPackage -Name Myapp -Path c:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration c:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml`   +## Have a suggestion for App-V? - **Have 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/en-US/home?forum=mdopappv). +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). ## Related topics - [Operations for App-V](appv-operations.md) - -  - -  - - - - - diff --git a/windows/manage/appv-apply-the-user-configuration-file-with-powershell.md b/windows/manage/appv-apply-the-user-configuration-file-with-powershell.md index 33e0832c8a..bedbf573df 100644 --- a/windows/manage/appv-apply-the-user-configuration-file-with-powershell.md +++ b/windows/manage/appv-apply-the-user-configuration-file-with-powershell.md @@ -1,6 +1,6 @@ --- -title: How to Apply the User Configuration File by Using PowerShell (Windows 10) -description: How to Apply the User Configuration File by Using PowerShell +title: How to Apply the User Configuration File by Using Windows PowerShell (Windows 10) +description: How to Apply the User Configuration File by Using Windows PowerShell author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,7 +9,7 @@ ms.prod: w10 --- -# How to Apply the User Configuration File by Using PowerShell +# How to Apply the User Configuration File by Using Windows PowerShell Applies to: Windows 10, version 1607 @@ -21,26 +21,19 @@ Use the following procedure to specify a user-specific configuration file. The f **To apply a user Configuration file** -1. To add the package to the computer using the PowerShell console type the following command: +1. To add the package to the computer using the Windows PowerShell console, type the following command: - **Add-AppVClientPackage c:\\Packages\\Contoso\\MyApp.appv**. + `Add-AppVClientPackage c:\Packages\Contoso\MyApp.appv` 2. Use the following command to publish the package to the user and specify the updated the dynamic user configuration file: - **Publish-AppVClientPackage $pkg –DynamicUserConfigurationPath c:\\Packages\\Contoso\\config.xml** + `Publish-AppVClientPackage $pkg -DynamicUserConfigurationPath c:\Packages\Contoso\config.xml` - **Have 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/en-US/home?forum=mdopappv). + +## 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). ## Related topics - [Operations for App-V](appv-operations.md) - -  - -  - - - - - diff --git a/windows/manage/appv-configure-connection-groups-to-ignore-the-package-version.md b/windows/manage/appv-configure-connection-groups-to-ignore-the-package-version.md index 7db96a1e62..b3de986775 100644 --- a/windows/manage/appv-configure-connection-groups-to-ignore-the-package-version.md +++ b/windows/manage/appv-configure-connection-groups-to-ignore-the-package-version.md @@ -13,93 +13,50 @@ ms.prod: w10 Applies to: Windows 10, version 1607 -Microsoft Application Virtualization (App-V) lets you configure a connection group to use any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create. +Application Virtualization (App-V) lets you configure a connection group to use any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create. -To upgrade a package in some earlier versions of App-V, you had to perform several steps, including disabling the connection group and modifying the connection group’s XML definition file. +You can configure a connection group to accept any version of a package, which enables you to upgrade the package without having to disable the connection group: - ---- - - - - - - - - - - - - -
Task description with App-VHow to perform the task with App-V

You can configure a connection group to accept any version of a package, which enables you to upgrade the package without having to disable the connection group.

-

How the feature works:

-
    -

  • If the connection group has access to multiple versions of a package, the latest version is used.

    • -

  • If the connection group contains an optional package that has an incorrect version, the package is ignored and won’t block the connection group’s virtual environment from being created.

    • -

  • If the connection group contains a non-optional package that has an incorrect version, the connection group’s virtual environment cannot be created.

    • -
 ---- - - - - - - - - - - - - - - - - -
MethodSteps

App-V Server – Management Console

    -

  1. In the Management Console, select CONNECTION GROUPS.

    2. -

  2. Select the correct connection group from the Connection Groups library.

    3. -

  3. Click EDIT in the CONNECTED PACKAGES pane.

    4. -

  4. Select Use Any Version check box next to the package name, and click Apply.

    5. -
-

For more about adding or upgrading packages, see [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md).

App-V Client on a Stand-alone computer

    -

  1. Create the connection group XML document.

    2. -

  2. For the package to be upgraded, set the Package tag attribute VersionID to an asterisk (*).

    3. -

  3. Use the following cmdlet to add the connection group, and include the path to the connection group XML document:

    -

    Add-AppvClientConnectionGroup

    4. -

  4. When you upgrade a package, use the following cmdlets to remove the old package, add the upgraded package, and publish the upgraded package:

    -
      -

    • RemoveAppvClientPackage

      • -

    • Add-AppvClientPackage

      • -

    • Publish-AppvClientPackage

      • -
    5. -
-

For more information, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md).

-
-

 

+- If the connection group has access to multiple versions of a package, the latest version is used. -  +- If the connection group contains an optional package that has an incorrect version, the package is ignored and won’t block the connection group’s virtual environment from being created. + +- If the connection group contains a non-optional package that has an incorrect version, the connection group’s virtual environment cannot be created. + +## To make a connection group ignore the package version by using the App-V Server Management Console + +1. In the Management Console, select **CONNECTION GROUPS**. + +2. Select the correct connection group from the Connection Groups library. + +3. Click **EDIT** in the CONNECTED PACKAGES pane. + +4. Select **Use Any Version** check box next to the package name, and click **Apply**. + +For more about adding or upgrading packages, see [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md). + +## To make a connection group ignore the package version from the App-V client on a stand-alone computer + +1. Create the connection group XML document. + +2. For the package to be upgraded, set the **Package** tag attribute **VersionID** to an asterisk (**\***). + +3. Use the following cmdlet to add the connection group, and include the path to the connection group XML document: + + `Add-AppvClientConnectionGroup` + +4. When you upgrade a package, use the following cmdlets to remove the old package, add the upgraded package, and publish the upgraded package: + + - RemoveAppvClientPackage + - Add-AppvClientPackage + - Publish-AppvClientPackage + +For more information, see [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). ## 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). ## Related topics - [Managing Connection Groups](appv-managing-connection-groups.md) - -  - -  - - - - - diff --git a/windows/manage/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md b/windows/manage/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md index 640b9078ae..0c1489d897 100644 --- a/windows/manage/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md +++ b/windows/manage/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md @@ -17,7 +17,7 @@ Deploying packages and connection groups using the App-V publishing server is he Use the following steps to configure the App-V client to receive updates from the publishing server. -**Note**   +**Note**
For the following procedures the management server was installed on a computer named **MyMgmtSrv**, and the publishing server was installed on a computer named **MyPubSrv**.   @@ -28,56 +28,37 @@ For the following procedures the management server was installed on a computer n 2. To open the management console click the following link, open a browser and type the following: http://MyMgmtSrv/AppvManagement/Console.html in a web browser, and import, publish, and entitle all the packages and connection groups which will be necessary for a particular set of users. -3. On the computer running the App-V client, open an elevated PowerShell command prompt, run the following command: +3. On the computer running the App-V client, open an elevated Windows PowerShell command prompt, and run the following command: - **Add-AppvPublishingServer  -Name  ABC  -URL  http:// MyPubSrv/AppvPublishing** + `Add-AppvPublishingServer -Name ABC -URL http://MyPubSrv/AppvPublishing` This command will configure the specified publishing server. You should see output similar to the following: - + + ``` Id                        : 1 - SetByGroupPolicy          : False - Name                      : ABC - URL                       : http:// MyPubSrv/AppvPublishing - GlobalRefreshEnabled      : False - GlobalRefreshOnLogon      : False - GlobalRefreshInterval     : 0 - GlobalRefreshIntervalUnit : Day - UserRefreshEnabled        : True - UserRefreshOnLogon        : True - UserRefreshInterval       : 0 - UserRefreshIntervalUnit   : Day + ``` - The returned Id – in this case 1 +4. On the computer running the App-V client, open a Windows PowerShell command prompt, and type the following command: -4. On the computer running the App-V client, open a PowerShell command prompt, and type the following command: - - **Sync-AppvPublishingServer  -ServerId  1** + `Sync-AppvPublishingServer -ServerId 1` The command will query the publishing server for the packages and connection groups that need to be added or removed for this particular client based on the entitlements for the packages and connection groups as configured on the management server. - **Have 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/en-US/home?forum=mdopappv). +## 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). ## Related topics - [Operations for App-V](appv-operations.md) - -  - -  - - - - - diff --git a/windows/manage/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md b/windows/manage/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md index 6d3897a4a3..ebcdf075bc 100644 --- a/windows/manage/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md +++ b/windows/manage/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md @@ -15,11 +15,11 @@ Applies to: Windows 10, version 1607 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) +- [How to use Windows PowerShell cmdlets to create user-entitled connection groups](#how-to-use-powershell-cmdlets-to-create-user-entitled-connection-groups) -- [How to use the App-V Server to create the user-entitled connection groups](#bkmk-appvserver-userentitled-cg) +- [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) -**What to know before you start:** +## What to know before you start: @@ -47,27 +47,27 @@ 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 Windows PowerShell cmdlets to create user-entitled connection groups 1. Add and publish packages by using the following commands: - - **Add-AppvClientPackage Pacakage1\_AppV\_file\_Path** - - **Add-AppvClientPackage Pacakage2\_AppV\_file\_Path** - - **Publish-AppvClientPackage -PackageId Package1\_ID -VersionId Package1\_Version ID -Global** - - **Publish-AppvClientPackage -PackageId Package2\_ID -VersionId Package2\_ID** + + ``` + Add-AppvClientPackage + Add-AppvClientPackage + Publish-AppvClientPackage -PackageId  -VersionId -Global + Publish-AppvClientPackage -PackageId -VersionId  + ``` 2. Create the connection group XML file. For more information, see [About the Connection Group File](appv-connection-group-file.md). 3. Add and publish the connection group by using the following commands: + + ``` + Add-AppvClientConnectionGroup + Enable-AppvClientConnectionGroup -GroupId  -VersionId + ``` - **Add-AppvClientConnectionGroup Connection\_Group\_XML\_file\_Path** - - **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 Management Console. @@ -75,7 +75,9 @@ You can create user-entitled connection groups that contain both user-published 3. Follow the instructions in [How to Create a Connection Group](appv-create-a-connection-group.md) to create the connection group, and add the user-published and globally published packages. - **Have 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/en-US/home?forum=mdopappv). +## 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). ## Related topics diff --git a/windows/manage/appv-create-a-connection-group.md b/windows/manage/appv-create-a-connection-group.md index 5818fa7c3a..1f4d4b0fc2 100644 --- a/windows/manage/appv-create-a-connection-group.md +++ b/windows/manage/appv-create-a-connection-group.md @@ -13,7 +13,7 @@ ms.prod: w10 Applies to: Windows 10, version 1607 -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](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md). +Use these steps to create a connection group by using the App-V Management Console. To use Windows PowerShell to create connection groups, 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). 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. @@ -33,27 +33,17 @@ When you place packages in a connection group, their package root paths are merg To reprioritize the applications in your connection group, use the arrows in the **PACKAGES IN** pane. - **Important**   + **Important**
By default, the Active Directory Domain Services access configurations that are associated with a specific application are not added to the connection group. To transfer the Active Directory access configuration, select **ADD PACKAGE ACCESS TO GROUP ACCESS**, which is located in the **PACKAGES IN** pane. -   - 6. After adding all the applications and configuring Active Directory access, click **Apply**. - **Have 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/en-US/home?forum=mdopappv). +## 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). ## Related topics - [Operations for App-V](appv-operations.md) [Managing Connection Groups](appv-managing-connection-groups.md) - -  - -  - - - - - diff --git a/windows/manage/appv-create-a-package-accelerator-with-powershell.md b/windows/manage/appv-create-a-package-accelerator-with-powershell.md index 2a8265cf30..d77e0714cf 100644 --- a/windows/manage/appv-create-a-package-accelerator-with-powershell.md +++ b/windows/manage/appv-create-a-package-accelerator-with-powershell.md @@ -1,6 +1,6 @@ --- -title: How to Create a Package Accelerator by Using PowerShell (Windows 10) -description: How to Create a Package Accelerator by Using PowerShell +title: How to Create a Package Accelerator by Using Windows PowerShell (Windows 10) +description: How to Create a Package Accelerator by Using Windows PowerShell author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,7 +9,7 @@ ms.prod: w10 --- -# How to Create a Package Accelerator by Using PowerShell +# How to Create a Package Accelerator by Using Windows PowerShell Applies to: Windows 10, version 1607 @@ -19,7 +19,7 @@ App-V package accelerators automatically sequence large, complex applications. A 1. Install the App-V sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md). -2. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. Use the **New-AppvPackageAccelerator** cmdlet. +2. To open a Windows PowerShell console, click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. Use the **New-AppvPackageAccelerator** cmdlet. 3. To create a package accelerator, make sure that you have the .appv package to create an accelerator from, the installation media or installation files, and optionally a read me file for consumers of the accelerator to use. The following parameters are required to use the package accelerator cmdlet: @@ -35,22 +35,14 @@ App-V package accelerators automatically sequence large, complex applications. A **New-AppvPackageAccelerator -InputPackagePath <path to the .appv file> -Installer <path to the installer executable> -Path <directory of the output path>** - Additional optional parameters that can be used with the **New-AppvPackageAccelerator** cmdlet are displayed in the following list: + An additional optional parameter that can be used with the **New-AppvPackageAccelerator** cmdlet is as follows: - **AcceleratorDescriptionFile** - specifies the path to user created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be packaged with the package created using the package accelerator. - **Have 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/en-US/home?forum=mdopappv). +## 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). ## Related topics - [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md) - -  - -  - - - - - diff --git a/windows/manage/appv-create-a-package-accelerator.md b/windows/manage/appv-create-a-package-accelerator.md index 6a632ed8cf..e7b679b245 100644 --- a/windows/manage/appv-create-a-package-accelerator.md +++ b/windows/manage/appv-create-a-package-accelerator.md @@ -15,63 +15,42 @@ Applies to: Windows 10, version 1607 App-V package accelerators automatically generate new virtual application packages. -**Note**   -You can use PowerShell to create a package accelerator. For more information see [How to Create a Package Accelerator by Using PowerShell](appv-create-a-package-accelerator-with-powershell.md). - -  +>**Note**  You can use Windows PowerShell to create a package accelerator. For more information see [How to Create a Package Accelerator by Using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md). Use the following procedure to create a package accelerator. -**Important**   -Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied. +>**Important** +> - Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied. +> - Before you begin the following procedure, perform the following: + - Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer. + - Copy all required installation files associated with the virtual application package to the computer running the sequencer. +> - The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a Package Accelerator using App-V Sequencer. -  +## To create a package accelerator -**Important**   -Before you begin the following procedure, you should perform the following: - -- Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer. - -- Copy all required installation files associated with the virtual application package to the computer running the sequencer. - -  - -**To create a package accelerator** - -1. **Important**   - The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a Package Accelerator using App-V Sequencer. - -   - - To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. +1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. 2. To start the App-V **Create Package Accelerator** wizard, in the App-V sequencer console, click **Tools** / **Create Accelerator**. 3. On the **Select Package** page, to specify an existing virtual application package to use to create the Package Accelerator, click **Browse**, and locate the existing virtual application package (.appv file). - **Tip**   + **Tip**
Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer. - -   - + Click **Next**. 4. On the **Installation Files** page, to specify the folder that contains the installation files that you used to create the original virtual application package, click **Browse**, and then select the directory that contains the installation files. - **Tip**   + **Tip**
Copy the folder that contains the required installation files to the computer running the Sequencer. -   - 5. If the application is already installed on the computer running the sequencer, to specify the installation file, select **Files installed on local system**. To use this option, the application must already be installed in the default installation location. 6. On the **Gathering Information** page, review the files that were not found in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, and then click **Next**. If the files are required, click **Previous** and copy the required files to the directory specified on the **Installation Files** page. - **Note**   + **Note**
You must either remove the unrequired files, or click **Previous** and locate the required files to advance to the next page of this wizard. -   - 7. On the **Select Files** page, carefully review the files that were detected, and clear any file that should be removed from the package accelerator. Select only files that are required for the application to run successfully, and then click **Next**. 8. On the **Verify Applications** page, confirm that all installation files that are required to build the package are displayed. When the Package Accelerator is used to create a new package, all installation files displayed in the **Applications** pane are required to create the package. @@ -84,25 +63,15 @@ Before you begin the following procedure, you should perform the following: 11. On the **Completion** page, to close the **Create Package Accelerator** wizard, click **Close**. - **Important**   + **Important**
To help ensure that the package accelerator is as secure as possible, and so that the publisher can be verified when the package accelerator is applied, you should always digitally sign the package accelerator. -   +## Have a suggestion for App-V? - **Have 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/en-US/home?forum=mdopappv). +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). ## Related topics - [Operations for App-V](appv-operations.md) [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-deploy-appv-packages-with-electronic-software-distribution-solutions.md b/windows/manage/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md index 9882506d3b..eddadfbe2e 100644 --- a/windows/manage/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md +++ b/windows/manage/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md @@ -22,7 +22,7 @@ Use one of the following methods to publish packages to App-V client computers w | - | - | | Functionality provided by a third-party ESD | Use the functionality in a third-party ESD.| | Stand-alone Windows Installer | Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V package file information used to configure a package and copies the required package files to the client. | -| Windows PowerShell | Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).| +| Windows PowerShell | Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).|   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 6fcdb04f02..c68bfae353 100644 --- a/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md @@ -88,7 +88,7 @@ You can deploy Office 2010 packages by using any of the following App-V deployme - App-V server -- Stand-alone through PowerShell commands +- Stand-alone through Windows PowerShell commands ## Office App-V package management and customization 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 9fb4652fa5..62d2a67615 100644 --- a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md @@ -239,68 +239,10 @@ The XML file that is included in the Office Deployment Tool specifies the produc ``` - **Note**   + **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: - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
InputDescriptionExample

Add element

Specifies the products and languages to include in the package.

N/A

OfficeClientEdition (attribute of Add element)

Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value.

OfficeClientEdition="32"

-

OfficeClientEdition="64"

Product element

Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.

Product ID ="O365ProPlusRetail "

-

Product ID ="VisioProRetail"

-

Product ID ="ProjectProRetail"

-

Product ID ="ProPlusVolume"

-

Product ID ="VisioProVolume"

-

Product ID = "ProjectProVolume"

Language element

Specifies the language supported in the applications

Language ID="en-us"

Version (attribute of Add element)

Optional. Specifies a build to use for the package

-

Defaults to latest advertised build (as defined in v32.CAB at the Office source).

15.1.2.3

SourcePath (attribute of Add element)

Specifies the location in which the applications will be saved to.

Sourcepath = "\\Server\Office2013”

- -   + 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. For more information, see [Customizable attributes and elements of the XML file](#customizable-attributes-and-elements-of-the-XML-file), later in this topic. 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. @@ -319,25 +261,72 @@ The XML file that is included in the Office Deployment Tool specifies the produc -

\\server\Office2013

+

\\\\server\Office2013

is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.

-

Setup.exe

+

setup.exe

is the Office Deployment Tool.

-

/download

+

/download

downloads the Office 2013 applications that you specify in the customConfig.xml file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing.

-

\\server\Office2013\Customconfig.xml

+

\\\\server\Office2013\Customconfig.xml

passes the XML configuration file required to complete the download process, in this example, customconfig.xml. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \\Server\Office2013.

-   +#### Customizable attributes and elements of the XML file + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Input and descriptionExample

Add element:
Specifies the products and languages to include in the package.

N/A

OfficeClientEdition (attribute of Add element):
Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value.

OfficeClientEdition="32"

+

OfficeClientEdition="64"

Product element:
Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.

Product ID ="O365ProPlusRetail "

+

Product ID ="VisioProRetail"

+

Product ID ="ProjectProRetail"

+

Product ID ="ProPlusVolume"

+

Product ID ="VisioProVolume"

+

Product ID = "ProjectProVolume"

Language element:
Specifies the language supported in the applications.

Language ID="en-us"

Version (attribute of Add element):
Optional. Specifies a build to use for the package. Defaults to latest advertised build (as defined in v32.CAB at the Office source).

15.1.2.3

SourcePath (attribute of Add element):
Specifies the location in which the applications will be saved to.

Sourcepath = "\\Server\Office2013”

+ +   ### Convert the Office applications into an App-V package @@ -389,122 +378,58 @@ After you download the Office 2013 applications through the Office Deployment To -  - -**How to convert the Office applications into an App-V package** +#### How to convert the Office applications into an App-V package 1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterWhat to change the value to

SourcePath

Point to the Office applications downloaded earlier.

ProductID

Specify the type of licensing, as shown in the following examples:

-
    -

  • Subscription Licensing

    - 
    <Configuration>
-       <Add SourcePath= "\\server\Office 2013" OfficeClientEdition="32" >
-        <Product ID="O365ProPlusRetail">
-          <Language ID="en-us" />
-        </Product>
-        <Product ID="VisioProRetail">
-          <Language ID="en-us" />
-        </Product>
-      </Add>  
-    </Configuration>
    -

    In this example, the following changes were made to create a package with Subscription licensing:

    - - - - - - - - - - - - - - - - - - - -

    SourcePath

    is the path, which was changed to point to the Office applications that were downloaded earlier.

    Product ID

    for Office was changed to O365ProPlusRetail.

    Product ID

    for Visio was changed to VisioProRetail.

    -

     

    -

    • -

  • Volume Licensing

    - 
    <Configuration>
-       <Add SourcePath= "\\Server\Office2013" OfficeClientEdition="32" >
-        <Product ID="ProPlusVolume">
-          <Language ID="en-us" />
-        </Product>
-        <Product ID="VisioProVolume">
-          <Language ID="en-us" />
-        </Product>
-      </Add>  
-    </Configuration>
    -

    In this example, the following changes were made to create a package with Volume licensing:

    - - - - - - - - - - - - - - - - - - - -

    SourcePath

    is the path, which was changed to point to the Office applications that were downloaded earlier.

    Product ID

    for Office was changed to ProPlusVolume.

    Product ID

    for Visio was changed to VisioProVolume.

    -

     

    -

    • -

ExcludeApp (optional)

Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.

PACKAGEGUID (optional)

By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.

-

An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users.

-
- Note   -

Even if you use unique package IDs, you can still deploy only one App-V package to a single device.

-
-
-   -
- -   + - **SourcePath**: Point to the Office applications downloaded earlier. + + - **ProductID**: Specify the type of licensing, as shown in the following examples: + - Subscription Licensing: + ``` + + + + + + + + + + + ``` + In this example, the following changes were made to create a package with Subscription licensing: + + **SourcePath** is the path, which was changed to point to the Office applications that were downloaded earlier.
+ **Product ID** for Office was changed to `O365ProPlusRetail`.
+ **Product ID** for Visio was changed to `VisioProRetail`. + + - Volume Licensing + ``` + + + + + + + + + + + ``` + In this example, the following changes were made to create a package with Volume licensing: + + **SourcePath** is the path, which was changed to point to the Office applications that were downloaded earlier.
+ **Product ID** for Office was changed to `ProPlusVolume`.
+ **Product ID** for Visio was changed to `VisioProVolume`. + + - **ExcludeApp** (optional): Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath. + + - **PACKAGEGUID** (optional): By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server. + + An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users. + + **Note**  Even if you use unique package IDs, you can still deploy only one App-V package to a single device. 2. Use the /packager command to convert the Office applications to an Office 2013 App-V package. @@ -523,40 +448,33 @@ After you download the Office 2013 applications through the Office Deployment To -

\\server\Office2013

+

\\\\server\Office2013

is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.

-

Setup.exe

+

setup.exe

is the Office Deployment Tool.

-

/packager

+

/packager

creates the Office 2013 App-V package with Volume Licensing as specified in the customConfig.xml file.

-

\\server\Office2013\Customconfig.xml

+

\\\\server\Office2013\Customconfig.xml

passes the configuration XML file (in this case customConfig) that has been prepared for the packaging stage.

-

\\server\share\Office 2013AppV

+

\\\\server\share\Office2013AppV

specifies the location of the newly created Office App-V package.

-   - After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved: - - - **App-V Packages** – contains an Office 2013 App-V package and two deployment configuration files. - - - **WorkingDir** - - **Note**   - To troubleshoot any issues, see the log files in the %temp% directory (default). - -   + **App-V Packages** – contains an Office 2013 App-V package and two deployment configuration files.
+ **WorkingDir** + + **Note**  To troubleshoot any issues, see the log files in the %temp% directory (default). 3. Verify that the Office 2013 App-V package works correctly: @@ -577,7 +495,7 @@ Deploy the App-V package for Office 2013 by using the same methods you use for a - App-V Server -- Stand-alone through PowerShell commands +- Stand-alone through Windows PowerShell commands ### Publishing prerequisites and requirements @@ -594,9 +512,9 @@ Deploy the App-V package for Office 2013 by using the same methods you use for a -

Enable PowerShell scripting on the App-V clients

+

Enable Windows PowerShell scripting on the App-V clients

To publish Office 2013 packages, you must run a script.

-

Package scripts are disabled by default on App-V clients. To enable scripting, run the following PowerShell command:

+

Package scripts are disabled by default on App-V clients. To enable scripting, run the following Windows PowerShell command:

Set-AppvClientConfiguration –EnablePackageScripts 1
@@ -640,20 +558,17 @@ Use the steps in this section to enable Office plug-ins with your Office package **To enable plug-ins for Office App-V packages** -1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet. +1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a Windows PowerShell cmdlet. 2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2013 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2013 plug-ins. 3. Create an App-V package that includes the desired plug-ins. -4. Add a Connection Group through App-V server, System Center Configuration Manager, or a PowerShell cmdlet. +4. Add a Connection Group through App-V server, System Center Configuration Manager, or a Windows PowerShell cmdlet. 5. Add the Office 2013 App-V package and the plug-ins package you sequenced to the Connection Group you created. - **Important**   - The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2013 App-V package first, and then add the plug-in App-V package. - -   + **Important**  The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2013 App-V package first, and then add the plug-in App-V package. 6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2013 App-V package. @@ -794,7 +709,11 @@ An Office 2013 App-V Package with your chosen licensing will be successfully dep ### Deploying Visio 2013 and Project 2013 with Office -The following table describes the requirements and options for deploying Visio 2013 and Project 2013 with Office. +This section describes the requirements and options for deploying Visio 2013 and Project 2013 with Office. + +- **To package and publish Visio 2013 and Project 2013 with Office**: 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. + +- **To deploy Visio 2013 and Project 2013 to specific users**: Use one of the following methods: @@ -803,28 +722,8 @@ The following table describes the requirements and options for deploying Visio 2 - - - - - - - - - - - - - - -
TaskDetails

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.

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

Use one of the following methods:

- ---- - - - - + + @@ -842,17 +741,11 @@ 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 [AppLocker](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/applocker-overview) to prevent specific users from using Visio and Project.

    4. +

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

If you want to......then use this methodGoalMethod
-

 

- -  ## Additional resources diff --git a/windows/manage/appv-deploying-the-appv-server.md b/windows/manage/appv-deploying-the-appv-server.md index 9ecaf08055..fd8e163de0 100644 --- a/windows/manage/appv-deploying-the-appv-server.md +++ b/windows/manage/appv-deploying-the-appv-server.md @@ -12,7 +12,7 @@ ms.prod: w10 Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 ->**Note** If you plan to use the App-V server components in your deployment, note that they reference App-V 5.x. This is because the App-V server components have not changed in App-V for Windows 10. +>**Note**
If you plan to use the App-V server components in your deployment, note that they reference App-V 5.x. This is because the App-V server components have not changed in App-V for Windows 10. You can install the Application Virtualization (App-V) server components using different deployment configurations, which are described in this topic. Before you install the server features, review the server section of [App-V Security Considerations](appv-security-considerations.md). @@ -102,7 +102,7 @@ The reporting information will be maintained until it is successfully sent to th If you want to retrieve report information, you must use Microsoft SQL Server Reporting Services (SSRS) which is available with Microsoft SQL. SSRS is not installed when you install the App-V reporting server and it must be deployed separately to generate the associated reports. -For more information, see [About App-V Reporting](appv-reporting.md) and [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md). +For more information, see [About App-V Reporting](appv-reporting.md) and [How to Enable Reporting on the App-V Client by Using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md). ## Other resources for the App-V server - [Deploying App-V](appv-deploying-appv.md) diff --git a/windows/manage/appv-dynamic-configuration.md b/windows/manage/appv-dynamic-configuration.md index 26cb71c3b7..7d462c4dfc 100644 --- a/windows/manage/appv-dynamic-configuration.md +++ b/windows/manage/appv-dynamic-configuration.md @@ -737,8 +737,8 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros ## Related topics -[How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md) +[How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md) -[How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md) +[How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md) [Operations for App-V](appv-operations.md) diff --git a/windows/manage/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md b/windows/manage/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md index 4712ea5236..b013a64db3 100644 --- a/windows/manage/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md +++ b/windows/manage/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md @@ -23,15 +23,8 @@ Starting in App-V 5.0 SP3, you can configure the App-V client so that only admin 2. Enable the **Require publish as administrator** Group Policy setting. - To alternatively use PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs). - - **Have 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/en-US/home?forum=mdopappv). - -  - -  - - - + To instead use Windows PowerShell to set this item, see [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). +## 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-enable-reporting-on-the-appv-client-with-powershell.md b/windows/manage/appv-enable-reporting-on-the-appv-client-with-powershell.md index 719260f7f2..30afc5cc80 100644 --- a/windows/manage/appv-enable-reporting-on-the-appv-client-with-powershell.md +++ b/windows/manage/appv-enable-reporting-on-the-appv-client-with-powershell.md @@ -1,6 +1,6 @@ --- -title: How to Enable Reporting on the App-V Client by Using PowerShell (Windows 10) -description: How to Enable Reporting on the App-V Client by Using PowerShell +title: How to Enable Reporting on the App-V Client by Using Windows PowerShell (Windows 10) +description: How to Enable Reporting on the App-V Client by Using Windows PowerShell author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,7 +9,7 @@ ms.prod: w10 --- -# How to Enable Reporting on the App-V Client by Using PowerShell +# How to Enable Reporting on the App-V Client by Using Windows PowerShell Applies to: Windows 10, version 1607 @@ -19,7 +19,7 @@ Use the following procedure to configure the App-V for reporting. 1. Enable the App-V client. For more information, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). -2. After you have enabled the App-V client, use the **Set-AppvClientConfiguration** PowerShell to configure appropriate Reporting Configuration settings: +2. After you have enabled the App-V client, use the **Set-AppvClientConfiguration** cmdlet to configure appropriate Reporting Configuration settings: @@ -75,7 +75,7 @@ Use the following procedure to configure the App-V for reporting. 3. After the appropriate settings have been configured, the computer running the App-V client will automatically collect data and will send the data back to the reporting server. - Additionally, administrators can manually send the data back in an on-demand manner using the **Send-AppvClientReport** PowerShell cmdlet. + Additionally, administrators can manually send the data back in an on-demand manner using the **Send-AppvClientReport** cmdlet. ## Have a suggestion for App-V? diff --git a/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md b/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md index 787a0bfe6c..b231f0d973 100644 --- a/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md +++ b/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md @@ -1,6 +1,6 @@ --- -title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell (Windows 10) -description: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell +title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell (Windows 10) +description: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,11 +9,11 @@ ms.prod: w10 --- -# How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell +# How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 -Use the following PowerShell procedure to convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by Microsoft SQL Server when running SQL scripts. +Use the following Windows PowerShell procedure to convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by Microsoft SQL Server when running SQL scripts. Before attempting this procedure, you should read and understand the information and examples displayed in the following list: @@ -33,336 +33,97 @@ Before attempting this procedure, you should read and understand the information **To convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs)** -1. Copy the following script into a text editor and save it as a PowerShell script file, for example **ConvertToSIDs.ps1**. +1. Copy the following script into a text editor and save it as a Windows PowerShell script file, for example **ConvertToSIDs.ps1**. -2. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. +2. To open a Windows PowerShell console, click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. ``` syntax <# - ``` - - ``` syntax .SYNOPSIS - ``` - - ``` syntax - This PowerShell script will take an array of account names and try to convert each of them to the corresponding SID in standard and hexadecimal formats. - ``` - - ``` syntax + This Windows PowerShell script will take an array of account names and try to convert each of them to the corresponding SID in standard and hexadecimal formats. .DESCRIPTION - ``` - - ``` syntax - This is a PowerShell script that converts any number of Active Directory (AD) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by SQL server when running SQL scripts. - ``` - - ``` syntax + This is a Windows PowerShell script that converts any number of Active Directory (AD) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by SQL server when running SQL scripts. .INPUTS - ``` - - ``` syntax The account(s) to convert to SID format. This can be a single account name or an array of account names. Please see examples below. - ``` - - ``` syntax .OUTPUTS - ``` - - ``` syntax A list of account names with the corresponding SID in standard and hexadecimal formats - ``` - - ``` syntax .EXAMPLE - ``` - - ``` syntax .\ConvertToSID.ps1 DOMAIN\user_account1 DOMAIN\machine_account1$ DOMAIN\user_account2 | Format-List - ``` - - ``` syntax .EXAMPLE - ``` - - ``` syntax $accountsArray = @("DOMAIN\user_account1", "DOMAIN\machine_account1$", "DOMAIN_user_account2") - ``` - - ``` syntax .\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\SIDs.txt -Width 200 - ``` - - ``` syntax -#> - ``` - - ``` syntax - ``` + #> []() []() - - ``` syntax function ConvertSIDToHexFormat - ``` - { - -    param(\[System.Security.Principal.SecurityIdentifier\]$sidToConvert) - - ``` syntax - ``` - - ``` syntax +    param([System.Security.Principal.SecurityIdentifier]$sidToConvert)    $sb = New-Object System.Text.StringBuilder - ``` - - ``` syntax     [int] $binLength = $sidToConvert.BinaryLength - ``` - - ``` syntax     [Byte[]] $byteArray = New-Object Byte[] $binLength - ``` - - ``` syntax    $sidToConvert.GetBinaryForm($byteArray, 0) - ``` - - ``` syntax    foreach($byte in $byteArray) - ``` - - ``` syntax    { - ``` - - ``` syntax    $sb.Append($byte.ToString("X2")) |Out-Null - ``` - - ``` syntax    } - ``` - - ``` syntax    return $sb.ToString() - ``` - - ``` syntax } - ``` - - ``` syntax [string[]]$myArgs = $args - ``` - - ``` syntax if(($myArgs.Length -lt 1) -or ($myArgs[0].CompareTo("/?") -eq 0)) - ``` - { - - ``` syntax [string]::Format("{0}====== Description ======{0}{0}" + - ``` - - ``` syntax "  Converts any number of user or machine account names to string and hexadecimal SIDs.{0}" + - ``` - - ``` syntax                "  Pass the account(s) as space separated command line parameters. (For example 'ConvertToSID.exe DOMAIN\\Account1 DOMAIN\\Account2 ...'){0}" + - ``` - - ``` syntax                "  The output is written to the console in the format 'Account name    SID as string   SID as hexadecimal'{0}" + - ``` - - ``` syntax -                "  And can be written out to a file using standard PowerShell redirection{0}" + - ``` - - ``` syntax +                "  And can be written out to a file using standard Windows PowerShell redirection{0}" +                "  Please specify user accounts in the format 'DOMAIN\username'{0}" + - ``` - - ``` syntax                "  Please specify machine accounts in the format 'DOMAIN\machinename$'{0}" + - ``` - - ``` syntax                "  For more help content, please run 'Get-Help ConvertToSID.ps1'{0}" + - ``` - - ``` syntax                "{0}====== Arguments ======{0}" + - ``` - - ``` syntax                "{0}  /?    Show this help message", [Environment]::NewLine) - ``` - - ``` syntax { - ``` - - ``` syntax else - ``` - - ``` syntax {      #If an array was passed in, try to split it - ``` - - ``` syntax     if($myArgs.Length -eq 1) - ``` - - ``` syntax     { - ``` - - ``` syntax         $myArgs = $myArgs.Split(' ') - ``` - - ``` syntax     } - ``` - - ``` syntax     #Parse the arguments for account names - ``` - - ``` syntax     foreach($accountName in $myArgs) - ``` - - ``` syntax     {    - ``` - - ``` syntax         [string[]] $splitString = $accountName.Split('\')  # We're looking for the format "DOMAIN\Account" so anything that does not match, we reject - ``` - - ``` syntax         if($splitString.Length -ne 2) - ``` - - ``` syntax         { - ``` - - ``` syntax             $message = [string]::Format("{0} is not a valid account name. Expected format 'Domain\username' for user accounts or 'DOMAIN\machinename$' for machine accounts.", $accountName) - ``` - - ``` syntax             Write-Error -Message $message - ``` - - ``` syntax             continue - ``` - - ``` syntax         } - ``` - - ``` syntax -         - ``` - - ``` syntax         #Convert any account names to SIDs - ``` - - ``` syntax         try - ``` - - ``` syntax         { - ``` - - ``` syntax             [System.Security.Principal.NTAccount] $account = New-Object System.Security.Principal.NTAccount($splitString[0], $splitString[1]) - ``` - - ``` syntax             [System.Security.Principal.SecurityIdentifier] $SID = [System.Security.Principal.SecurityIdentifier]($account.Translate([System.Security.Principal.SecurityIdentifier])) - ``` - - ``` syntax         } - ``` - - ``` syntax         catch [System.Security.Principal.IdentityNotMappedException] - ``` - - ``` syntax         { - ``` - - ``` syntax             $message = [string]::Format("Failed to translate account object '{0}' to a SID. Please verify that this is a valid user or machine account.", $account.ToString()) - ``` - - ``` syntax             Write-Error -Message $message - ``` - - ``` syntax             continue - ``` - - ``` syntax         } - ``` - - ``` syntax         #Convert regular SID to binary format used by SQL - ``` - - ``` syntax         $hexSIDString = ConvertSIDToHexFormat $SID - ``` - - ``` syntax -                 $SIDs = New-Object PSObject - ``` - - ``` syntax         $SIDs | Add-Member NoteProperty Account $accountName - ``` - - ``` syntax         $SIDs | Add-Member NoteProperty SID $SID.ToString() - ``` - - ``` syntax         $SIDs | Add-Member NoteProperty Hexadecimal $hexSIDString - ``` - - ``` syntax         Write-Output $SIDs - ``` - - ``` syntax     } - ``` - - ``` syntax } ``` @@ -374,18 +135,10 @@ Before attempting this procedure, you should read and understand the information **.\\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\\SIDs.txt -Width 200”** - **Have 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/en-US/home?forum=mdopappv). +## 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). ## Related topics - [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md) - -  - -  - - - - - diff --git a/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md b/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md index c104d88d25..c8fb57e012 100644 --- a/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md +++ b/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md @@ -85,7 +85,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance 4. For each database, copy the scripts to a share and modify them following the instructions in the readme file. **Note**   - For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).   + For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).   5. Run the scripts on the computer running Microsoft SQL Server. @@ -95,14 +95,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros ## Related topics - [Deploying App-V](appv-deploying-appv.md) - -  - -  - - - - - diff --git a/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md b/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md index 324f9b5804..08141a0e4e 100644 --- a/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md +++ b/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md @@ -56,13 +56,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros [Deploying App-V](appv-deploying-appv.md) -[How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md) - -  - -  - - - - - +[How to Enable Reporting on the App-V Client by Using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.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 d96ba47b0a..166f2987a4 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 @@ -1,6 +1,6 @@ --- -title: How to Load the PowerShell Cmdlets and Get Cmdlet Help (Windows 10) -description: How to Load the App-V PowerShell Cmdlets and Get Cmdlet Help +title: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help (Windows 10) +description: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,24 +9,24 @@ ms.prod: w10 --- -# How to Load the PowerShell Cmdlets and Get Cmdlet Help +# How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help Applies to: Windows 10, version 1607 What this topic covers: -- [Requirements for using PowerShell cmdlets](#bkmk-reqs-using-posh) +- [Requirements for using Windows PowerShell cmdlets](#bkmk-reqs-using-posh) -- [Loading the PowerShell cmdlets](#bkmk-load-cmdlets) +- [Loading the Windows PowerShell cmdlets](#bkmk-load-cmdlets) -- [Getting help for the PowerShell cmdlets](#bkmk-get-cmdlet-help) +- [Getting help for the Windows PowerShell cmdlets](#bkmk-get-cmdlet-help) -- [Displaying the help for a PowerShell cmdlet](#bkmk-display-help-cmdlet) +- [Displaying the help for a Windows PowerShell cmdlet](#bkmk-display-help-cmdlet) -## Requirements for using PowerShell cmdlets +## Requirements for using Windows PowerShell cmdlets -Review the following requirements for using the App-V PowerShell cmdlets: +Review the following requirements for using the Windows PowerShell cmdlets:
@@ -72,42 +72,23 @@ Review the following requirements for using the App-V PowerShell cmdlets:

  • Unpublish-AppvClientPackage

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

    -
    ---- - - - - - - - - - - - - - - - - -
    MethodMore resources

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

      -

    • [How to Manage Connection Groups on a Stand-alone Computer by Using 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 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.

    [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)

    -

     

    + +   -## Loading the PowerShell cmdlets +## Loading the Windows PowerShell cmdlets -To load the PowerShell cmdlet modules: +To load the Windows PowerShell cmdlet modules: 1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). @@ -142,30 +123,12 @@ To load the PowerShell cmdlet modules:   -## Getting help for the PowerShell cmdlets - +## Getting help for the Windows PowerShell cmdlets Starting in App-V 5.0 SP3, cmdlet help is available in two formats: - ---- - - - - - - - - - - - - - - - - -
    FormatDescription

    As a downloadable module

    To download the latest help after downloading the cmdlet module:

    -
      -

    1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).

      2. -

    2. Type one of the following commands to load the cmdlets for the module you want:

      3. -
    +- **As a downloadable module**: To download the latest help after downloading the cmdlet module, open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE), and type one of the following commands: + @@ -192,33 +155,21 @@ Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
    -

     

    On TechNet as web pages

    See the App-V node under [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](http://technet.microsoft.com/library/dn520245.aspx).

    - -  - -## Displaying the help for a PowerShell cmdlet -To display help for a specific PowerShell cmdlet: + +- **On TechNet as web pages**: See the App-V node under [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](http://technet.microsoft.com/library/dn520245.aspx). + +## Displaying the help for a Windows PowerShell cmdlet + + +To display help for a specific Windows PowerShell cmdlet: 1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). 2. Type **Get-Help** <*cmdlet*>, for example, **Get-Help Publish-AppvClientPackage**. -**Have 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/en-US/home?forum=mdopappv). - -  - -  - - - +## 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-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/manage/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md index 81e50c0cee..8be4ce5307 100644 --- a/windows/manage/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md +++ b/windows/manage/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md @@ -1,6 +1,6 @@ --- -title: How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell (Windows 10) -description: How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell +title: How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell (Windows 10) +description: How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,12 +9,12 @@ ms.prod: w10 --- -# How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell +# How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell Applies to: Windows 10, version 1607 -The following sections explain how to perform various management tasks on a stand-alone client computer by using PowerShell: +The following sections explain how to perform various management tasks on a stand-alone client computer by using Windows PowerShell: - [To return a list of packages](#bkmk-return-pkgs-standalone-posh) @@ -169,7 +169,7 @@ Use the following information to remove a package from the computer. **Example**: Remove-AppvClientPackage “ContosoApplication” **Note**   -App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [To add and publish a package](#bkmk-add-pub-pkg-standalone-posh). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](http://go.microsoft.com/fwlink/?LinkId=324466). +App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [To add and publish a package](#bkmk-add-pub-pkg-standalone-posh). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](https://blogs.technet.microsoft.com/appv/2012/12/03/app-v-5-0-client-powershell-deep-dive/).   @@ -213,7 +213,7 @@ To use the App-V Management console to set this configuration, see [How to Publi ## Understanding pending packages (UserPending and GlobalPending) -**Starting in App-V 5.0 SP2**: If you run a PowerShell cmdlet that affects a package that is currently in use, the task that you are trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows: +**Starting in App-V 5.0 SP2**: If you run a Windows PowerShell cmdlet that affects a package that is currently in use, the task that you are trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows: @@ -273,24 +273,15 @@ The pending task will run later, according to the following rules:
    -  - For more information about pending tasks, see [Upgrading an in-use App-V package](appv-application-publishing-and-client-interaction.md#upgrading-an-in-use-app-v-package). -**Have 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/en-US/home?forum=mdopappv). +## 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). ## Related topics - [Operations for App-V](appv-operations.md) [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md) -  - -  - - - - - diff --git a/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md b/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md index 140842081a..bc49311d2e 100644 --- a/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md +++ b/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md @@ -1,6 +1,6 @@ --- -title: How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell (Windows 10) -description: How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell +title: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell (Windows 10) +description: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,7 +9,7 @@ ms.prod: w10 --- -# 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 Windows PowerShell Applies to: Windows 10, version 1607 @@ -82,8 +82,8 @@ This topic explains the following procedures:

    Enable-AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345

    -

    Disable -AppVClientConnectionGroup

    -

    Disable -AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345

    +

    Disable-AppVClientConnectionGroup

    +

    Disable-AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345

    @@ -116,19 +116,19 @@ This topic explains the following procedures:

    Set-AppvClientConfiguration

    -

    –RequirePublishAsAdmin

    +

    -RequirePublishAsAdmin

    -

    Set-AppvClientConfiguration –RequirePublishAsAdmin1

    +

    Set-AppvClientConfiguration -RequirePublishAsAdmin 1

    -   +## Have a suggestion for App-V? - **Have 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/en-US/home?forum=mdopappv). +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). ## Related topics @@ -136,12 +136,3 @@ This topic explains the following procedures: [Operations for App-V](appv-operations.md) [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md) - -  - -  - - - - - diff --git a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md index 0c954a7bf8..786c35ec08 100644 --- a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md +++ b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md @@ -161,7 +161,7 @@ ConvertFrom-AppvLegacyPackage –SourcePath \\OldPkgStore\ContosoApp\ ## Converting packages created using a prior version of App-V -Use the package converter utility to upgrade virtual application packages created using versions of App-V prior to App-V 5.0. The package converter uses PowerShell to convert packages and can help automate the process if you have many packages that require conversion. App-V packages created with App-V 5.x don't need to be converted. +Use the package converter utility to upgrade virtual application packages created using versions of App-V prior to App-V 5.0. The package converter uses Windows PowerShell to convert packages and can help automate the process if you have many packages that require conversion. App-V packages created with App-V 5.x don't need to be converted. **Important**   diff --git a/windows/manage/appv-modify-client-configuration-with-powershell.md b/windows/manage/appv-modify-client-configuration-with-powershell.md index 3843e5468f..6547a2bdb7 100644 --- a/windows/manage/appv-modify-client-configuration-with-powershell.md +++ b/windows/manage/appv-modify-client-configuration-with-powershell.md @@ -15,7 +15,7 @@ Applies to: Windows 10, version 1607 Use the following procedure to configure the App-V client configuration. -1. To configure the client settings using Windows PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing Windows PowerShell, and a list of cmdlets see, [How to Load the PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md). +1. To configure the client settings using Windows PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing Windows PowerShell, and a list of cmdlets see, [How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md). 2. To modify the client configuration, open a Windows PowerShell Command prompt and run **Set-AppvClientConfiguration** with any required parameters. For example: diff --git a/windows/manage/appv-performance-guidance.md b/windows/manage/appv-performance-guidance.md index 9273be8a26..4529d5c06f 100644 --- a/windows/manage/appv-performance-guidance.md +++ b/windows/manage/appv-performance-guidance.md @@ -536,9 +536,9 @@ Removing FB1 does not require the original application installer. After completi 3. Move to **Create Package**. -**PowerShell** - Update an Existing Virtual Application Package. +**Windows PowerShell** - Update an Existing Virtual Application Package. -1. Open an elevated PowerShell session. +1. Open an elevated Windows PowerShell session. 2. Import-module **appvsequencer**. @@ -619,7 +619,7 @@ When publishing a virtual application package, the App-V Client will detect if a   -### Disabling a Dynamic Configuration using Powershell +### Disabling a Dynamic Configuration by using Windows Powershell - For already published packages, you can use `Set-AppVClientPackage –Name Myapp –Path c:\Packages\Apps\MyApp.appv` without @@ -631,9 +631,9 @@ When publishing a virtual application package, the App-V Client will detect if a For documentation on How to Apply a Dynamic Configuration, see: -- [How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md) +- [How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md) -- [How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md) +- [How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md) @@ -653,7 +653,7 @@ For documentation on How to Apply a Dynamic Configuration, see: - @@ -677,18 +677,15 @@ For documentation on How to Apply a Dynamic Configuration, see: - Open AppxManifest.xml and locate the following: - <appv:Extension Category="AppV.Fonts"> + ``` + + + + + ``` - <appv:Fonts> + **Note**  If there are fonts marked as **DelayLoad**, those will not impact first launch. - <appv:Font Path="\[{Fonts}\]\\private\\CalibriL.ttf" DelayLoad="true"></appv:Font> - - **Note**   - If there are fonts marked as **DelayLoad**, those will not impact first launch. - -   - - </appv:Fonts> ### Excluding virtual fonts from the package @@ -698,11 +695,11 @@ Use the dynamic configuration file that best suits the user scope – deployment Fonts ---> - -<Fonts Enabled="false" /> - -<!-- +``` +--> + +

    Account for Synchronous Script Execution during Package Lifecycle.

    If script collateral is embedded in the package, Add (Powershell) may be significantly slower.

    +

    If script collateral is embedded in the package, Add cmdlets may be significantly slower.

    Running of scripts during virtual application launch (StartVirtualEnvironment, StartProcess) and/or Add+Publish will impact the perceived performance during one or more of these lifecycle operations.

    Use of Asynchronous (Non-Blocking) Scripts will ensure that the lifecycle operations complete efficiently.

    This step requires working knowledge of all virtual application packages with embedded script collateral, which have associated dynamic configurations files and which reference and run scripts synchronously.