deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-07 01:57:21 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Started next wave of revisions

Browse Source
This commit is contained in:
Heidi Lohr 2018-06-25 14:53:13 -07:00
parent 139bc297d5
commit f593106232
2 changed files with 19 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
windows/application-management/app-v/appv-connection-group-file.md
View File

@ -44,7 +44,7 @@ The following table describes the parameters in the XML file that define the con
### Parameters that define the packages in the connection group
In the <Packages> section of the connection group XML file, you list the member packages in the connection group by specifying each package’s unique package identifier and version identifier, as described in the following table. The first package in the list has the highest precedence.
In the **<Packages>** section of the connection group XML file, you list the member packages in the connection group by specifying each package’s unique package identifier and version identifier, as described in the following table. The first package in the list has the highest precedence.
|Field|Description|
|---|---|

31
windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md
View File

@ -1,6 +1,6 @@
---
title: How to Convert a Package Created in a Previous Version of App-V (Windows 10)
description: How to Convert a Package Created in a Previous Version of App-V
title: How to convert a package created in a previous version of App-V (Windows 10)
description: How to convert a package created in a previous version of App-V.
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
@ -8,36 +8,31 @@ ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
---
# How to Convert a Package Created in a Previous Version of App-V
**Applies to**
- Windows 10, version 1607
>Applies to: Windows 10, version 1607
You can use the package converter utility to upgrade virtual application packages that have been created with previous versions of App-V.
You can use the package converter utility to upgrade virtual application packages created by previous versions of App-V. This section will tell you how to convert existing virtual application packages for upgrade.
> [!NOTE]
> If you are running a computer with a 64-bit architecture, you must use the x86 version of Windows PowerShell.
>[!NOTE]
>If you are running a computer with a 64-bit architecture, you must use the x86 version of Windows PowerShell.
The package converter can only directly convert packages that were created by using the App-V 4.5 sequencer or later. Packages that were created using a version prior to App-V 4.5 must be upgraded to at least App-V 4.5 before conversion.
The package converter can only directly convert packages created by the App-V 4.5 sequencer or later. Packages created with an App-V version earlier than 4.5 must be upgraded to at least App-V 4.5 before conversion.
The following information provides direction for converting existing virtual application packages.
> [!IMPORTANT]
> You must configure the package converter to always save the package ingredients file to a secure location and directory. A secure location is accessible only by an administrator. Additionally, when you deploy the package, you should save the package to a location that is secure, or make sure that no other user is allowed to be logged in during the conversion process.
>[!IMPORTANT]
>In order to keep your files secure, you must configure the package converter to always save the package ingredients file to a secure location and directory that can only be accessed by an administrator. When you deploy the package, you should either save the package to a secure location or make sure that no other users can sign in during the conversion process.
## App-V 4.6 installation folder is redirected to virtual file system root
When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for Windows 10 package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive letter is Q:\\.)
When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for Windows 10 package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive is drive Q.)
**Technical Details:** The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the Filesystem element. When the App-V for Windows 10 client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root.
## Getting started
1. Install the App-V Sequencer on a computer in your environment. For information about how to install the Sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md).
1. Install the App-V Sequencer on a computer in your environment. For information about how to install the Sequencer, see [How to install the Sequencer](appv-install-the-sequencer.md).
2. The following cmdlets are available:
2. You can enter the following cmdlets to check or convert packages:
- **Test-AppvLegacyPackage** – This cmdlet is designed to check packages. It will return information about any failures with the package such as missing **.sft** files, an invalid source, **.osd** file errors, or invalid package version. This cmdlet will not parse the **.sft** file or do any in depth validation. For information about options and basic functionality for this cmdlet, using Windows PowerShell, type `Test-AppvLegacyPackage -?`.
@ -58,7 +53,7 @@ When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for
## Have a suggestion for App-V?
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
## Related topics