Publish-AppvClientPackage
For more information, see:
-The example XML file, Connection group XML file with optional packages, in this section: [How to Use Optional Packages in Connection Groups](appv-use-optional-packages-in-connection-groups.md#bkmk-apps-plugs-optional)
[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)
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).
+ diff --git a/windows/manage/appv-connection-group-file.md b/windows/manage/appv-connection-group-file.md index d84e5c6982..cf82d7392b 100644 --- a/windows/manage/appv-connection-group-file.md +++ b/windows/manage/appv-connection-group-file.md @@ -139,7 +139,7 @@ In the <Packages> section of the connection group XML file, you list the m“true” – package is optional in the connection group
“false” – package is required in the connection group
See [How to Use Optional Packages in Connection Groups](appv-use-optional-packages-in-connection-groups.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 3455bd85a2..fab3419e83 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 @@ -80,14 +80,3 @@ You can create user-entitled connection groups that contain both user-published [Managing Connection Groups](appv-managing-connection-groups.md) - -[How to Use Optional Packages in Connection Groups](appv-use-optional-packages-in-connection-groups.md) - - - - - - - - - diff --git a/windows/manage/appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md b/windows/manage/appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md deleted file mode 100644 index 6c49beef4e..0000000000 --- a/windows/manage/appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer (Windows 10) -description: How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer -author: MaggiePucciEvans -ms.pagetype: mdop, appcompat, virtualization -ms.mktglfcycl: deploy -ms.sitesec: library -ms.prod: w10 ---- - - -# How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer - - -Use the following information to install the Microsoft Application Virtualization (App-V) client (preferably, with the latest Service Packs and hotfixes) and the App-V 4.6 SP2 client or the App-V 4.6 S3 client on the same computer. For supported versions, requirements, and other planning information, see [Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md). - -**To deploy the App-V client and App-V 4.6.x client on the same computer** - -1. Install one of the following versions of the App-V client on the computer that is running App-V 4.6. - - - [Microsoft Application Virtualization 4.6 Service Pack 2](http://go.microsoft.com/fwlink/?LinkId=262687) - - - [Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187) - -2. Install the App-V client on the computer that is running the App-V 4.6 SP2 or 4.6 SP3 version of the client. For best results, we recommend that you install all available updates to the App-V client. - -3. Convert or re-sequence the packages gradually. - - - To convert the packages, use the App-V package converter and convert the required packages to the App-V (**.appv**) file format. - - - To re-sequence the packages, consider using the latest version of the Sequencer for best results. - - For more information about publishing packages, see [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md). - -4. Deploy packages to the client computers. - -5. Convert extension points, as needed. For more information, see the following resources: - - - [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md) - - - [How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md) - - - [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) - -6. Test that your App-V packages are successful, and then remove the 4.6 packages. To check the user state of your client computers, we recommend that you use [User Experience Virtualization](http://technet.microsoft.com/library/dn458947.aspx) or another user environment management tool. - - **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). - -## Related topics - - -[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md) - -[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md) - - - - - - - - - diff --git a/windows/manage/appv-deploy-the-appv-client.md b/windows/manage/appv-deploy-the-appv-client.md deleted file mode 100644 index b3c3662519..0000000000 --- a/windows/manage/appv-deploy-the-appv-client.md +++ /dev/null @@ -1,345 +0,0 @@ ---- -title: How to Deploy the App-V Client (Windows 10) -description: How to Deploy the App-V Client -author: MaggiePucciEvans -ms.pagetype: mdop, appcompat, virtualization -ms.mktglfcycl: deploy -ms.sitesec: library -ms.prod: w10 ---- - - -# How to Deploy the App-V Client - -Use the following procedure to install the Microsoft Application Virtualization (App-V) client and Remote Desktop Services client. You must install the version of the client that matches the operating system of the target computer. - -## What to do before you start - -1. Review and install the software prerequisites: - - Install the prerequisite software that corresponds to the version of App-V that you are installing: - - - [About App-V](appv-about-appv.md) - - - [App-V Prerequisites](appv-prerequisites.md) - -2. Review the client coexistence and unsupported scenarios, as applicable to your installation: - -Deploying coexisting App-V clients |
- [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md) |
-
Unsupported or limited installation scenarios |
- See the client section in [App-V Supported Configurations](appv-supported-configurations.md) |
-
Client registry information |
-
|
-
Client log files |
-
|
-
Client installation troubleshooting information |
-See the error log in the %temp% folder. To review the log files, click Start, type %temp%, and then look for the appv_ log. |
-
| Client type | -File to use | -
|---|---|
Standard version of the client |
- appv_client_setup.exe |
-
Remote Desktop Services version of the client |
- appv_client_setup_rds.exe |
-
/INSTALLDIR |
- Specifies the installation directory. Example usage: /INSTALLDIR=C:\Program Files\AppV Client |
-
/CEIPOPTIN |
- Enables participation in the Customer Experience Improvement Program. Example usage: /CEIPOPTIN=[0|1] |
-
/MUOPTIN |
- Enables Microsoft Update. Example usage: /MUOPTIN=[0|1] |
-
/PACKAGEINSTALLATIONROOT |
- Specifies the directory in which to install all new applications and updates. Example usage: /PACKAGEINSTALLATIONROOT='C:\App-V Packages' |
-
/PACKAGESOURCEROOT |
- Overrides the source location for downloading package content. Example usage: /PACKAGESOURCEROOT='http://packageStore' |
-
/AUTOLOAD |
- Specifies how new packages will be loaded by App-V on a specific computer. The following options are enabled: [1]; automatically load all packages [2]; or automatically load no packages [0].Example usage: /AUTOLOAD=[0|1|2] |
-
/SHAREDCONTENTSTOREMODE |
- Specifies that streamed package contents will be not be saved to the local hard disk. Example usage: /SHAREDCONTENTSTOREMODE=[0|1] |
-
/MIGRATIONMODE |
- Allows the App-V client to modify the shortcuts and FTAs that are associated with the packages that are created with a previous version. Example usage: /MIGRATIONMODE=[0|1] |
-
/ENABLEPACKAGESCRIPTS |
- Enables the scripts that are defined in the package manifest file or configuration files that should run. Example usage: /ENABLEPACKAGESCRIPTS=[0|1] |
-
/ROAMINGREGISTRYEXCLUSIONS |
- Specifies the registry paths that will not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=software\classes;software\clients |
-
/ROAMINGFILEEXCLUSIONS |
- Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /ROAMINGFILEEXCLUSIONS 'desktop;my pictures' |
-
/S[1-5]PUBLISHINGSERVERNAME |
- Displays the name of the publishing server. Example usage: /S2PUBLISHINGSERVERNAME=MyPublishingServer |
-
/S[1-5]PUBLISHINGSERVERURL |
- Displays the URL of the publishing server. Example usage: /S2PUBLISHINGSERVERURL=\\pubserver |
-
/S[1-5]GLOBALREFRESHENABLED - |
- Enables a global publishing refresh. Example usage: /S2GLOBALREFRESHENABLED=[0|1] |
-
/S[1-5]GLOBALREFRESHONLOGON |
- Initiates a global publishing refresh when a user logs on. Example usage: /S2LOGONREFRESH=[0|1] |
-
/S[1-5]GLOBALREFRESHINTERVAL - |
- Specifies the publishing refresh interval, where 0 indicates do not periodically refresh. Example usage: /S2PERIODICREFRESHINTERVAL=[0-744] |
-
/S[1-5]GLOBALREFRESHINTERVALUNIT |
- Specifies the interval unit (Hours[0], Days[1]). Example usage: /S2GLOBALREFRESHINTERVALUNIT=[0|1] |
-
/S[1-5]USERREFRESHENABLED |
- Enables user publishing refresh. Example usage: /S2USERREFRESHENABLED=[0|1] |
-
/S[1-5]USERREFRESHONLOGON |
- Initiates a user publishing refresh when a user logs on. Example usage: /S2LOGONREFRESH=[0|1] |
-
/S[1-5]USERREFRESHINTERVAL - |
- Specifies the publishing refresh interval, where 0 indicates do not periodically refresh. Example usage: /S2PERIODICREFRESHINTERVAL=[0-744] |
-
/S[1-5]USERREFRESHINTERVALUNIT |
- Specifies the interval unit (Hours[0], Days[1]). Example usage: /S2USERREFRESHINTERVALUNIT=[0|1] |
-
/Log |
- Specifies a location where the log information is saved. The default location is %Temp%. Example usage: /log C:\logs\log.log |
-
/q |
- Specifies an unattended installation. |
-
/REPAIR |
- Repairs a previous client installation. |
-
/NORESTART |
- Prevents the computer from rebooting after the client installation. -The parameter prevents the end-user computer from rebooting after each update is installed and lets you schedule the reboot at your convenience. For example, you can install App-V and then install Hotfix Package Y without rebooting after the Service Pack installation. After the installation, you must reboot before you start using App-V. |
-
/UNINSTALL |
- Uninstalls the client. |
-
/ACCEPTEULA |
- Accepts the license agreement. This is required for an unattended installation. Example usage: /ACCEPTEULA or /ACCEPTEULA=1. |
-
/LAYOUT |
- Specifies the associated layout action. It also extracts the Windows Installer (.msi) and script files to a folder without installing App-V. No value is expected. |
-
/LAYOUTDIR |
- Specifies the layout directory. Requires a string value. Example usage: /LAYOUTDIR=”C:\Application Virtualization Client”. |
-
/?, /h, /help |
- Requests help about the previous installation parameters. |
-
| Type of deployment | -Deploy this file | -
|---|---|
Computer is running a 32-bit Microsoft Windows operating system |
- appv_client_MSI_x86.msi |
-
Computer is running a 64-bit Microsoft Windows operating system |
- appv_client_MSI_x64.msi |
-
You are deploying the App-V Remote Desktop Services client |
- appv_client_rds_MSI_x64.msi |
-
| Type of deployment | -Deploy this file | -
|---|---|
Computer is running a 32-bit Microsoft Windows operating system |
- appv_client_LP_xxxx_ x86.msi |
-
Computer is running a 64-bit Microsoft Windows operating system |
- appv_client_LP_xxxx_ x64.msi |
-