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

Folded in some changes from Maggie's email

Browse Source
This commit is contained in:
JanKeller1 2016-08-08 17:59:36 -07:00
parent e6e02031d0
commit 038a5e9e71
4 changed files with 20 additions and 178 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md
View File

@ -12,7 +12,7 @@ ms.prod: w10
# How to Install the App-V Client for Shared Content Store Mode # How to Install the App-V Client for Shared Content Store Mode
Use the following procedure to install the Microsoft Application Virtualization (App-V) client so that it uses the App-V Shared Content Store (SCS) mode. You should ensure that all required prerequisites are installed on the computer you plan to install to. Use the following link to see [App-V Prerequisites](appv-prerequisites.md). Use the following procedure to install the Microsoft Application Virtualization (App-V) client so that it uses the App-V Shared Content Store (SCS) mode.
**Enable the App-V client for SCS mode** **Enable the App-V client for SCS mode**

5
windows/manage/appv-planning-for-sequencer-and-client-deployment.md
View File

@ -38,10 +38,7 @@ Ideally, you should install the sequencer on a computer running as a virtual mac
## Planning for App-V client deployment ## Planning for App-V client deployment
In Windows 10, version 1607, the App-V client is included with the operating system. For more info, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). In Windows 10, version 1607, the App-V client is included with the operating system. For more information, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
For a list of the client minimum requirements see [App-V Prerequisites](appv-prerequisites.md).
## Planning for the App-V Shared Content Store (SCS) ## Planning for the App-V Shared Content Store (SCS)

44
windows/manage/appv-prerequisites.md
View File

@ -517,50 +517,6 @@ The Reporting database is required only if you are using the App-V Reporting ser
</tbody> </tbody>
</table> </table>
 
## App-V client prerequisite software
Install the following prerequisite software for the App-V client.
> [!NOTE]
> This is not required on Windows 10, version 1607.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Prerequisite</th>
<th align="left">Details</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><p>[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595)</p>
<p></p></td>
<td align="left"><p>Installing PowerShell 3.0 requires a restart.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[KB2533623](http://support.microsoft.com/kb/2533623)</p></td>
<td align="left"><p>Applies to Windows 7 only: Download and install the KB.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784)</p></td>
<td align="left"><p></p></td>
</tr>
</tbody>
</table>
 
## Remote Desktop Services client prerequisite software ## Remote Desktop Services client prerequisite software

147
windows/manage/appv-release-notes-for-appv-for-windows.md
View File

@ -13,150 +13,39 @@ ms.prod: w10
Applies to: Windows 10, version 1607 Applies to: Windows 10, version 1607
Review these known issues in Microsoft Application Virtualization (App-V) for Windows. The following is a known issue in Microsoft Application Virtualization (App-V) Windows 10 Anniversary Update:
**MSI packages generated by App-V 5.1 and older sequencer fail to install on computers with built-in App-V client**
When MSI packages are generated by an older sequencer (5.1 and below), they include a check to ensure the App-V client is installed before allowing the MSI package to install. Since App-V client is now part of the operating system, the pre-requisite check fails and it leads to MSI installation failure.
## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10 **Workaround**:
1. Install the latest App-V sequencer, which is part of the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1607. See [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). For more information, see [Install the App-V Sequencer](appv-install-the-sequencer).
An error is generated during publishing refresh when synchronizing packages from the App-V 5.0 SP3 management server to an App-V client on Windows 10 . This error occurs because the App-V 5.0 SP3 server does not understand the Windows 10 operating system that is specified in the publishing URL. The issue is fixed for App-V publishing server, but is not backported to versions of App-V 5.0 SP3 or earlier. 2. Ensure that you have installed the **MSI Tools** included in the Windows 10 SDK, available as follows:
**Workaround**: Upgrade the App-V 5.0 management server to the App-V management server for Windows 10 clients. - For the **Visual Studio Community 2015 with Update 3** client, which includes the latest Windows 10 SDK and developer tools, see [Downloads and tools for Windows 10](https://developer.microsoft.com/en-us/windows/downloads).
- For the standalone Windows 10 SDK without other tools, see [Standalone Windows 10 SDK](https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk).
## Custom configurations do not get applied for packages that will be published globally if they are set using the App-V Server 3. From an elevated Windows PowerShell prompt, navigate to the following folder:
&lt;Windows Kits 10 installation folder&gt;**\Microsoft Application Virtualization\Sequencer\**
If you assign a package to an AD group that contains machine accounts and apply a custom configuration to that group using the App-V Server, the custom configuration will not be applied to those machines. The App-V Client will publish packages assigned to a machine account globally. However, it stores custom configuration files per user in each user’s profile. Globally published packages will not have access to this custom configuration. By default, this path will be:<br>**C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer**
**Workaround**: Do one of the following: 4. Run the following command:
- Assign the package to groups containing only user accounts. This will ensure that the package’s custom configuration is stored in each user’s profile and will be applied correctly. `Update-AppvPackageMsi -MsiPackage "<path to App-V Package .msi file>" -MsSdkPath "<path to Windows SDK installation>"`
- Create a custom deployment configuration file and apply it to the package on the client using the Add-AppvClientPackage cmdlet with the –DynamicDeploymentConfiguration parameter. See [About App-V Dynamic Configuration](appv-dynamic-configuration.md) for more information. By default, the path to the Windows SDK installation will be:<br>**C:\Program Files (x86)\Windows Kits\10**
- Create a new package with the custom configuration using the App-V sequencer.
## Server files not deleted after new App-V for Windows server installation
If you uninstall the App-V 5.0 SP1 Server and then install the App-V Server, the installation fails, the wrong version of the Management server is installed, and an error message is returned. The issue occurs because the Server files are not being deleted when you uninstall App-V 5.0 SP1, so the installation process does an upgrade instead of a new installation.
**Workaround**: Delete this registry key before you start installing App-V:
Under HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall, locate and delete the installation GUID key that contains the DWORD value "DisplayName" with value data "Microsoft Application Virtualization (App-V) Server". This is the only key that should be deleted.
## File type associations added manually are not saved correctly
File type associations added to an application package manually using the Shortcuts and FTAs tab at the end of the application upgrade wizard are not saved correctly. They will not be available to the App-V Client or to the Sequencer when updating the saved package again.
**Workaround**: To add a file type association, open the package for modification and run the update wizard. During the Installation step, add the new file type association through the operating system. The sequencer will detect the new association in the system registry and add it to the package’s virtual registry, where it will be available to the client.
## When streaming packages in Shared Content Store (SCS) mode to a client that is also managed with AppLocker, additional data is written to the local disk.
To decrease the amount of data written to a client’s local disk, you can enable SCS mode on the App-V Client to stream the contents of a package on demand. However, if AppLocker manages an application within the package, some data might be written to the client’s local disk that would not otherwise be written.
**Workaround**: None
## In the Management Console Add Package dialog box, the Browse button is not available when using Chrome or Firefox
On the Packages page of the Management Console, if you click **Add or Upgrade** in the lower-right corner, the **Add Package** dialog box appears. If you are accessing the Management Console using Chrome or Firefox as your browser, you will not be able to browse to the location of the package.
**Workaround**: Type or copy and paste the path to the package into the **Add Package** input field. If the Management Console has access to this path, you will be able to add the package. If the package is on a network share, you can browse to the location using File Explorer by doing these steps:
1. While pressing **Shift**, right-click on the package file
2. Select **Copy as path**
3. Paste the path into the **Add Package** dialog box input field
## <a href="" id="upgrading-app-v-management-server-to-5-1-sometimes-fails-with-the-message--a-database-error-occurred-"></a>Upgrading App-V Management Server to 5.1 sometimes fails with the message “A database error occurred”
If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V Server when multiple connection groups are configured and enabled, the following error is displayed: “A database error occurred. Reason: 'Invalid column name 'PackageOptional'. Invalid column name 'VersionOptional'.”
**Workaround**: Run this command on your SQL database:
`ALTER TABLE AppVManagement.dbo.PackageGroupMembers ADD PackageOptional bit NOT NULL DEFAULT 0, VersionOptional bit NOT NULL DEFAULT 0`
where “AppVManagement” is the name of the database.
## Users cannot open a package in a user-published connection group if you add or remove an optional package
In environments that are running the RDS Client or that have multiple concurrent users per computer, logged-in users cannot open applications in packages that are in a user-published connection group if an optional package is added to or removed from the connection group.
**Workaround**: Have users log out and then log back in.
## Error message is erroneously displayed when the connection group is published only to the user
When you run Repair-AppvClientConnectionGroup, the following error is displayed, even when the connection group is published only to the user: “Internal App-V Integration error: Package not integrated for the user. Please ensure that the package is added to the machine and published to the user.”
**Workaround**: Do one of the following:
- Publish all packages in a connection group.
The problem arises when the connection group being repaired has packages that are missing or not available to the user (that is, not published globally or to the user). However, the repair will work if all of the connection group’s packages are available, so ensure that all packages are published.
- Repair packages individually using the Repair-AppvClientPackage command rather than the Repair-AppvClientConnectionGroup command.
Determine which packages are available to users and then run the Repair-AppvClientPackage command once for each package. Use PowerShell cmdlets to do the following:
1. Get all the packages in a connection group.
2. Check to see if each package is currently published.
3. If the package is currently published, run Repair-AppvClientPackage on that package.
## Icons not displayed properly in Sequencer
Icons in the Shortcuts and File Type Associations tab are not displayed correctly when modifying a package in the App-V Sequencer. This problem occurs when the size of the icons are not 16x16 or 32x32.
**Workaround**: Only use icons that are 16x16 or 32x32.
## InsertVersionInfo.sql script no longer required for the Management Database
The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.
The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340).
**Important**  
**Step 1** is not required for versions of App-V later than App-V 5.0 SP3.
 
## Microsoft Visual Studio 2012 not supported
App-V does not support Visual Studio 2012.
**Workaround**: None
## Application filename restrictions for App-V Sequencer
The App-V Sequencer cannot sequence applications with filenames matching "CO_&lt;x&gt;" where x is any numeral. Error 0x8007139F will be generated.
**Workaround**: Use a different filename
## 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). 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 [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 ## Related topics
[About App-V](appv-about-appv.md) [About App-V](appv-about-appv.md)