deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-14 22:37:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #117 from Justinha/8442312-app-v

Browse Source 
8442312 app v
This commit is contained in:
Justin Hall 2016-08-12 13:59:31 -07:00 committed by GitHub
commit 926e54a30b
2 changed files with 9 additions and 342 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

341
windows/manage/appv-about-appv.md
View File

@ -20,7 +20,7 @@ Application Virtualization (App-V) for Windows 10, version 1607, includes these
## App-V is now a feature in Windows 10
With Windows 10, version 1607 and later releases, Application Virtualization (App-V) is included with [Windows 10 for Enterprise and Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home) and is no longer part of the Microsoft Desktop Optimization Pack.
With Windows 10, version 1607 and later releases, Application Virtualization (App-V) is included with [Windows 10 for Enterprise and Windows 10 for Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home) and is no longer part of the Microsoft Desktop Optimization Pack.
For information about earlier versions of App-V, see [MDOP Information Experience](https://technet.microsoft.com/itpro/mdop/index).
@ -28,7 +28,7 @@ The changes in App-V for Windows 10, version 1607 impact already existing implem
- The App-V client is installed on user devices automatically with Windows 10, version 1607, and no longer has to be deployed separately. Performing an in-place upgrade to Windows 10, version 1607, on user devices automatically installs the App-V client.
- The App-V application sequencer is available from the Windows 10 Assessment and Deployment Kit (ADK). In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work.
- The App-V application sequencer is available from the [Windows 10 Assessment and Deployment Kit (ADK)](http://go.microsoft.com/fwlink/p/?LinkId=526740). In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work.
>**Note**<br>If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released.
@ -38,346 +38,15 @@ For more information about how to configure an existing App-V installation after
You can upgrade your existing App-V installation to Windows 10, version 1607 from App-V versions 5.0 SP2 and higher only. If you are using a previous version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade to Windows 10, version 1607.
 
## Support for using System Center Configuration Manager 2016 with App-V
## Support for System Center
App-V supports System Center 2016 and 2012 R2 Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx) for information about integrating your App-V environment with Configuration Manager.
App-V supports System Center 2016 and System Center 2012 R2 Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx) for information about integrating your App-V environment with Configuration Manager.
<!-- Need to verify with Chintan that the rest of the topic can be deleted -->
### <a href="" id="bkmk-steps-upgrd-infrastruc"></a>Steps to upgrade the App-V infrastructure
Complete the following steps to upgrade each component of the App-V infrastructure to App-V for Windows. The following order is only a suggestion; you can upgrade components in any order.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Step</th>
<th align="left">For more information</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Step 1: Upgrade the App-V server components.</p>
<div class="alert">
<strong>Note</strong>  
<p>If you are not using the App-V server, skip this step and go to the next step.</p>
</div>
<div>
 
</div></td>
<td align="left"><p>Follow these steps:</p>
<ol>
<li><p>Do one of the following, depending on the method you are using to upgrade the management database and/or reporting database:</p>
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Database upgrade method</th>
<th align="left">Step</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Windows Installer</p></td>
<td align="left"><p>Skip this step and go to step 2, “If you are upgrading the App-V server...”</p></td>
</tr>
<tr class="even">
<td align="left"><p>SQL scripts</p></td>
<td align="left"><p>Follow the steps in [How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md).</p></td>
</tr>
</tbody>
</table>
<li><p>If you are upgrading to App-V for Windows server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 server](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/check-reg-key-svr).</p></li>
<li><p>Follow the steps in [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)</p></li>
<p> </p></li>
</ol></td>
</tr>
<tr class="even">
<td align="left"><p>Step 2: Install the new App-V for Windows sequencer.</p></td>
<td align="left"><p>See [How to Install the Sequencer](appv-install-the-sequencer.md).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Step 3: Enable the in-box App-V client.</p></td>
<td align="left"><p>See [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).</p></td>
</tr>
</tbody>
</table>
 
### 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 for Windows, version 1607. The package converter uses PowerShell to convert packages and can help automate the process if you have many packages that require conversion.
>**Note**  
App-V for Windows packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and so there is no need to convert App-V 5.0 packages to App-V for Windows packages.
 
## <a href="" id="bkmk-whatsnew"></a>What’s New in App-V
These sections are for users who are already familiar with App-V and want to know what has changed in App-V for Windows. If you are not already familiar with App-V, you should start by reading [Planning for App-V](appv-planning-for-appv.md).
### <a href="" id="bkmk-mgmtconsole"></a>App-V Management Console Changes
This section compares the App-V for Windows Management Console’s current and previous functionality.
### Silverlight is no longer required
The Management Console UI no longer requires Silverlight. The Management Console is built on HTML5 and Javascript.
### Notifications and messages are displayed individually in a dialog box
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">New in App-V for Windows</th>
<th align="left">Prior to App-V for Windows</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p><strong>Number of messages indicator:</strong></p>
<p>On the title bar of the App-V Management Console, a number is now displayed next to a flag icon to indicate the number of messages that are waiting to be read.</p></td>
<td align="left"><p>You could see only one message or error at a time, and you were unable to determine how many messages there were.</p></td>
</tr>
<tr class="even">
<td align="left"><p><strong>Message appearance:</strong></p>
<ul>
<li><p>Messages that require user input appear in a separate dialog box that displays on top of the current page that you were viewing, and require a response before you can dismiss them.</p></li>
<li><p>Messages and errors appear in a list, with one beneath the other.</p></li>
</ul></td>
<td align="left"><p>You could see only one message or error at a time.</p></td>
</tr>
<tr class="odd">
<td align="left"><p><strong>Dismissing messages:</strong></p>
<p>Use the <strong>Dismiss All</strong> link to dismiss all messages and errors at one time, or dismiss them one at a time.</p></td>
<td align="left"><p>You could dismiss messages and errors only one at a time.</p></td>
</tr>
</tbody>
</table>
 
### Console pages are now separate URLs
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">New in App-V for Windows</th>
<th align="left">Prior to App-V for Windows</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Each page in the console has a different URL, which enables you to bookmark specific pages for quick access in the future.</p>
<p>The number that appears in some URLs indicates the specific package. These numbers are unique.</p></td>
<td align="left"><p>All console pages are accessed through the same URL.</p></td>
</tr>
</tbody>
</table>
 
### New, separate CONNECTION GROUPS page and menu option
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">New in App-V for Windows</th>
<th align="left">Prior to App-V for Windows</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>The CONNECTION GROUPS page is now part of the main menu, at the same level as the PACKAGES page.</p></td>
<td align="left"><p>To open the CONNECTION GROUPS page, you navigate through the PACKAGES page.</p></td>
</tr>
</tbody>
</table>
 
### Menu options for packages have changed
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">New in App-V for Windows</th>
<th align="left">Prior to App-V Windows</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>The following options are now buttons that appear at the bottom of the PACKAGES page:</p>
<ul>
<li><p>Add or Upgrade</p></li>
<li><p>Publish</p></li>
<li><p>Unpublish</p></li>
<li><p>Delete</p></li>
</ul>
<p>The following options will still appear when you right-click a package to open the drop-down context menu:</p>
<ul>
<li><p>Publish</p></li>
<li><p>Unpublish</p></li>
<li><p>Edit AD Access</p></li>
<li><p>Edit Deployment Config</p></li>
<li><p>Transfer deployment configuration from…</p></li>
<li><p>Transfer access and configuration from…</p></li>
<li><p>Delete</p></li>
</ul>
<p>When you click <strong>Delete</strong> to remove a package, a dialog box opens and asks you to confirm that you want to delete the package.</p></td>
<td align="left"><p>The <strong>Add or Upgrade</strong> option was a button at the top right of the PACKAGES page.</p>
<p>The <strong>Publish</strong>, <strong>Unpublish</strong>, and <strong>Delete</strong> options were available only if you right-clicked a package name in the packages list.</p></td>
</tr>
<tr class="even">
<td align="left"><p>The following package operations are now buttons on the package details page for each package:</p>
<ul>
<li><p>Transfer (drop-down menu with the following options):</p>
<ul>
<li><p>Transfer deployment configuration from…</p></li>
<li><p>Transfer access and configuration from…</p></li>
</ul></li>
<li><p>Edit (connection groups and AD Access)</p></li>
<li><p>Unpublish</p></li>
<li><p>Delete</p></li>
<li><p>Edit Default Configuration</p></li>
</ul></td>
<td align="left"><p>These package options were available only if you right-clicked a package name in the packages list.</p></td>
</tr>
</tbody>
</table>
 
### Icons in left pane have new colors and text
The colors of the icons in the left pane have been changed, and text added, to make the icons consistent with other Microsoft products.
### Overview page has been removed
In the left pane of the Management Console, the OVERVIEW menu option and its associated OVERVIEW page have been removed.
### <a href="" id="bkmk-seqimprove"></a>Sequencer Improvements
The following improvements have been made to the package editor in the App-V Sequencer.
#### Import and export the manifest file
You can import and export the AppxManifest.xml file. To export the manifest file, select the **Advanced** tab and in the Manifest File box, click **Export...**. You can make changes to the manifest file, such as removing shell extensions or editing file type associations.
After you make your changes, click **Import...** and select the file you edited. After you successfully import it back in, the manifest file is immediately updated within the package editor.
>**Caution**  
When you import the file, your changes are validated against the XML schema. If the file is not valid, you will receive an error. Be aware that it is possible to import a file that is validated against the XML schema, but that might still fail to run for other reasons.
 
#### Addition of Windows 10 to operating systems list
In the Deployment tab, Windows 10 32-bit and Windows 10-64 bit have been added to the list of operating systems for which you can sequence a package. If you select **Any Operating System**, Windows 10 is automatically included among the operating systems that the sequenced package will support.
#### Current path displays at bottom of virtual registry editor
In the Virtual Registry tab, the path now displays at the bottom of the virtual registry editor, which enables you to determine the currently selected key. Previously, you had to scroll through the registry tree to find the currently selected key.
#### <a href="" id="combined--find-and-replace--dialog-box-and-shortcut-keys-added-in-virtual-registry-editor"></a>Combined “find and replace” dialog box and shortcut keys added in virtual registry editor
In the virtual registry editor, shortcut keys have been added for the Find option (Ctrl+F), and a dialog box that combines the “find” and “replace” tasks has been added to enable you to find and replace values and data. To access this combined dialog box, select a key and do one of the following:
- Press **Ctrl+H**
- Right-click a key and select **Replace**.
- Select **View** &gt; **Virtual Registry** &gt; **Replace**.
Previously, the “Replace” dialog box did not exist, and you had to make changes manually.
#### Rename registry keys and package files successfully
You can rename virtual registry keys and files without experiencing Sequencer issues. Previously, the Sequencer stopped working if you tried to rename a key.
#### Import and export virtual registry keys
You can import and export virtual registry keys. To import a key, right-click the node under which to import the key, navigate to the key you want to import, and then click **Import**. To export a key, right-click the key and select **Export**.
#### Import a directory into the virtual file system
You can import a directory into the VFS. To import a directory, click the **Package Files** tab, and then click **View** &gt; **Virtual File System** &gt; **Import Directory**. If you try to import a directory that contains files that are already in the VFS, the import fails, and an explanatory message is displayed. Prior to App-V, you could not import directories.
#### Import or export a VFS file without having to delete and then add it back to the package
You can import files to or export files from the VFS without having to delete the file and then add it back to the package. For example, you might use this feature to export a change log to a local drive, edit the file using an external editor, and then re-import the file into the VFS.
To export a file, select the **Package Files** tab, right-click the file in the VFS, click **Export**, and choose an export location from which you can make your edits.
To import a file, select the **Package Files** tab and right-click the file that you had exported. Browse to the file that you edited, and then click **Import**. The imported file will overwrite the existing file.
After you import a file, you must save the package by clicking **File** &gt; **Save**.
#### Menu for adding a package file has moved
The menu option for adding a package file has been moved. To find the Add option, select the **Package Files** tab, then click **View** &gt; **Virtual File System** &gt; **Add File**. Previously, you right-clicked a folder under the VFS node, and chose **Add File**.
#### Virtual registry node expands MACHINE and USER hives by default
When you open the virtual registry, the MACHINE and USER hives are shown below the top-level REGISTRY node. Previously, you had to expand the REGISTRY node to show the hives beneath.
#### Enable or disable Browser Helper Objects
You can enable or disable Browser Helper Objects by selecting a new check box, Enable Browser Helper Objects, on the Advanced tab of the Sequencer user interface. If Browser Helper Objects:
- Exist in the package and are enabled, the check box is selected by default.
- Exist in the package and are disabled, the check box is clear by default.
- Exist in the package, with one or more enabled and one or more disabled, the check box is set to indeterminate by default.
- Do not exist in the package, the check box is disabled.
### <a href="" id="bkmk-pkgconvimprove"></a>Improvements to Package Converter
You can now use the package converter to convert App-V 4.6 packages that contain scripts, and registry information and scripts from source .osd files are now included in package converter output.
For more information including examples, see [Migrating to App-V for Windows from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md).
#### <a href="" id="bkmk-supmultscripts"></a>Support for multiple scripts on a single event trigger
App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you are converting from App-V 4.6 to App-V 5.0 or later. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is installed as part of the App-V client installation.
For more information, including a list of event triggers and the context under which scripts can be run, see the Scripts section in [About App-V Dynamic Configuration](appv-dynamic-configuration.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).
Add or vote on suggestions at [Microsoft Application Virtualization](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

10
windows/manage/appv-migrating-to-appv-from-a-previous-version.md
View File

@ -13,10 +13,7 @@ ms.prod: w10
Applies to: Windows 10, version 1607
When you upgrade your existing App-V environment to App-V for Windows 10, version 1607, you'll experience more flexibility, integratation, and ease of management. You can upgrade from any App-V 5.x release, however, you cannot upgrade directly from App-V 4.x to App-V for Windows 10; you must upgrade to App-V 5.x first. For more information about upgrading to App-V for Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md)
>**Note**  
THe package format for App-V packages created with App-V 5.x has not changed in App-V for Windows 10. As a result, you don't need to convert packages.
To migrate from App-V 4.x to App-V for Windows 10, you must upgrade to App-V 5.x first.
## <a href="" id="bkmk-pkgconvimprove"></a>Improvements to the App-V Package Converter
@ -164,7 +161,8 @@ 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.
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.
**Important**  
After you convert an existing package you should test the package prior to deploying the package to ensure the conversion process was successful.
@ -279,7 +277,7 @@ There is no direct method to upgrade to a full App-V infrastructure. Use the inf
</tr>
<tr class="even">
<td align="left"><p>Migrate existing packages.</p></td>
<td align="left"><p>See the <strong>Converting packages created using a prior version of App-V</strong> section of this article.</p></td>
<td align="left"><p>See Converting packages created using a prior version of App-V earlier in this topic.</p></td>
</tr>
</tbody>
</table>