mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 06:47:21 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into live
This commit is contained in:
LizRoss
commit
7b1734ff7c
@ -154,7 +154,7 @@ This screen is purely informational, and shows which recommended settings have b
|
||||
|
||||
### Details
|
||||
|
||||
You should read this screen and note which services have been enabled by default. All of them can be changed using the Settings app if need be, but you should be careful about the effects of doing so. For example, Cortana depends on some of these settings, and may not work if you disable them. See [Intro to Surface Hub](intro-to-surface-hub.md) for details.
|
||||
You should read this screen and note which services have been enabled by default. All of them can be changed using the Settings app if need be, but you should be careful about the effects of doing so. See [Intro to Surface Hub](intro-to-surface-hub.md) for details.
|
||||
|
||||
Once you're done reviewing the settings, click **Next** to go on.
|
||||
|
||||
@ -185,9 +185,8 @@ Click **Skip setting up a device account** to skip setting up a device account.
|
||||
|
||||
- See a meeting calendar on the Welcome screen
|
||||
- Start a meeting from the Welcome screen
|
||||
- Start a meeting using Cortana
|
||||
- Email whiteboards from OneNote
|
||||
- Use Skype for Business for meetings.
|
||||
- Use Skype for Business for meetings
|
||||
|
||||
If you skip setting it up now, you can add a device account later by using the Settings app.
|
||||
|
||||
@ -222,7 +221,6 @@ Click **Skip setting up Exchange services** to skip this step. If you do, people
|
||||
|
||||
- See a meeting calendar on the welcome screen.
|
||||
- Start a meeting from the welcome screen.
|
||||
- Start a meeting using Cortana.
|
||||
- Email whiteboards from OneNote.
|
||||
|
||||
See [Intro to Surface Hub](intro-to-surface-hub.md) for details on setup dependencies.
|
||||
|
||||
@ -62,7 +62,6 @@ User interface (UI) settings are returned to their default values when **I'm Don
|
||||
- Reset Quick Actions to default state
|
||||
- Clear Toast notifications
|
||||
- Reset volume levels
|
||||
- Reset Cortana relaunch count
|
||||
- Reset sidebar width
|
||||
- Reset tablet mode layout
|
||||
|
||||
|
||||
@ -44,10 +44,6 @@ The capabilities of your Surface Hub will depend on what other Microsoft product
|
||||
<td align="left"><p>Web browsing through Microsoft Edge</p></td>
|
||||
<td align="left"><p>Internet connectivity.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Cortana meeting room assistant (voice commands, search)</p></td>
|
||||
<td align="left"><p>Internet connectivity needed to process questions and do searches.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Remote and multi-device management</p></td>
|
||||
<td align="left"><p>Supported mobile device management (MDM) solutions (Microsoft Intune, System Center 2012 R2 Configuration Manager, or supported third-party solution).</p></td>
|
||||
|
||||
@ -49,13 +49,13 @@ System Center 2012 R2 Endpoint Protection<br>System Center 2012 Configuration Ma
|
||||
|
||||
You can use PowerShell to detect PUA without blocking them. In fact, you can run audit mode on individual machines. This feature is useful if your company is conducting an internal software security compliance check and you’d like to avoid any false positives.
|
||||
|
||||
1. Open PowerShell as Administrator <br>
|
||||
1. Open PowerShell as Administrator: <br>
|
||||
|
||||
a. Click **Start**, type **powershell**, and press **Enter**.
|
||||
|
||||
|
||||
b. Click **Windows PowerShell** to open the interface.
|
||||
> [!NOTE]
|
||||
> You may need to open an administrator-level version of PowerShell. Right-click the item in the Start menu, click **Run as administrator** and click **Yes** at the permissions prompt.
|
||||
>[!NOTE]
|
||||
>You may need to open an administrator-level version of PowerShell. Right-click the item in the Start menu, click **Run as administrator** and click **Yes** at the permissions prompt.
|
||||
2. Enter the PowerShell command:
|
||||
|
||||
```text
|
||||
@ -72,7 +72,22 @@ You can use PowerShell to detect PUA without blocking them. In fact, you can run
|
||||
|
||||
###Use PUA audit mode in Intune
|
||||
|
||||
You can detect PUA without blocking them from your client. Gain insights into what can be blocked.
|
||||
You can detect PUA without blocking them from your client so you can gain insights into what can be blocked.
|
||||
|
||||
1. Open PowerShell as Administrator: <br>
|
||||
|
||||
a. Click **Start**, type **powershell**, and press **Enter**.
|
||||
|
||||
b. Click **Windows PowerShell** to open the interface.
|
||||
|
||||
>[!NOTE]
|
||||
>You may need to open an administrator-level version of PowerShell. Right-click the item in the Start menu, click **Run as administrator** and click **Yes** at the permissions prompt.
|
||||
|
||||
2. Enter the PowerShell command:
|
||||
|
||||
```text
|
||||
et-mpPreference -puaprotection 1
|
||||
```
|
||||
|
||||
##View PUA events
|
||||
|
||||
|
||||
@ -52,22 +52,20 @@
|
||||
##### [App-V Capacity Planning](appv-capacity-planning.md)
|
||||
##### [Planning for High Availability with App-V](appv-planning-for-high-availability-with-appv.md)
|
||||
##### [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md)
|
||||
##### [Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md)
|
||||
##### [Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)
|
||||
##### [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)
|
||||
##### [Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)
|
||||
##### [Planning for Using App-V with Office](appv-planning-for-using-appv-with-office.md)
|
||||
##### [Planning to Use Folder Redirection with App-V](appv-planning-folder-redirection-with-appv.md)
|
||||
#### [App-V Planning Checklist](appv-planning-checklist.md)
|
||||
### [Deploying App-V](appv-deploying-appv.md)
|
||||
#### [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
#### [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
##### [About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
##### [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
##### [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
|
||||
##### [How to Install the Sequencer](appv-install-the-sequencer.md)
|
||||
##### [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
#### [Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
|
||||
##### [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md)
|
||||
##### [How to Deploy the App-V 5.1 Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
#### [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
##### [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
|
||||
##### [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
##### [How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md)
|
||||
##### [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md)
|
||||
##### [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md)
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Application development for Windows as a service (Windows 10)
|
||||
description: In today’s environment, where user expectations frequently are set by device-centric experiences, complete product cycles need to be measured in months, not years.
|
||||
description: Microsoft recommends that our ISV partners decouple their app release and support from specific Windows builds.
|
||||
ms.assetid: 28E0D103-B0EE-4B14-8680-6F30BD373ACF
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, servicing
|
||||
author: greg-lindsay
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Application development for Windows as a service
|
||||
@ -14,7 +14,7 @@ author: greg-lindsay
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
- Windows 10 IoT Core (IoT Core)
|
||||
- Windows 10 IoT Core
|
||||
|
||||
In today’s environment, where user expectations frequently are set by device-centric experiences, complete product cycles need to be measured in months, not years. Additionally, new releases must be made available on a continual basis, and must be deployable with minimal impact on users. Microsoft designed Windows 10 to meet these requirements by implementing a new approach to innovation, development, and delivery called [Windows as a service (WaaS)](introduction-to-windows-10-servicing.md). The key to enabling significantly shorter product cycles while maintaining high quality levels is an innovative community-centric approach to testing that Microsoft has implemented for Windows 10. The community, known as Windows Insiders, is comprised of millions of users around the world. When Windows Insiders opt in to the community, they test many builds over the course of a product cycle and provide feedback to Microsoft through an iterative methodology called flighting.
|
||||
|
||||
@ -25,6 +25,7 @@ Builds distributed as flights provide the Windows engineering team with signific
|
||||
Although Microsoft releases flight builds to Windows Insiders, Microsoft will publish two types of Windows 10 releases broadly to the public on an ongoing basis:
|
||||
|
||||
**Feature updates** install the latest new features, experiences, and capabilities on devices that are already running Windows 10. Because feature updates contain an entire copy of Windows, they are also what customers use to install Windows 10 on existing devices running Windows 7 or Windows 8.1, and on new devices where no operating system is installed. Microsoft expects to publish an average of one to two new feature updates per year.
|
||||
|
||||
**Quality updates** deliver security issue resolutions and other important bug fixes. Quality updates will be provided to improve each feature currently in support, on a cadence of one or more times per month. Microsoft will continue publishing quality updates on Update Tuesday (sometimes referred to as Patch Tuesday). Additionally, Microsoft may publish additional quality updates for Windows 10 outside the Update Tuesday process when required to address customer needs.
|
||||
|
||||
During Windows 10 development, Microsoft streamlined the Windows product engineering and release cycle so that we can deliver the features, experiences, and functionality customers want, more quickly than ever. We also created new ways to deliver and install feature updates and quality updates that simplify deployments and on-going management, broaden the base of employees who can be kept current with the latest Windows capabilities and experiences, and lower total cost of ownership. Hence we have implemented new servicing options – referred to as Current Branch (CB), Current Branch for Business (CBB), and Long-Term Servicing Branch (LTSB) – that provide pragmatic solutions to keep more devices more current in enterprise environments than was previously possible.
|
||||
@ -60,7 +61,7 @@ In the following sections, you will find additional information about the steps
|
||||
We understand that compatibility matters to developers. ISVs and developers want to ensure their apps will run as expected on all supported versions of the Windows OS. Consumers and businesses have a key investment here—they want to ensure that the apps they have paid for will continue to work. We know that compatibility is the primary criteria for purchase decisions. Apps that are well written based on best practices will lead to much less code churn when
|
||||
a new Windows version is released and will reduce fragmentation—these apps have a reduced engineering investment to maintain, and a faster time to market.
|
||||
|
||||
In the Windows 7 timeframe, compatibility was very much a reactive approach. In Windows 8 we started looking at this differently, working within Windows to ensure that compatibility was by design rather than an afterthought.
|
||||
In the Windows 7 timeframe, compatibility was very much a reactive approach. In Windows 8, we started looking at this differently, working within Windows to ensure that compatibility was by design rather than an afterthought.
|
||||
Windows 10 is the most compatible-by-design version of the OS to date. Here are some key ways we accomplished this:
|
||||
- **App telemetry**: This helps us understand app popularity in the Windows ecosystem to inform compatibility testing.
|
||||
- **ISV partnerships**: Work directly with external partners to provide them with data and help fix issues that our users experience.
|
||||
@ -68,15 +69,15 @@ Windows 10 is the most compatible-by-design version of the OS to date. Here are
|
||||
- **Communication**: Tighter control over API changes and improved communication.
|
||||
- **Flighting and feedback loop**: Windows insiders receive flighted builds that help improve our ability to find compatibility issues before a final build is released to customers. This feedback process not only exposes bugs, but ensures we are shipping features our users want.
|
||||
|
||||
## Microsoft uses data to make Windows 10 better
|
||||
## Best practices for app compatibility
|
||||
|
||||
Microsoft uses diagnostic and usage data to identify and troubleshoot problems, improve our products and services, and provide our users with personalized experiences. The usage data we collect also extends to the apps that PCs in the Windows ecosystem are running. Based on what our customers use, we build our list to test these apps, devices, and drivers against new versions of the Windows OS. Windows 10 has been the most compatible version of Windows to-date, with over 90% compatibility against thousands of popular apps. The Windows Compatibility team commonly reaches out to our ISV partners to provide feedback if issues are discovered, so that we can partner together on solutions. Ideally, we’d like our common customers to be able to update Windows seamlessly and without losing functionality in either their OS or the apps they depend on for their productivity or entertainment.
|
||||
|
||||
The following sections contain some best practices Microsoft recommends so you can ensure your apps are compatible with Windows 10.
|
||||
|
||||
**Windows version check**
|
||||
### Windows version check
|
||||
|
||||
The OS version has been incremented with Windows 10. This means that the internal version number has been changed to 10.0. As in the past, we go to great lengths to maintain application and device compatibility after an OS version change. For most app categories (without any kernel dependencies) the change will not negatively impact app functionality, and existing apps will continue to work fine on Windows 10.
|
||||
The OS version has been incremented with Windows 10. This means that the internal version number has been changed to 10.0. As in the past, we go to great lengths to maintain application and device compatibility after an OS version change. For most app categories (without any kernel dependencies), the change will not negatively impact app functionality, and existing apps will continue to work fine on Windows 10.
|
||||
|
||||
The manifestation of this change is app-specific. This means any app that specifically checks for the OS version will get a higher version number, which can lead to one or more of the following situations:
|
||||
- App installers might not be able to install the app, and apps might not be able to start.
|
||||
@ -91,16 +92,17 @@ Some apps perform a version check and simply pass a warning to users. However, t
|
||||
|
||||
If you own apps such as antimalware or firewall apps, you should work through your usual feedback channels and via the Windows Insider program.
|
||||
|
||||
**Undocumented APIs**
|
||||
### Undocumented APIs
|
||||
|
||||
Your apps should not call undocumented Windows APIs, or take dependency on specific Windows file exports or registry keys. This can lead to broken functionality, data loss, and potential security issues. If there is functionality your app requires that is not available, this is an opportunity to provide feedback through your usual feedback channels and via the Windows Insider program.
|
||||
|
||||
**Develop Universal Windows Platform (UWP) and Centennial apps**
|
||||
### Develop Universal Windows Platform (UWP) and Centennial apps
|
||||
|
||||
We encourage all Win32 app ISVs to develop [Universal Windows Platform (UWP)](http://go.microsoft.com/fwlink/?LinkID=780560) and, specifically, [Centennial](http://go.microsoft.com/fwlink/?LinkID=780562) apps moving forward. There are great benefits to developing these app packages rather than using traditional Win32 installers. UWP apps are also supported in the [Windows Store](http://go.microsoft.com/fwlink/?LinkID=780563), so it’s easier for you to update your users to a consistent version automatically, lowering your support costs.
|
||||
|
||||
If your Win32 app types do not work with the Centennial model, we highly recommend that you use the right installer and ensure this is fully tested. An installer is your user or customer’s first experience with your app, so ensure that this works well. All too often, this doesn’t work well or it hasn’t been fully tested for all scenarios. The [Windows App Certification Kit](http://go.microsoft.com/fwlink/?LinkID=780565) can help you test the install and uninstall of your Win32 app and help you identify use of undocumented APIs, as well as other basic performance-related best-practice issues, before your users do.
|
||||
|
||||
**Best pratcices:**
|
||||
**Best practices:**
|
||||
- Use installers that work for both 32-bit and 64-bit versions of Windows.
|
||||
- Design your installers to run on multiple scenarios (user or machine level).
|
||||
- Keep all Windows redistributables in the original packaging – if you repackage these, it’s possible that this will break the installer.
|
||||
@ -112,7 +114,7 @@ Windows OS flighting refers to the interim builds available to Windows Insiders
|
||||
|
||||
If your app is in the Store, you can flight your app via the Store, which means that your app will be available for our Windows Insider population to install. Users can install your app and you can receive preliminary feedback on your app before you release it to the general population. The follow sections outline the steps for testing your apps against Windows flighted builds.
|
||||
|
||||
**Step 1: Become a Windows Insider and participate in flighting**
|
||||
### Step 1: Become a Windows Insider and participate in flighting
|
||||
As a [Windows Insider,](http://go.microsoft.com/fwlink/p/?LinkId=521639) you can help shape the future of Windows—your feedback will help us improve features and functionality in the platform. This is a vibrant community where you can connect with other enthusiasts, join forums, trade advice, and learn about upcoming Insider-only events.
|
||||
|
||||
Since you’ll have access to preview builds of Windows 10, Windows 10 Mobile, and the latest Windows SDK and Emulator, you’ll have all the tools at your disposal to develop great apps and explore what's new in the Universal Windows Platform and the Windows Store.
|
||||
@ -127,7 +129,7 @@ Before you become a Windows Insider, please note that participation is intended
|
||||
- Know what an ISO file is and how to use it.
|
||||
- Aren't installing it on their everyday computer or device.
|
||||
|
||||
**Step 2: Test your scenarios**
|
||||
### Step 2: Test your scenarios
|
||||
|
||||
Once you have updated to a flighted build, the following are some sample test cases to help you get started on testing and gathering feedback. For most of these tests, ensure you cover both x86 and AMD64 systems.
|
||||
**Clean install test:** On a clean install of Windows 10, ensure your app is fully functional. If your app fails this test and the upgrade test, then it’s likely that the issue is caused by underlying OS changes or bugs in the app.
|
||||
@ -149,11 +151,11 @@ If after investigation, the former is the case, be sure to use the Windows Insid
|
||||
- Sensors (accelerometer, fusion, and so on)
|
||||
- Camera
|
||||
|
||||
**Step 3: Provide feedback**
|
||||
### Step 3: Provide feedback
|
||||
|
||||
Let us know how your app is performing against flighted builds. As you discover issues with your app during testing, please log bugs via the partner portal if you have access, or through your Microsoft representative. We encourage this information so that we can build a quality experience for our users together.
|
||||
|
||||
**Step 4: Register on Windows 10**
|
||||
### Step 4: Register on Windows 10
|
||||
The [Ready for Windows 10](http://go.microsoft.com/fwlink/?LinkID=780580) website is a directory of software that supports Windows 10. It’s intended for IT administrators at companies and organizations worldwide that are considering Windows 10 for their deployments. IT administrators can check the site to see whether software deployed in their enterprise is supported in Windows 10.
|
||||
|
||||
## Related topics
|
||||
|
||||
@ -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** > **Virtual Registry** > **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** > **Virtual File System** > **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** > **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** > **Virtual File System** > **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
|
||||
|
||||
|
||||
@ -1059,7 +1059,7 @@ For situations where there is more than one application that could register the
|
||||
|
||||
The AppPath extension point supports calling App-V applications directly from the operating system. This is typically accomplished from the Run or Start Screen, depending on the operating system, which enables administrators to provide access to App-V applications from operating system commands or scripts without calling the specific path to the executable. It therefore avoids modifying the system path environment variable on all systems, as it is accomplished during publishing.
|
||||
|
||||
The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: [App Paths ? A Virtual Application Extension in App-V 5.0](https://blogs.technet.microsoft.com/virtualworld/2012/12/12/app-paths-a-virtual-application-extension-in-app-v-5-0/).
|
||||
The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: [App Paths - A Virtual Application Extension in App-V 5.0](https://blogs.technet.microsoft.com/virtualworld/2012/12/12/app-paths-a-virtual-application-extension-in-app-v-5-0/).
|
||||
|
||||
### Virtual application
|
||||
|
||||
|
||||
@ -47,23 +47,15 @@ Before you design the App-V infrastructure, determine the project’s scope. The
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Determine Which App-V Infrastructure is Required
|
||||
|
||||
|
||||
>**Important**
|
||||
Both of the following models require the App-V client to be installed on the computer where you plan to run virtual applications.
|
||||
|
||||
You can also manage your App-V environment using an Electronic Software Distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information see [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
|
||||
|
||||
- **Standalone Model** - The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V in Standalone Mode consists of the sequencer and the client; no additional components are required. Applications are prepared for virtualization using a process called sequencing. For more information see, [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md). The stand-alone model is recommended for the following scenarios:
|
||||
|
||||
- With disconnected remote users who cannot connect to the App-V infrastructure.
|
||||
|
||||
- When you are running a software management system, such as Configuration Manager 2012.
|
||||
- When you are running a software management system, such as System Center 2012 Configuration Manager.
|
||||
|
||||
- When network bandwidth limitations inhibit electronic software distribution.
|
||||
|
||||
@ -925,7 +917,7 @@ For example, an average user can stream a 100 MB package in less than 2 minutes,
|
||||
|
||||
The number of clients a streaming server can support can be significantly increased and the peak streaming requirements reduced if you pre-cache your applications. You can also increase the number of clients a streaming server can support by using on-demand streaming delivery and stream optimized packages.
|
||||
|
||||
## Combining App-V 5.1 Server Roles
|
||||
## Combining App-V Server Roles
|
||||
|
||||
|
||||
Discounting scaling and fault-tolerance requirements, the minimum number of servers needed for a location with connectivity to Active Directory is one. This server will host the management server, management server service, and Microsoft SQL Server roles. Server roles, therefore, can be arranged in any desired combination since they do not conflict with one another.
|
||||
|
||||
@ -108,6 +108,6 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
## Related topics
|
||||
|
||||
[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Deploy the App-V Server (new installataion)
|
||||
# How to Deploy the App-V Server (new installation)
|
||||
|
||||
>**Important**<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.
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ App-V supports a number of different deployment options. Review this topic for i
|
||||
## App-V Deployment Information
|
||||
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
This section describes how to install the App-V sequencer, which is used to virtualize applications, and how to enable the App-V client, which runs on target computers to facilitate virtualized packages.
|
||||
|
||||
|
||||
@ -72,9 +72,9 @@ Sequencing Office 2010 is one of the main methods for creating an Office 2010 pa
|
||||
|
||||
Office 2010 App-V packages can be created through package accelerators. Microsoft has provided package accelerators for creating Office 2010 on Windows 10, Windows 8 and Windows 7. To create Office 2010 packages on App-V using Package accelerators, refer to the following pages to access the appropriate package accelerator:
|
||||
|
||||
- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](http://go.microsoft.com/fwlink/p/?LinkId=330677)
|
||||
- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](https://gallery.technet.microsoft.com/App-V-50-Package-a29410db)
|
||||
|
||||
- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](http://go.microsoft.com/fwlink/p/?LinkId=330678)
|
||||
- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](https://gallery.technet.microsoft.com/App-V-50-Package-e7ef536b)
|
||||
|
||||
For detailed instructions on how to create virtual application packages using App-V package accelerators, see [How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md).
|
||||
|
||||
|
||||
@ -133,7 +133,7 @@ The following table describes the recommended methods for excluding specific Off
|
||||
<td align="left"><p>Use the <strong>ExcludeApp</strong> setting when you create the package by using the Office Deployment Tool.</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.</p></li>
|
||||
<li><p>For more information, see [ExcludeApp element](http://technet.microsoft.com/library/jj219426.aspx#bkmk-excludeappelement).</p></li>
|
||||
<li><p>For more information, see [ExcludeApp element](https://technet.microsoft.com/library/jj219426.aspx#BKMK_ExcludeAppElement).</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -205,7 +205,7 @@ Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the
|
||||
|
||||
Office 2013 App-V Packages are created using the Office Deployment Tool, which generates an Office 2013 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation:
|
||||
|
||||
1. Download the [Office Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778).
|
||||
1. Download the [Office 2013 Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778).
|
||||
|
||||
2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
|
||||
|
||||
@ -810,7 +810,7 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
<tr class="odd">
|
||||
<td align="left"><p>How do I package and publish Visio 2013 and Project 2013 with Office?</p></td>
|
||||
<td align="left"><p>You must include Visio 2013 and Project 2013 in the same package with Office.</p>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the [Virtualizing Microsoft Office 2013 for Application Virtualization (App-V) 5.0](https://technet.microsoft.com/en-us/itpro/mdop/solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions#bkmk-pkg-pub-reqs).</p></td>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>How can I deploy Visio 2013 and Project 2013 to specific users?</p></td>
|
||||
@ -841,7 +841,7 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
<ol>
|
||||
<li><p>Create a package that contains Office, Visio, and Project.</p></li>
|
||||
<li><p>Deploy the package to all users.</p></li>
|
||||
<li><p>Use [Microsoft AppLocker](http://technet.microsoft.com/library/dd723678.aspx) to prevent specific users from using Visio and Project.</p></li>
|
||||
<li><p>Use [AppLocker](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/applocker-overview) to prevent specific users from using Visio and Project.</p></li>
|
||||
</ol></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@ -858,13 +858,13 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
|
||||
**Office 2013 App-V Packages Additional Resources**
|
||||
|
||||
[Office Deployment Tool for Click-to-Run](http://go.microsoft.com/fwlink/p/?LinkID=330672)
|
||||
[Office 2013 Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778)
|
||||
|
||||
[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://support.microsoft.com/en-us/kb/2772509)
|
||||
|
||||
**Office 2010 App-V Packages**
|
||||
|
||||
[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://www.microsoft.com/en-us/download/details.aspx?id=38399)
|
||||
[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://www.microsoft.com/download/details.aspx?id=38399)
|
||||
|
||||
[Known issues when you create or use an App-V 5.0 Office 2010 package](https://support.microsoft.com/en-us/kb/2828619)
|
||||
|
||||
@ -882,14 +882,4 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
|
||||
## 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).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ To deploy App-V packages with Microsoft System Center 2012 Configuration Manage
|
||||
## How to deploy virtualized packages using an ESD
|
||||
|
||||
|
||||
Describes the methods you can use to deploy App-V packages by using an ESD
|
||||
Describes the methods you can use to deploy App-V packages by using an ESD.
|
||||
|
||||
[How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md)
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Deploy the App-V Sequencer and Client (Windows 10)
|
||||
description: Deploying the App-V Sequencer and Client
|
||||
title: Deploying the App-V Sequencer and Configuring the Client (Windows 10)
|
||||
description: Deploying the App-V Sequencer and Configuring the Client
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,13 +9,12 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Deploying the App-V Sequencer and Client
|
||||
# Deploying the App-V Sequencer and Configuring the Client
|
||||
|
||||
The App-V Sequencer and client enable administrators to virtualize and run virtualized applications.
|
||||
|
||||
## Enable the client
|
||||
|
||||
|
||||
The App-V client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and to double-click file types, so that they can start a virtualized application. The client can also obtain the virtual application content from the management server.
|
||||
|
||||
> [!NOTE]
|
||||
@ -25,7 +24,6 @@ The App-V client is the component that runs a virtualized application on a targe
|
||||
|
||||
## Client Configuration Settings
|
||||
|
||||
|
||||
The App-V client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries.
|
||||
|
||||
[About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
@ -34,7 +32,6 @@ The App-V client stores its configuration in the registry. You can gather some u
|
||||
|
||||
You can use Group Policy to configure the client settings for the App-V client and the Remote Desktop Services client.
|
||||
|
||||
|
||||
Perform the following steps on the computer that you will use to manage Group Policy. This is typically the Domain Controller.
|
||||
|
||||
1. Save the **.admx** file to the following directory: **Windows \\ PolicyDefinitions**
|
||||
@ -43,11 +40,9 @@ Perform the following steps on the computer that you will use to manage Group Po
|
||||
|
||||
After you have completed the preceding steps, you can manage the App-V client configuration settings with the **Group Policy Management** console.
|
||||
|
||||
The App-V client also stores its configuration in the registry. You can gather some useful information about the client if you understand the format of the data in the registry. You can also configure many client actions by changing registry entries.
|
||||
|
||||
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
|
||||
## Deploy the client by using the Shared Content Store mode
|
||||
## Understanding Shared Content Store mode for App-V clients
|
||||
|
||||
The App-V Shared Content Store (SCS) mode enables the SCS App-V clients to run virtualized applications without saving any of the associated package data locally. All required virtualized package data is transmitted across the network; therefore, you should only use the SCS mode in environments with a fast connection. Both the Remote Desktop Services (RDS) and the standard version of the App-V client are supported with SCS mode.
|
||||
|
||||
@ -62,15 +57,25 @@ The SCS mode is helpful in the following scenarios:
|
||||
|
||||
- Remote Desktop Services deployments
|
||||
|
||||
To use SCS in your environment, you must enable the App-V client to run in SCS mode. This setting should be specified during installation. By default, the client is not configured to use SCS mode. You should install the client by using the suggested procedure if you plan to use SCS. However, you can configure an existing App-V client to run in SCS mode by entering the following Windows PowerShell command on the computer that runs the App-V client:
|
||||
|
||||
```
|
||||
set-AppvClientConfiguration -SharedContentStoreMode 1
|
||||
```
|
||||
To use SCS in your environment, you must configure the App-V client to run in SCS mode (it will not use SCS mode by default).
|
||||
|
||||
There might be cases when the administrator pre-loads some virtual applications on the computer that runs the App-V client in SCS mode. This can be accomplished with Windows PowerShell commands to add, publish, and mount the package. For example, if a package is pre-loaded on all computers, the administrator could add, publish, and mount the package by using Windows PowerShell commands. The package would not stream across the network because it would be locally stored.
|
||||
|
||||
[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
|
||||
### Configure the Group Policy setting for the SCS Mode for App-V clients
|
||||
|
||||
Use the following steps to locate and configure the Group Policy setting for the SCS Mode for App-V clients.
|
||||
|
||||
1. In the Group Policy Management Console, navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Streaming**.
|
||||
|
||||
2. Enable the **Set the Shared Content Mode (SCS) mode** setting.
|
||||
|
||||
### Configure an individual client to use the SCS mode
|
||||
|
||||
To configure the App-V client to run in SCS mode, on the client, enter the following Windows PowerShell command:
|
||||
|
||||
```
|
||||
Set-AppvClientConfiguration -SharedContentStoreMode 1
|
||||
```
|
||||
|
||||
## Deploy the Sequencer
|
||||
|
||||
@ -87,11 +92,6 @@ You can use the App-V Sequencer log information to help troubleshoot the Sequenc
|
||||
|
||||
**Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**. Sequencer-related events are prepended with **AppV\_Sequencer**. Client-related events are prepended with **AppV\_Client**.
|
||||
|
||||
## Other resources for deploying the Sequencer and client
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
- [Planning for App-V](appv-planning-for-appv.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).
|
||||
|
||||
@ -74,7 +74,7 @@ The distributed deployment topology can support a large App-V client base and it
|
||||
- [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md)
|
||||
|
||||
## Using an Enterprise Software Distribution (ESD) solution and App-V
|
||||
You can also deploy the App-V clients and packages by using an ESD without having to deploy App-V. The full capabilities for integration will vary depending on the ESD that you use.
|
||||
You can also deploy packages by using an ESD. The full capabilities for integration will vary depending on the ESD that you use.
|
||||
|
||||
>**Note**<br>The App-V reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V clients. However, the other three server components should not be deployed, because they will conflict with the ESD functionality.
|
||||
|
||||
|
||||
@ -41,7 +41,7 @@ This checklist outlines the recommended steps and items to consider when deployi
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>Review the App-V supported configurations information to make sure selected client and server computers are supported for App-V feature installation.</p></td>
|
||||
<td align="left"><p>Review the App-V supported configurations information.</p></td>
|
||||
<td align="left"><p>[App-V Supported Configurations](appv-supported-configurations.md)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
|
||||
@ -636,7 +636,7 @@ The following table describes the various script events and the context under wh
|
||||
|
||||
### Using 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 convert from App-V 4.6 to App-V for Windows 10. 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.
|
||||
App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you convert from App-V 4.6 to App-V for Windows 10. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is included in the App-V client.
|
||||
|
||||
**How to use multiple scripts on a single event trigger:**
|
||||
|
||||
@ -683,10 +683,10 @@ Using the following example file and table, modify the deployment or user config
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><code><Path>ScriptRunner.exe</Path></code></p></td>
|
||||
<td align="left"><p>The script launcher application that is installed as part of the App-V client installation.</p>
|
||||
<td align="left"><p>The script launcher application that is included in the App-V client.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Although ScriptRunner.exe is installed as part of the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.</p>
|
||||
<p>Although ScriptRunner.exe is included in the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
@ -31,7 +31,7 @@ The topics in this section provide information and step-by-step procedures to he
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
- [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
- [App-V Deployment Checklist](appv-deployment-checklist.md)
|
||||
- [Deploying Microsoft Office 2013 by Using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
|
||||
|
||||
@ -1,29 +1,4 @@
|
||||
---
|
||||
title: How to Install the App-V Client for Shared Content Store Mode (Windows 10)
|
||||
description: How to Install the App-V Client for Shared Content Store Mode
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
redirect_url: https://technet.microsoft.com/itpro/windows/manage/appv-deploying-the-appv-sequencer-and-client
|
||||
---
|
||||
|
||||
|
||||
# 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.
|
||||
|
||||
**Enable the App-V client for SCS mode**
|
||||
|
||||
1. In the Group Policy Management Console, navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Streaming**.
|
||||
|
||||
2. Enable the **Set the Shared Content Mode (SCS) mode** setting.
|
||||
|
||||
## 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
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
@ -17,8 +17,6 @@ Use the following procedure to install the database server and management server
|
||||
>**Note**
|
||||
After you complete the deployment, the **Microsoft SQL Server name**, **instance name** and **database name** will be required by the administrator installing the service to be able to connect to these databases.
|
||||
|
||||
|
||||
|
||||
**To install the management database and the management server on separate computers**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
@ -40,11 +38,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
|
||||
7. On the next **Create New Management Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
|
||||
|
||||
>**Note**
|
||||
If you plan to deploy the management server on the same computer you must select **Use this local computer**.
|
||||
|
||||
|
||||
|
||||
Specify the user name for the management server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**.
|
||||
If you plan to deploy the management server on the same computer you must select **Use this local computer**. Specify the user name for the management server **Install Administrator** using the following format: Domain\\AdministratorLoginName. Click **Next**.
|
||||
|
||||
8. To start the installation, click **Install**.
|
||||
|
||||
@ -66,14 +60,10 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
|
||||
|
||||
If you are using a custom database name, then select **Custom configuration** and type the database name.
|
||||
|
||||
7. On the next **Create New Reporting Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
|
||||
7. On the next **Create New Reporting Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: Domain\\MachineAccount.
|
||||
|
||||
**Note**
|
||||
If you plan to deploy the reporting server on the same computer you must select **Use this local computer**.
|
||||
|
||||
|
||||
|
||||
Specify the user name for the reporting server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**.
|
||||
If you plan to deploy the reporting server on the same computer you must select **Use this local computer**. Specify the user name for the reporting server **Install Administrator** using the following format: Domain\\AdministratorLoginName. Click **Next**.
|
||||
|
||||
8. To start the installation, click **Install**.
|
||||
|
||||
@ -83,7 +73,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
|
||||
|
||||
2. To extract the App-V database scripts, open a command prompt and specify the location where the installation files are saved and run the following command:
|
||||
|
||||
**appv\_server\_setup.exe** **/LAYOUT** **/LAYOUTDIR=”InstallationExtractionLocation”**.
|
||||
**appv\_server\_setup.exe** **/LAYOUT** **/LAYOUTDIR=”InstallationExtractionLocation”**
|
||||
|
||||
3. After the extraction has been completed, to access the App-V database scripts and instructions readme file:
|
||||
|
||||
@ -94,13 +84,13 @@ 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 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.
|
||||
|
||||
**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
|
||||
|
||||
|
||||
@ -29,13 +29,7 @@ Use the following procedure to install the management server on a standalone com
|
||||
6. On the **Configure Existing Management Database** page, select **Use a remote SQL Server**, and type the machine name of the computer running Microsoft SQL SQL, for example **SqlServerMachine**.
|
||||
|
||||
>**Note**
|
||||
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**.
|
||||
|
||||
|
||||
|
||||
For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance.
|
||||
|
||||
Specify the **SQL Server Database name** that this management server will use, for example **AppvManagement**.
|
||||
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance. Specify the **SQL Server Database name** that this management server will use, for example **AppvManagement**.
|
||||
|
||||
7. On the **Configure Management Server Configuration** page, specify the AD group or account that will connect to the management console for administrative purposes for example **MyDomain\\MyUser** or **MyDomain\\AdminGroup**. The account or AD group you specify will be enabled to manage the server through the management console. You can add additional users or groups using the management console after installation
|
||||
|
||||
@ -45,7 +39,9 @@ Use the following procedure to install the management server on a standalone com
|
||||
|
||||
9. To confirm that the setup has completed successfully, open a web browser, and type the following URL: http://managementserver:portnumber/Console. If the installation was successful, you should see the **Management Console** appear without any error messages or warnings being displayed.
|
||||
|
||||
**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
|
||||
|
||||
|
||||
@ -46,23 +46,27 @@ Use the following procedure to install the publishing server on a separate compu
|
||||
|
||||
9. To verify that the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: **http://publishingserver:pubport**. If the server is running correctly information similar to the following will be displayed:
|
||||
|
||||
`<Publishing Protocol="1.0">`
|
||||
```syntax
|
||||
<Publishing Protocol="1.0">
|
||||
|
||||
<Packages>
|
||||
|
||||
` <Packages>`
|
||||
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />
|
||||
|
||||
</Packages>
|
||||
|
||||
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />`
|
||||
<NoGroup>
|
||||
|
||||
` </Packages>`
|
||||
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />
|
||||
|
||||
` <NoGroup>`
|
||||
</NoGroup>
|
||||
|
||||
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />`
|
||||
</Publishing>
|
||||
```
|
||||
|
||||
` </NoGroup>`
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
`</Publishing>`
|
||||
|
||||
**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
|
||||
|
||||
|
||||
@ -34,13 +34,7 @@ Before performing the following procedure you should read and understand [About
|
||||
6. On the **Configure Existing Reporting Database** page, select **Use a remote SQL Server**, and type the machine name of the computer running Microsoft SQL Server, for example **SqlServerMachine**.
|
||||
|
||||
**Note**
|
||||
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**.
|
||||
|
||||
|
||||
|
||||
For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance.
|
||||
|
||||
Specify the **SQL Server Database name** that this reporting server will use, for example **AppvReporting**.
|
||||
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance. Specify the **SQL Server Database name** that this reporting server will use, for example **AppvReporting**.
|
||||
|
||||
7. On the **Configure Reporting Server Configuration** page.
|
||||
|
||||
@ -50,7 +44,9 @@ Before performing the following procedure you should read and understand [About
|
||||
|
||||
8. Click **Install**.
|
||||
|
||||
**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
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ ms.prod: w10
|
||||
|
||||
An App-V connection group allows you to run all the virtual applications as a defined set of packages in a single virtual environment. For example, you can virtualize an application and its plug-ins by using separate packages, but run them together in a single connection group.
|
||||
|
||||
A connection group XML file defines the connection group that runs on the computer where you’ve installed the App-V client. For information about the connection group XML file and how to configure it, see [About the Connection Group File](appv-connection-group-file.md).
|
||||
A connection group XML file defines the connection group for the App-V client. For information about the connection group XML file and how to configure it, see [About the Connection Group File](appv-connection-group-file.md).
|
||||
|
||||
This topic explains the following procedures:
|
||||
|
||||
|
||||
@ -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.
|
||||
@ -202,53 +200,16 @@ After you convert an existing package you should test the package prior to deplo
|
||||
|
||||
|
||||
|
||||
When converting a package check for failing files or shortcuts. Locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path.
|
||||
When converting a package check for failing files or shortcuts, locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path.
|
||||
|
||||
**Note**
|
||||
It is recommended that you use the App-V sequencer for converting critical applications or applications that need to take advantage of features. See, [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).
|
||||
It is recommended that you use the App-V sequencer for converting critical applications or applications that need to take advantage of features. See [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).
|
||||
|
||||
If a converted package does not open after you convert it, it is also recommended that you re-sequence the application using the App-V sequencer.
|
||||
|
||||
|
||||
|
||||
[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)
|
||||
|
||||
## Migrating Clients
|
||||
|
||||
|
||||
The following table displays the recommended method for upgrading clients.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Task</th>
|
||||
<th align="left">More Information</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Upgrade your environment to the latest version of App-V 4.6</p></td>
|
||||
<td align="left"><p>[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Sequence and roll out App-V packages. As needed, unpublish App-V 4.6 packages.</p></td>
|
||||
<td align="left"><p>[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
You must be running the latest version of App-V 4.6 to use coexistence mode. Additionally, when you sequence a package, you must configure the Managing Authority setting, which is in the **User Configuration** is located in the **User Configuration** section.
|
||||
|
||||
|
||||
|
||||
## Migrating the App-V server Server Full Infrastructure
|
||||
## Migrating the App-V Server Full Infrastructure
|
||||
|
||||
|
||||
There is no direct method to upgrade to a full App-V infrastructure. Use the information in the following section for information about upgrading the App-V server.
|
||||
@ -266,20 +227,20 @@ There is no direct method to upgrade to a full App-V infrastructure. Use the inf
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Upgrade your environment to the latest version of App-V 4.6.</p></td>
|
||||
<td align="left"><p>[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).</p></td>
|
||||
<td align="left"><p>Review prerequisites.</p></td>
|
||||
<td align="left"><p>[App-V Server prerequisite software](appv-prerequisites.md#app-v-server-prerequisite-software).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Deploy App-V version of the client.</p></td>
|
||||
<td align="left"><p>Enable the App-V client.</p></td>
|
||||
<td align="left"><p>[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Install App-V server server.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V server Server](appv-deploy-the-appv-server.md).</p></td>
|
||||
<td align="left"><p>Install App-V Server.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V Server](appv-deploy-the-appv-server.md).</p></td>
|
||||
</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](#converting-packages-created-using-a-prior-version-of-app-v) earlier in this topic.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -171,9 +171,9 @@ The following table displays the required steps to prepare the base image and th
|
||||
<tr class="odd">
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Install the App-V client version of the client.</p></li>
|
||||
<li><p>Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).</p></li>
|
||||
<li><p>Install UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.</p></li>
|
||||
<li><p>Configure for Shared Content Store (SCS) mode. For more information see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).</p></li>
|
||||
<li><p>Configure for Shared Content Store (SCS) mode. For more information see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).</p></li>
|
||||
<li><p>Configure Preserve User Integrations on Login Registry DWORD.</p></li>
|
||||
<li><p>Pre-configure all user- and global-targeted packages for example, <strong>Add-AppvClientPackage</strong>.</p></li>
|
||||
<li><p>Pre-configure all user- and global-targeted connection groups for example, <strong>Add-AppvClientConnectionGroup</strong>.</p></li>
|
||||
@ -191,9 +191,9 @@ The following table displays the required steps to prepare the base image and th
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Install the App-V client version of the client.</p></li>
|
||||
<li><p>Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).</p></li>
|
||||
<li><p>Install UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.</p></li>
|
||||
<li><p>Configure for Shared Content Store (SCS) mode. For more information see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).</p></li>
|
||||
<li><p>Configure for Shared Content Store (SCS) mode. For more information see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).</p></li>
|
||||
<li><p>Configure Preserve User Integrations on Login Registry DWORD.</p></li>
|
||||
<li><p>Pre-configure all global-targeted packages for example, <strong>Add-AppvClientPackage</strong>.</p></li>
|
||||
<li><p>Pre-configure all global-targeted connection groups for example, <strong>Add-AppvClientConnectionGroup</strong>.</p></li>
|
||||
@ -225,8 +225,7 @@ The following table displays the required steps to prepare the base image and th
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Shared Content Store (SCS) Mode</p>
|
||||
<ul>
|
||||
<li><p>Configurable in PowerShell using <strong>Set- AppvClientConfiguration</strong> –<strong>SharedContentStoreMode</strong>, or</p></li>
|
||||
<li><p>During installation of the App-V client.</p></li>
|
||||
<li><p>Configurable in Windows PowerShell with `Set-AppvClientConfiguration -SharedContentStoreMode 1`<br>or configurable with Group Policy, as described in [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>When running the shared content store only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM).</p>
|
||||
<p>This helps to conserve local storage and minimize disk I/O per second (IOPS).</p></td>
|
||||
|
||||
@ -41,14 +41,14 @@ This checklist can be used to help you plan for preparing your organization for
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>Plan for App-V 1.0 Deployment Prerequisites and prepare your computing environment.</p></td>
|
||||
<td align="left"><p>Plan for App-V deployment prerequisites and prepare your computing environment.</p></td>
|
||||
<td align="left"><p>[App-V Prerequisites](appv-prerequisites.md)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>If you plan to use the App-V management server, plan for the required roles.</p></td>
|
||||
<td align="left"><p>[Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md)</p></td>
|
||||
<td align="left"><p>[Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -60,13 +60,13 @@ This checklist can be used to help you plan for preparing your organization for
|
||||
<tr class="odd">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>If applicable, review the options and steps for migrating from a previous version of App-V.</p></td>
|
||||
<td align="left"><p>[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)</p></td>
|
||||
<td align="left"><p>[Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>Plan for running App-V clients using in shared content store mode.</p></td>
|
||||
<td align="left"><p>[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)</p></td>
|
||||
<td align="left"><p>Decide whether to configure App-V clients in Shared Content Store mode.</p></td>
|
||||
<td align="left"><p>[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Planning for the App-V 5.1 Server Deployment (Windows 10)
|
||||
title: Planning for the App-V Server Deployment (Windows 10)
|
||||
description: Planning for the App-V 5.1 Server Deployment
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -9,15 +9,15 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning for the App-V 5.1 Server Deployment
|
||||
# Planning for the App-V Server Deployment
|
||||
|
||||
|
||||
The Microsoft Application Virtualization (App-V) server infrastructure consists of a set of specialized features that can be installed on one or more server computers, based on the requirements of the enterprise.
|
||||
|
||||
## Planning for App-V 5.1 Server Deployment
|
||||
## Planning for App-V Server Deployment
|
||||
|
||||
|
||||
The App-V 5.1 server consists of the following features:
|
||||
The App-V server consists of the following features:
|
||||
|
||||
- Management Server – provides overall management functionality for the App-V infrastructure.
|
||||
|
||||
@ -29,9 +29,9 @@ The App-V 5.1 server consists of the following features:
|
||||
|
||||
- Reporting Database – facilitates database predeployments for App-V reporting.
|
||||
|
||||
The following list displays the recommended methods for installing the App-V 5.1 server infrastructure:
|
||||
The following list displays the recommended methods for installing the App-V server infrastructure:
|
||||
|
||||
- Install the App-V 5.1 server. For more information, see [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md).
|
||||
- Install the App-V server. For more information, see [How to Deploy the App-V Server](appv-deploy-the-appv-server.md).
|
||||
|
||||
- Install the database, reporting, and management features on separate computers. For more information, see [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md).
|
||||
|
||||
@ -54,7 +54,7 @@ The Management Server does not perform any load balancing. The associated metada
|
||||
## Server-Related Protocols and External Features
|
||||
|
||||
|
||||
The following displays information about server-related protocols used by the App-V 5.1 servers. The table also includes the reporting mechanism for each server type.
|
||||
The following displays information about server-related protocols used by the App-V servers. The table also includes the reporting mechanism for each server type.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -96,10 +96,10 @@ The following displays information about server-related protocols used by the Ap
|
||||
|
||||
## 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
|
||||
|
||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
[Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
|
||||
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
|
||||
@ -21,7 +21,7 @@ Use this information to plan how to deploy App-V so that it does not disrupt you
|
||||
|
||||
- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
This section describes the minimum hardware and software requirements necessary for App-V client, sequencer and server feature installations. Additionally, associated feature planning information is also displayed.
|
||||
This section describes the minimum hardware and software requirements and other planning information for the App-V sequencer and App-V server components.
|
||||
|
||||
- [App-V Planning Checklist](appv-planning-checklist.md)
|
||||
|
||||
|
||||
@ -54,11 +54,11 @@ Review the following for more information about configuring IIS and Network Load
|
||||
|
||||
## <a href="" id="bkmk-clusterscsmode"></a>Support for clustered file servers when running SCS mode
|
||||
|
||||
Running App-V Server in Share Content Store (SCS) mode with clustered file servers is supported.
|
||||
Running App-V Server in Shared Content Store (SCS) mode with clustered file servers is supported.
|
||||
|
||||
The following steps can be used to enable this configuration:
|
||||
|
||||
- Configure App-V to run in client SCS mode. For more information about configuring App-V SCS mode, see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).
|
||||
- Configure the App-V client to run in Shared Content Store mode. For more information, see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
|
||||
|
||||
- Configure the file server cluster, configured in either the scale out mode (which started with Windows Server 2012) or the earlier clustering mode, with a virtual SAN.
|
||||
|
||||
|
||||
@ -1,154 +1,4 @@
|
||||
---
|
||||
title: Planning for Migrating from a Previous Version of App-V (Windows 10)
|
||||
description: Planning for Migrating from a Previous Version of App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
redirect_url: https://technet.microsoft.com/itpro/windows/manage/appv-migrating-to-appv-from-a-previous-version
|
||||
---
|
||||
|
||||
|
||||
# Planning for Migrating from a Previous Version of App-V
|
||||
|
||||
|
||||
Use the following information to plan how to migrate to Microsoft Application Virtualization (App-V) from previous versions of App-V.
|
||||
|
||||
## Migration requirements
|
||||
|
||||
|
||||
Before you start any upgrades, review the following requirements:
|
||||
|
||||
- If you are upgrading from a version earlier than 4.6 SP2, upgrade to version 4.6 SP2 or version 4.6 SP3 first before upgrading to App-V or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
|
||||
|
||||
- App-V supports only packages that are created using App-V 5.0 or App-V, or packages that have been converted to the **.appv** format.
|
||||
|
||||
- If you are upgrading the App-V Server from App-V 5.0 SP1, see [About App-V](appv-about-appv.md#bkmk-migrate-to-51) for instructions.
|
||||
|
||||
## Running the App-V client concurrently with App-V 4.6 SP2 or later
|
||||
|
||||
|
||||
You can run the App-V client concurrently on the same computer with the App-V 4.6 SP2 client or App-V 4.6 SP3 client.
|
||||
|
||||
When you run coexisting App-V clients, you can:
|
||||
|
||||
- Convert an App-V 4.6 SP2 or 4.6 SP3 package to the App-V format and publish both packages, when you have both clients running.
|
||||
|
||||
- Define the migration policy for the converted package, which allows the converted App-V package to assume the file type associations and shortcuts from the App-V 4.6 SP2 package.
|
||||
|
||||
### Supported coexistence scenarios
|
||||
|
||||
The following table shows the supported App-V coexistence scenarios. We recommend that you install the latest available updates of a given release when you are running coexisting clients.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V 4.6.x client type</th>
|
||||
<th align="left">App-V client type</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>App-V</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP2 RDS</p></td>
|
||||
<td align="left"><p>App-V RDS</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>App-V</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3 RDS</p></td>
|
||||
<td align="left"><p>App-V RDS</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Requirements for running coexisting clients
|
||||
|
||||
To run coexisting clients, you must:
|
||||
|
||||
- Install the App-V 4.6 SP2 or App-V 4.6 SP3 client before you install the App-V client.
|
||||
|
||||
- Enable the **Enable Migration Mode** Group Policy setting, which is in the **App-V** > **Client Coexistence** node. To deploy the .admx template, see [How to Download and Deploy MDOP Group Policy (.admx) Templates](http://technet.microsoft.com/library/dn659707.aspx).
|
||||
|
||||
**Note**
|
||||
App-V packages can run side by side with App-V 4.X packages if you have coexisting installations of App-V and 4.X. However, App-V packages cannot interact with App-V 4.X packages in the same virtual environment.
|
||||
|
||||
|
||||
|
||||
### Client downloads and documentation
|
||||
|
||||
The following table provides links to the App-V 4.6.x client downloads and to the TechNet documentation about the releases. The downloads include the App-V “regular” and RDS clients. The TechNet documentation about the App-V client applies to both clients, unless stated otherwise.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V version</th>
|
||||
<th align="left">Link to download the client</th>
|
||||
<th align="left">Link to TechNet documentation</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 2](http://www.microsoft.com/download/details.aspx?id=35513)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP2](http://technet.microsoft.com/library/jj680847.aspx)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
For more information about how to configure App-V client coexistence, see:
|
||||
|
||||
- [App-V 5.0 Coexistence and Migration](http://technet.microsoft.com/windows/jj835811.aspx)
|
||||
|
||||
## <a href="" id="converting--previous-version--packages-using-the-package-converter-"></a>Converting “previous-version” packages using the package converter
|
||||
|
||||
|
||||
Before migrating a package, created using App- 4.6 SP2 or earlier, to App-V, review the following requirements:
|
||||
|
||||
- You must convert the package to the **.appv** file format.
|
||||
|
||||
- The Package Converter supports only the direct conversion of packages that were created by using App-V 4.5 and later. To use the package converter on a package that was created using a previous version, you must use an App-V 4.5 or later version of the sequencer to upgrade the package, and then you can perform the package conversion.
|
||||
|
||||
For more information about using the package converter to convert a package, see [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). After you convert the file, you can deploy it to target computers that run the App-V client.
|
||||
|
||||
## 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
|
||||
|
||||
|
||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -66,4 +66,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
- [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
|
||||
- [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
|
||||
- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning to Deploy App-V for Windows 0
|
||||
# Planning to Deploy App-V for Windows 10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
@ -55,7 +55,7 @@ Describes the planning considerations for the App-V Client and for the Sequencer
|
||||
|
||||
Describes the recommended path for migrating from previous versions of App-V, while ensuring that existing server configurations, packages and clients continue to work in your new App-V environment.
|
||||
|
||||
[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)
|
||||
[Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
|
||||
|
||||
## Planning for using App-V with Office
|
||||
|
||||
|
||||
@ -50,7 +50,7 @@ The following table indicates the software that is already installed for differe
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows Server 2012</p></td>
|
||||
<td align="left"><p>Windows Server 2016</p></td>
|
||||
<td align="left"><p>The following prerequisite software is already installed:</p>
|
||||
<ul>
|
||||
<li><p>Microsoft .NET Framework 4.5</p></li>
|
||||
|
||||
@ -13,10 +13,10 @@ ms.prod: w10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The following is a known issue in Application Virtualization (App-V) for Windows 10, version 1607:
|
||||
|
||||
**Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client**
|
||||
The following are known issues in Application Virtualization (App-V) for Windows 10, version 1607.
|
||||
|
||||
## Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client
|
||||
|
||||
MSI packages that were generated using an App-V sequencer from previous versions of App-V (App-V versions 5.1 and earlier) include a check to validate that the App-V client is installed on client devices before allowing the MSI package to install. Now that the App-V client is installed automatically when you upgrade user devices to Windows 10, version 1607, the pre-requisite check fails and causes the MSI to fail.
|
||||
|
||||
**Workaround**:
|
||||
@ -41,6 +41,123 @@ MSI packages that were generated using an App-V sequencer from previous versions
|
||||
|
||||
By default, the path to the Windows SDK installation will be:<br>**C:\Program Files (x86)\Windows Kits\10**
|
||||
|
||||
## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10
|
||||
|
||||
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.
|
||||
|
||||
**Workaround**: Upgrade the App-V 5.0 Management server to the App-V Management server for Windows 10 Clients.
|
||||
|
||||
## Custom configurations do not get applied for packages that will be published globally if they are set using the App-V Server
|
||||
|
||||
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.
|
||||
|
||||
**Workaround**: Do one of the following:
|
||||
|
||||
- Assign the package to groups containing only user accounts. This will ensure that the package’s custom configuration will be stored in each user’s profile and will be applied correctly.
|
||||
|
||||
- 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.
|
||||
|
||||
- Create a new package with the custom configuration using the App-V Sequencer.
|
||||
|
||||
## Server files not deleted after new App-V 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_<x>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
|
||||
**Workaround**: Use a different filename
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
@ -38,15 +38,15 @@ The following list displays the end–to-end high-level workflow for reporting i
|
||||
|
||||
|
||||
|
||||
4. After importing the App-V PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V client. This sample PowerShell cmdlet enables App-V reporting:
|
||||
4. After importing the App-V Windows PowerShell module using `Import-Module AppvClient` as administrator, enable App-V client reporting. This sample Windows PowerShell command enables App-V reporting:
|
||||
|
||||
``` syntax
|
||||
Set-AppvClientConfiguration –reportingserverurl <url>:<port> -reportingenabled 1 – ReportingStartTime <0-23> - ReportingRandomDelay <#min>
|
||||
Set-AppvClientConfiguration -ReportingServerURL <url>:<port> -ReportingEnabled 1 -ReportingStartTime <0-23> -ReportingRandomDelay <#min>
|
||||
```
|
||||
|
||||
To immediately send App-V report data, run `Send-AppvClientReport` on the App-V client.
|
||||
|
||||
For more information about installing the App-V client with reporting enabled see [About Client Configuration Settings](appv-client-configuration-settings.md). To administer App-V Reporting with Windows PowerShell, see [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 about configuring reporting on the App-V client, see [About Client Configuration Settings](appv-client-configuration-settings.md). To administer App-V Reporting with Windows PowerShell, see [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
|
||||
|
||||
5. After the reporting server receives the data from the App-V client it sends the data to the reporting database. When the database receives and processes the client data, a successful reply is sent to the reporting server and then a notification is sent to the App-V client.
|
||||
|
||||
@ -95,24 +95,24 @@ The following table displays answers to common questions about App-V reporting
|
||||
<ol>
|
||||
<li><p>Operating system, and App-V client information. ~150 Bytes, every time this data is sent.</p></li>
|
||||
<li><p>Published package list. ~7 KB for 30 packages. This is sent only when the package list is updated with a publishing refresh, which is done infrequently; if there is no change, this information is not sent.</p></li>
|
||||
<li><p>Virtual application usage information – about 0.25KB per event. Opening and closing count as one event if both occur before sending the information. When sending using a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the PowerShell cmdlet, there is an optional argument that controls if the data needs to be re-sent next time around – that argument is <strong>DeleteOnSuccess</strong>.</p>
|
||||
<li><p>Virtual application usage information – about 0.25KB per event. Opening and closing count as one event if both occur before sending the information. When sending using a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the Windows PowerShell cmdlet, there is an optional argument that controls if the data needs to be re-sent next time around – that argument is <strong>DeleteOnSuccess</strong>.</p>
|
||||
<p></p>
|
||||
<p>So for example, if twenty applications are opened and closed and reporting information is scheduled to be sent daily, the typical daily traffic should be about 0.15KB + 20 x 0.25KB, or about 5KB/user</p></li>
|
||||
</ol></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Can reporting be scheduled?</p></td>
|
||||
<td align="left"><p>Yes. Besides manually sending reporting using PowerShell Cmdlets (<strong>Send-AppvClientReport</strong>), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:</p>
|
||||
<td align="left"><p>Yes. Besides manually sending reporting using Windows PowerShell cmdlets (<strong>Send-AppvClientReport</strong>), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:</p>
|
||||
<ol>
|
||||
<li><p>Using PowerShell cmdlets - <strong>Set-AppvClientConfiguration</strong>. For example:</p>
|
||||
<p>Set-AppvClientConfiguration -ReportingEnabled 1 - ReportingServerURL http://any.com/appv-reporting</p>
|
||||
<li><p>Using Windows PowerShell cmdlets - <strong>Set-AppvClientConfiguration</strong>. For example:</p>
|
||||
<p>Set-AppvClientConfiguration -ReportingEnabled 1 -ReportingServerURL http://any.com/appv-reporting</p>
|
||||
<p></p>
|
||||
<p>For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md) and look for the following entries: <strong>ReportingEnabled</strong>, <strong>ReportingServerURL</strong>, <strong>ReportingDataCacheLimit</strong>, <strong>ReportingDataBlockSize</strong>, <strong>ReportingStartTime</strong>, <strong>ReportingRandomDelay</strong>, <strong>ReportingInterval</strong>.</p>
|
||||
<p></p></li>
|
||||
<li><p>By using Group Policy. If distributed using the domain controller, the settings are the same as previously listed.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Group Policy settings override local settings configured using PowerShell.</p>
|
||||
<p>Group Policy settings override local settings configured using Windows PowerShell.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -127,14 +127,14 @@ The following table displays answers to common questions about App-V reporting
|
||||
## <a href="" id="---------app-v-client-reporting"></a> App-V Client Reporting
|
||||
|
||||
|
||||
To use App-V reporting you must enable and configure the App-V client. After the client has been installed, use the **Set-AppVClientConfiguration** PowerShell cmdlet or the **ADMX Template** to configure reporting. The reporting feature cmdlets are available by using the following link and are prefaced by **Reporting**. For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of App-V client reporting configuration using PowerShell.
|
||||
To use App-V reporting you must enable and configure the App-V client. To configure reporting on the client, use the Windows PowerShell cmdlet **Set-AppVClientConfiguration**, or the Group Policy **ADMX Template**. For more information about the Windows PowerShell cmdlets, see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of Windows PowerShell commands for configuring App-V client reporting.
|
||||
|
||||
### Configuring App-V Client reporting using PowerShell
|
||||
### Configuring App-V Client reporting using Windows PowerShell
|
||||
|
||||
The following examples show how PowerShell parameters can configure the reporting features of the App-V client.
|
||||
The following examples show how Windows PowerShell parameters can configure the reporting features of the App-V client.
|
||||
|
||||
**Note**
|
||||
The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. For more information about using the ADMX template, see [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md).
|
||||
The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. The App-V settings are under **Computer Configuration > Administrative Templates > System > App-V**. For more information about using the ADMX template, see [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md).
|
||||
|
||||
|
||||
|
||||
@ -145,12 +145,10 @@ The following configuration task can also be configured using Group Policy setti
|
||||
**To configure the client to automatically send data to a specific reporting server**:
|
||||
|
||||
``` syntax
|
||||
Set-AppVClientConfiguration –ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30
|
||||
Set-AppVClientConfiguration -ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30
|
||||
```
|
||||
|
||||
`-ReportingInterval 1 -ReportingRandomDelay 30`
|
||||
|
||||
This example configures the client to automatically send the reporting data to the reporting server URL **http://MyReportingServer:MyPort/**. Additionally, the reporting data will be sent daily between 8:00 and 8:30 PM, depending on the random delay generated for the session.
|
||||
The preceding example configures the client to automatically send the reporting data to the reporting server URL **http://MyReportingServer:MyPort/**. Additionally, the reporting data will be sent daily between 8:00 and 8:30 PM, depending on the random delay generated for the session.
|
||||
|
||||
**To limit the size of the data cache on the client**:
|
||||
|
||||
@ -238,7 +236,7 @@ You can configure the computer that is running the App-V client to automatically
|
||||
|
||||
- ReportingRandomDelay
|
||||
|
||||
After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following PowerShell cmdlet:
|
||||
After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following Windows PowerShell cmdlet:
|
||||
|
||||
`Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess`
|
||||
|
||||
|
||||
@ -29,16 +29,16 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that wa
|
||||
|
||||
**Understand the security risks.** The most serious risk to App-V is that its functionality could be hijacked by an unauthorized user who could then reconfigure key data on App-V clients. The loss of App-V functionality for a short period of time due to a denial-of-service attack would not generally have a catastrophic impact.
|
||||
|
||||
**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V 5.1 server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V 5.1 servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver.
|
||||
**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver.
|
||||
|
||||
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, subscribe to the Security Notification service (<http://go.microsoft.com/fwlink/p/?LinkId=28819>).
|
||||
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, see the [Microsoft Security TechCenter](https://technet.microsoft.com/en-us/security/bb291012).
|
||||
|
||||
**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see the “Account Passwords and Policies” white paper on TechNet (<http://go.microsoft.com/fwlink/p/?LinkId=30009>).
|
||||
**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see [Password Policy](https://technet.microsoft.com/library/hh994572.aspx).
|
||||
|
||||
## Accounts and groups in App-V
|
||||
|
||||
|
||||
A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V local groups on the App-V 5.1 servers.
|
||||
A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V local groups on the App-V servers.
|
||||
|
||||
**Note**
|
||||
App-V client computer accounts that need to connect to the publishing server must be part of the publishing server’s **Users** local group. By default, all computers in the domain are part of the **Authorized Users** group, which is part of the **Users** local group.
|
||||
@ -47,7 +47,7 @@ App-V client computer accounts that need to connect to the publishing server mus
|
||||
|
||||
### <a href="" id="-------------app-v-5-1-server-security"></a> App-V server security
|
||||
|
||||
No groups are created automatically during App-V Setup. You should create the following Active Directory Domain Services global groups to manage App-V 5.1 server operations.
|
||||
No groups are created automatically during App-V Setup. You should create the following Active Directory Domain Services global groups to manage App-V server operations.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
|
||||
@ -53,11 +53,9 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!NOTE]
|
||||
> If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
|
||||
|
||||
|
||||
|
||||
If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then click **Next**.
|
||||
|
||||
|
||||
6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console.
|
||||
|
||||
Click **Next**.
|
||||
@ -66,8 +64,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring.
|
||||
|
||||
|
||||
|
||||
Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**.
|
||||
|
||||
8. On the **Installation** page, wait while the sequencer configures the virtualized application package.
|
||||
@ -76,8 +73,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!NOTE]
|
||||
> To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
|
||||
|
||||
|
||||
|
||||
Click **Next**.
|
||||
|
||||
10. On the **Installation Report** page, you can review information about the virtualized application package you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**.
|
||||
@ -109,9 +105,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in **Comments** and **Descriptions**.
|
||||
|
||||
|
||||
|
||||
|
||||
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
15. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory where the package was created.
|
||||
@ -148,7 +142,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
Click **Next**.
|
||||
|
||||
7. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V 5.0 Management Console.
|
||||
7. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V Management Console.
|
||||
|
||||
Click **Next**.
|
||||
|
||||
@ -179,9 +173,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in Comments and Descriptions.
|
||||
|
||||
|
||||
|
||||
|
||||
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
**To sequence a middleware application**
|
||||
@ -193,14 +185,14 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the App-V 5.0 Sequencer in order to ensure that no unwanted or malicious files can be added to the package.
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the App-V Sequencer in order to ensure that no unwanted or malicious files can be added to the package.
|
||||
|
||||
|
||||
4. On the **Type of Application** page, select **Middleware**, and then click **Next**.
|
||||
|
||||
5. On the **Select Installer** page, click **Browse** and specify the installation file for the application. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**.
|
||||
|
||||
6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V 5.0 Management Console.
|
||||
6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console.
|
||||
|
||||
Click **Next**.
|
||||
|
||||
@ -218,8 +210,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in Comments and Descriptions.
|
||||
|
||||
|
||||
|
||||
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
12. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure.
|
||||
|
||||
@ -25,7 +25,7 @@ The App-V server does not support the following scenarios:
|
||||
|
||||
- Deployment to a computer that runs the Server Core installation option.
|
||||
|
||||
- Deployment to a computer that runs a previous version of the App-V 5.1 server components. You can install App-V side by side with the App-V 4.5 Lightweight Streaming Server (LWS) server only. Deployment of App-V side by side with the Application Virtualization Management Service (HWS) 4.x is not supported.
|
||||
- Deployment to a computer that runs a previous version of the App-V server components. You can install App-V side by side with the App-V 4.5 Lightweight Streaming Server (LWS) server only. Deployment of App-V side by side with the Application Virtualization Management Service (HWS) 4.x is not supported.
|
||||
|
||||
- Deployment to a computer that runs Microsoft SQL Server Express edition.
|
||||
|
||||
@ -35,47 +35,7 @@ The App-V server does not support the following scenarios:
|
||||
|
||||
### Management server operating system requirements
|
||||
|
||||
The following table lists the operating systems that are supported for the App-V Management server installation.
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Operating system</th>
|
||||
<th align="left">Service Pack</th>
|
||||
<th align="left">System architecture</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2016</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2012 R2</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Microsoft Windows Server 2012</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2008 R2</p></td>
|
||||
<td align="left"><p>SP1</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
The App-V Management server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Deployment of the Management server role to a computer with Remote Desktop Services enabled is not supported.
|
||||
@ -130,46 +90,8 @@ The following table lists the SQL Server versions that are supported for the App
|
||||
|
||||
### Publishing server operating system requirements
|
||||
|
||||
The following table lists the operating systems that are supported for the App-V Publishing server installation.
|
||||
The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Operating system</th>
|
||||
<th align="left">Service Pack</th>
|
||||
<th align="left">System architecture</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2016</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2012 R2</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Microsoft Windows Server 2012</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2008 R2</p></td>
|
||||
<td align="left"><p>SP1</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Publishing server hardware requirements
|
||||
|
||||
@ -183,46 +105,7 @@ App-V adds no additional requirements beyond those of Windows Server.
|
||||
|
||||
### Reporting server operating system requirements
|
||||
|
||||
The following table lists the operating systems that are supported for the App-V Reporting server installation.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Operating system</th>
|
||||
<th align="left">Service Pack</th>
|
||||
<th align="left">System architecture</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2016</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2012 R2</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Microsoft Windows Server 2012</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2008 R2</p></td>
|
||||
<td align="left"><p>SP1</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
The App-V Reporting server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
|
||||
|
||||
### Reporting server hardware requirements
|
||||
|
||||
|
||||
@ -175,7 +175,7 @@ If you only want to remove some of the default pinned apps, you would use this m
|
||||
|
||||
## Configure taskbar by country or region
|
||||
|
||||
The following example shows you how to configure taskbars by country or region. When you specify one or more country or region in `<taskbar:TaskbarPinList>`, the pinned apps in that section are only pinned on computers that are configured for that country or region. When specifying taskbar configuration by country or region, the taskbar will concatenate pinlists together so long as the target computer meets the country or region requirements. If no country or region is specified for a `<TaskbarPinList>` node, it will apply to every country and region, only if the country or region has not been defined prior. Unspecified country or region in `<taskbar:TaskbarPinList>` will not merge with a `<taskbar:TaskbarPinList>` that has country or region specified.
|
||||
The following example shows you how to configure taskbars by country or region. When the layout is applied to a computer, if there is no `<TaskbarPinList>` node with a region tag for the current region, the first `<TaskbarPinList>` node that has no specified region will be applied. When you specify one or more countries or regions in a `<TaskbarPinList>` node, the specified apps are pinned on computers configured for any of the specified countries or regions.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
@ -7,8 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, servicing
|
||||
author: greg-lindsay
|
||||
localizationpriority: high
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Windows 10 servicing options
|
||||
|
||||
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.sitesec: library
|
||||
ms.pagetype: servicing, devices
|
||||
author: TrudyHa
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Integration with management solutions
|
||||
|
||||
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.sitesec: library
|
||||
ms.pagetype: servicing, devices
|
||||
author: TrudyHa
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Setup and deployment
|
||||
|
||||
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
ms.pagetype: servicing
|
||||
ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Windows 10 servicing overview
|
||||
|
||||
@ -8,7 +8,6 @@ ms.mktglfcycl: plan
|
||||
ms.sitesec: library
|
||||
ms.pagetype: servicing; devices
|
||||
author: jdeckerMS
|
||||
localizationpriority: high
|
||||
---
|
||||
|
||||
# Windows Update for Business
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user