diff --git a/devices/surface-hub/first-run-program-surface-hub.md b/devices/surface-hub/first-run-program-surface-hub.md index 8305a2bd53..b34943faf8 100644 --- a/devices/surface-hub/first-run-program-surface-hub.md +++ b/devices/surface-hub/first-run-program-surface-hub.md @@ -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. diff --git a/devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md b/devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md index 45d66f1d0a..3f17756233 100644 --- a/devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md +++ b/devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md @@ -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 diff --git a/devices/surface-hub/intro-to-surface-hub.md b/devices/surface-hub/intro-to-surface-hub.md index d8a4c1c1e2..ec1712c7a0 100644 --- a/devices/surface-hub/intro-to-surface-hub.md +++ b/devices/surface-hub/intro-to-surface-hub.md @@ -44,10 +44,6 @@ The capabilities of your Surface Hub will depend on what other Microsoft product

Web browsing through Microsoft Edge

Internet connectivity.

- -

Cortana meeting room assistant (voice commands, search)

-

Internet connectivity needed to process questions and do searches.

-

Remote and multi-device management

Supported mobile device management (MDM) solutions (Microsoft Intune, System Center 2012 R2 Configuration Manager, or supported third-party solution).

diff --git a/windows/keep-secure/enable-pua-windows-defender-for-windows-10.md b/windows/keep-secure/enable-pua-windows-defender-for-windows-10.md index 113656af14..b2d0ca16e4 100644 --- a/windows/keep-secure/enable-pua-windows-defender-for-windows-10.md +++ b/windows/keep-secure/enable-pua-windows-defender-for-windows-10.md @@ -49,13 +49,13 @@ System Center 2012 R2 Endpoint Protection
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
+1. Open PowerShell as Administrator:
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:
+ + 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 diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index e49b9df2ec..b439a02e08 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -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) diff --git a/windows/manage/application-development-for-windows-as-a-service.md b/windows/manage/application-development-for-windows-as-a-service.md index dedc91d3cd..d890f1f880 100644 --- a/windows/manage/application-development-for-windows-as-a-service.md +++ b/windows/manage/application-development-for-windows-as-a-service.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 diff --git a/windows/manage/appv-about-appv.md b/windows/manage/appv-about-appv.md index 5c6ea7dcf4..24e04a16d6 100644 --- a/windows/manage/appv-about-appv.md +++ b/windows/manage/appv-about-appv.md @@ -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**
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. - - -### 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. - - ---- - - - - - - - - - - - - - - - - - - - - -
StepFor more information

Step 1: Upgrade the App-V server components.

-
-Note   -

If you are not using the App-V server, skip this step and go to the next step.

-
-
-  -

Follow these steps:

-
    -

  1. Do one of the following, depending on the method you are using to upgrade the management database and/or reporting database:

    - ---- - - - - - - - - - - - - - - - - -
    Database upgrade methodStep

    Windows Installer

    Skip this step and go to step 2, “If you are upgrading the App-V server...”

    SQL scripts

    Follow the steps in [How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md).

    -

  2. 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).

    3. -

  3. Follow the steps in [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)

    4. -

     

    -

Step 2: Install the new App-V for Windows sequencer.

See [How to Install the Sequencer](appv-install-the-sequencer.md).

Step 3: Enable the in-box App-V client.

See [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).

- -  - -### 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. - -  - -## 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). - - -### 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 - - ---- - - - - - - - - - - - - - - - - - - - - -
New in App-V for WindowsPrior to App-V for Windows

Number of messages indicator:

-

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.

You could see only one message or error at a time, and you were unable to determine how many messages there were.

Message appearance:

-
    -

  • 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.

    • -

  • Messages and errors appear in a list, with one beneath the other.

    • -

You could see only one message or error at a time.

Dismissing messages:

-

Use the Dismiss All link to dismiss all messages and errors at one time, or dismiss them one at a time.

You could dismiss messages and errors only one at a time.

- -  - -### Console pages are now separate URLs - - ---- - - - - - - - - - - - - -
New in App-V for WindowsPrior to App-V for Windows

Each page in the console has a different URL, which enables you to bookmark specific pages for quick access in the future.

-

The number that appears in some URLs indicates the specific package. These numbers are unique.

All console pages are accessed through the same URL.

- -  - -### New, separate CONNECTION GROUPS page and menu option - - ---- - - - - - - - - - - - - -
New in App-V for WindowsPrior to App-V for Windows

The CONNECTION GROUPS page is now part of the main menu, at the same level as the PACKAGES page.

To open the CONNECTION GROUPS page, you navigate through the PACKAGES page.

- -  - -### Menu options for packages have changed - - ---- - - - - - - - - - - - - - - - - -
New in App-V for WindowsPrior to App-V Windows

The following options are now buttons that appear at the bottom of the PACKAGES page:

-
    -

  • Add or Upgrade

    • -

  • Publish

    • -

  • Unpublish

    • -

  • Delete

    • -
-

The following options will still appear when you right-click a package to open the drop-down context menu:

-
    -

  • Publish

    • -

  • Unpublish

    • -

  • Edit AD Access

    • -

  • Edit Deployment Config

    • -

  • Transfer deployment configuration from…

    • -

  • Transfer access and configuration from…

    • -

  • Delete

    • -
-

When you click Delete to remove a package, a dialog box opens and asks you to confirm that you want to delete the package.

The Add or Upgrade option was a button at the top right of the PACKAGES page.

-

The Publish, Unpublish, and Delete options were available only if you right-clicked a package name in the packages list.

The following package operations are now buttons on the package details page for each package:

-
    -

  • Transfer (drop-down menu with the following options):

    -
      -

    • Transfer deployment configuration from…

      • -

    • Transfer access and configuration from…

      • -
    • -

  • Edit (connection groups and AD Access)

    • -

  • Unpublish

    • -

  • Delete

    • -

  • Edit Default Configuration

    • -

These package options were available only if you right-clicked a package name in the packages list.

- -  - -### 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. - -### 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. - -#### 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. - -### 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). - -#### 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 diff --git a/windows/manage/appv-application-publishing-and-client-interaction.md b/windows/manage/appv-application-publishing-and-client-interaction.md index d9e5931749..fdec3fdd21 100644 --- a/windows/manage/appv-application-publishing-and-client-interaction.md +++ b/windows/manage/appv-application-publishing-and-client-interaction.md @@ -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 diff --git a/windows/manage/appv-capacity-planning.md b/windows/manage/appv-capacity-planning.md index 3388a0522a..0c1453422f 100644 --- a/windows/manage/appv-capacity-planning.md +++ b/windows/manage/appv-capacity-planning.md @@ -47,23 +47,15 @@ Before you design the App-V infrastructure, determine the project’s scope. The -  - ## 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. diff --git a/windows/manage/appv-client-configuration-settings.md b/windows/manage/appv-client-configuration-settings.md index 93b6745d4e..6dfed6b51b 100644 --- a/windows/manage/appv-client-configuration-settings.md +++ b/windows/manage/appv-client-configuration-settings.md @@ -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) diff --git a/windows/manage/appv-deploy-the-appv-server-with-a-script.md b/windows/manage/appv-deploy-the-appv-server-with-a-script.md index 1394472c33..0821433da2 100644 --- a/windows/manage/appv-deploy-the-appv-server-with-a-script.md +++ b/windows/manage/appv-deploy-the-appv-server-with-a-script.md @@ -11,768 +11,727 @@ ms.prod: w10 # How to Deploy the App-V Server Using a Script - In order to complete the **appv\_server\_setup.exe** Server setup successfully using the command line, you must specify and combine multiple parameters. **To Install the App-V server using a script** -- Use the following tables for more information about installing the App-V server using the command line. +Use the following tables for more information about installing the App-V server using the command line. **Note**   - The information in the following tables can also be accessed using the command line by typing the following command: **appv\_server\_setup.exe /?**. +The information in the following tables can also be accessed using the command line by typing the following command: **appv\_server\_setup.exe /?**. -   +**Common parameters and Examples** - **Common parameters and Examples** + ++++ + + + + + + +

To Install the Management server and Management database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /MANAGEMENT_SERVER

    • +

  • /MANAGEMENT_ADMINACCOUNT

    • +

  • /MANAGEMENT_WEBSITE_NAME

    • +

  • /MANAGEMENT_WEBSITE_PORT

    • +

  • /DB_PREDEPLOY_MANAGEMENT

    • +

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /MANAGEMENT_DB_NAME

    • +
+

To use a custom instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /MANAGEMENT_SERVER

    • +

  • /MANAGEMENT_ADMINACCOUNT

    • +

  • /MANAGEMENT_WEBSITE_NAME

    • +

  • /MANAGEMENT_WEBSITE_PORT

    • +

  • /DB_PREDEPLOY_MANAGEMENT

    • +

  • /MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • +

  • /MANAGEMENT_DB_NAME

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/MANAGEMENT_SERVER

+

/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”

+

/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”

+

/MANAGEMENT_WEBSITE_PORT=”8080”

+

/DB_PREDEPLOY_MANAGEMENT

+

/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

+

/MANAGEMENT_DB_NAME=”AppVManagement”

- - - - - - - - - - - -

To Install the Management server and Management database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /MANAGEMENT_DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • -

  • /MANAGEMENT_DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/MANAGEMENT_SERVER

-

/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”

-

/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”

-

/MANAGEMENT_WEBSITE_PORT=”8080”

-

/DB_PREDEPLOY_MANAGEMENT

-

/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/MANAGEMENT_DB_NAME=”AppVManagement”

+ ++++ + + + + + + +

To Install the Management server using an existing Management database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /MANAGEMENT_SERVER

    • +

  • /MANAGEMENT_ADMINACCOUNT

    • +

  • /MANAGEMENT_WEBSITE_NAME

    • +

  • /MANAGEMENT_WEBSITE_PORT

    • +

  • /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

    • +

  • /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /EXISTING_MANAGEMENT_DB_NAME

    • +
+

To use a custom instance of Microsoft SQL Server, use these parameters:

+
    +

  • /MANAGEMENT_SERVER

    • +

  • /MANAGEMENT_ADMINACCOUNT

    • +

  • /MANAGEMENT_WEBSITE_NAME

    • +

  • /MANAGEMENT_WEBSITE_PORT

    • +

  • /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

    • +

  • /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • +

  • /EXISTING_MANAGEMENT_DB_NAME

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/MANAGEMENT_SERVER

+

/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”

+

/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”

+

/MANAGEMENT_WEBSITE_PORT=”8080”

+

/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

+

/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName”

+

/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement”

-   + ++++ + + + + + + +

To install the Management server using an existing Management database on a remote machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /MANAGEMENT_SERVER

    • +

  • /MANAGEMENT_ADMINACCOUNT

    • +

  • /MANAGEMENT_WEBSITE_NAME

    • +

  • /MANAGEMENT_WEBSITE_PORT

    • +

  • /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME

    • +

  • /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /EXISTING_MANAGEMENT_DB_NAME

    • +
+

To use a custom instance of Microsoft SQL Server, use these parameters:

+
    +

  • /MANAGEMENT_SERVER

    • +

  • /MANAGEMENT_ADMINACCOUNT

    • +

  • /MANAGEMENT_WEBSITE_NAME

    • +

  • /MANAGEMENT_WEBSITE_PORT

    • +

  • /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME

    • +

  • /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • +

  • /EXISTING_MANAGEMENT_DB_NAME

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/MANAGEMENT_SERVER

+

/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”

+

/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”

+

/MANAGEMENT_WEBSITE_PORT=”8080”

+

/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME=”SqlServermachine.domainName”

+

/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName”

+

/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement”

- - - - - - - - - - - -

To Install the Management server using an existing Management database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

    • -

  • /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /EXISTING_MANAGEMENT_DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

    • -

  • /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • -

  • /EXISTING_MANAGEMENT_DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/MANAGEMENT_SERVER

-

/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”

-

/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”

-

/MANAGEMENT_WEBSITE_PORT=”8080”

-

/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

-

/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName”

-

/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement”

+ ++++ + + + + + + +

To Install the Management database and the Management Server on the same computer.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /DB_PREDEPLOY_MANAGEMENT

    • +

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /MANAGEMENT_DB_NAME

    • +

  • /MANAGEMENT_SERVER_MACHINE_USE_LOCAL

    • +

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • +
+

To use a custom instance of Microsoft SQL Server, use these parameters:

+
    +

  • /DB_PREDEPLOY_MANAGEMENT

    • +

  • /MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • +

  • /MANAGEMENT_DB_NAME

    • +

  • /MANAGEMENT_SERVER_MACHINE_USE_LOCAL

    • +

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/DB_PREDEPLOY_MANAGEMENT

+

/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

+

/MANAGEMENT_DB_NAME=”AppVManagement”

+

/MANAGEMENT_SERVER_MACHINE_USE_LOCAL

+

/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

  -   + ++++ + + + + + + +

To install the Management database on a different computer than the Management server.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /DB_PREDEPLOY_MANAGEMENT

    • +

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /MANAGEMENT_DB_NAME

    • +

  • /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT

    • +

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • +
+

To use a custom instance of Microsoft SQL Server, use these parameters:

+
    +

  • /DB_PREDEPLOY_MANAGEMENT

    • +

  • /MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • +

  • /MANAGEMENT_DB_NAME

    • +

  • /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT

    • +

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/DB_PREDEPLOY_MANAGEMENT

+

/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

+

/MANAGEMENT_DB_NAME=”AppVManagement”

+

/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount”

+

/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

- - - - - - - - - - - -

To install the Management server using an existing Management database on a remote machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME

    • -

  • /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /EXISTING_MANAGEMENT_DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME

    • -

  • /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • -

  • /EXISTING_MANAGEMENT_DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/MANAGEMENT_SERVER

-

/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”

-

/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”

-

/MANAGEMENT_WEBSITE_PORT=”8080”

-

/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME=”SqlServermachine.domainName”

-

/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName”

-

/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement”

+ ++++ + + + + + + +

To Install the publishing server.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /PUBLISHING_SERVER

    • +

  • /PUBLISHING_MGT_SERVER

    • +

  • /PUBLISHING_WEBSITE_NAME

    • +

  • /PUBLISHING_WEBSITE_PORT

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/PUBLISHING_SERVER

+

/PUBLISHING_MGT_SERVER=”http://ManagementServerName:ManagementPort”

+

/PUBLISHING_WEBSITE_NAME=”Microsoft AppV Publishing Service”

+

/PUBLISHING_WEBSITE_PORT=”8081”

-   + ++++ + + + + + + +

To Install the Reporting server and Reporting database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /REPORTING _SERVER

    • +

  • /REPORTING _WEBSITE_NAME

    • +

  • /REPORTING _WEBSITE_PORT

    • +

  • /DB_PREDEPLOY_REPORTING

    • +

  • /REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /REPORTING _DB_NAME

    • +
+

To use a custom instance of Microsoft SQL Server, use these parameters:

+
    +

  • /REPORTING _SERVER

    • +

  • /REPORTING _ADMINACCOUNT

    • +

  • /REPORTING _WEBSITE_NAME

    • +

  • /REPORTING _WEBSITE_PORT

    • +

  • /DB_PREDEPLOY_REPORTING

    • +

  • /REPORTING _DB_CUSTOM_SQLINSTANCE

    • +

  • /REPORTING _DB_NAME

    • +
+

Using a custom instance of Microsoft SQL Server example:

+
    +

  • /appv_server_setup.exe /QUIET

    • +

  • /REPORTING_SERVER

    • +

  • /REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”

    • +

  • /REPORTING_WEBSITE_PORT=”8082”

    • +

  • /DB_PREDEPLOY_REPORTING

    • +

  • /REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

    • +

  • /REPORTING_DB_NAME=”AppVReporting”

    • +
- - - - - - - - - - - -

To Install the Management database and the Management Server on the same computer.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /MANAGEMENT_DB_NAME

    • -

  • /MANAGEMENT_SERVER_MACHINE_USE_LOCAL

    • -

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • -

  • /MANAGEMENT_DB_NAME

    • -

  • /MANAGEMENT_SERVER_MACHINE_USE_LOCAL

    • -

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/DB_PREDEPLOY_MANAGEMENT

-

/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/MANAGEMENT_DB_NAME=”AppVManagement”

-

/MANAGEMENT_SERVER_MACHINE_USE_LOCAL

-

/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

+ ++++ + + + + + + +

To Install the Reporting server and using an existing Reporting database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /REPORTING _SERVER

    • +

  • /REPORTING _WEBSITE_NAME

    • +

  • /REPORTING _WEBSITE_PORT

    • +

  • /EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

    • +

  • /EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /EXISTING_REPORTING _DB_NAME

    • +
+

To use a custom instance of Microsoft SQL Server, use these parameters:

+
    +

  • /REPORTING _SERVER

    • +

  • /REPORTING _ADMINACCOUNT

    • +

  • /REPORTING _WEBSITE_NAME

    • +

  • /REPORTING _WEBSITE_PORT

    • +

  • /EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

    • +

  • /EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE

    • +

  • /EXISTING_REPORTING _DB_NAME

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/REPORTING_SERVER

+

/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”

+

/REPORTING_WEBSITE_PORT=”8082”

+

/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

+

/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

+

/EXITING_REPORTING_DB_NAME=”AppVReporting”

  -   + ++++ + + + + + + +

To Install the Reporting server using an existing Reporting database on a remote machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /REPORTING _SERVER

    • +

  • /REPORTING _WEBSITE_NAME

    • +

  • /REPORTING _WEBSITE_PORT

    • +

  • /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME

    • +

  • /EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /EXISTING_REPORTING _DB_NAME

    • +
+

To use a custom instance of Microsoft SQL Server, use these parameters:

+
    +

  • /REPORTING _SERVER

    • +

  • /REPORTING _ADMINACCOUNT

    • +

  • /REPORTING _WEBSITE_NAME

    • +

  • /REPORTING _WEBSITE_PORT

    • +

  • /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME

    • +

  • /EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE

    • +

  • /EXISTING_REPORTING _DB_NAME

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/REPORTING_SERVER

+

/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”

+

/REPORTING_WEBSITE_PORT=”8082”

+

/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME=”SqlServerMachine.DomainName”

+

/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

+

/EXITING_REPORTING_DB_NAME=”AppVReporting”

- - - - - - - - - - - -

To install the Management database on a different computer than the Management server.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /MANAGEMENT_DB_NAME

    • -

  • /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT

    • -

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • -

  • /MANAGEMENT_DB_NAME

    • -

  • /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT

    • -

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/DB_PREDEPLOY_MANAGEMENT

-

/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/MANAGEMENT_DB_NAME=”AppVManagement”

-

/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount”

-

/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

+ ++++ + + + + + + +

To install the Reporting database on the same computer as the Reporting server.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /DB_PREDEPLOY_REPORTING

    • +

  • /REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /REPORTING _DB_NAME

    • +

  • /REPORTING_SERVER_MACHINE_USE_LOCAL

    • +

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • +
+

To use a custom instance of Microsoft SQL Server, use these parameters:

+
    +

  • /DB_PREDEPLOY_REPORTING

    • +

  • /REPORTING _DB_CUSTOM_SQLINSTANCE

    • +

  • /REPORTING _DB_NAME

    • +

  • /REPORTING_SERVER_MACHINE_USE_LOCAL

    • +

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/DB_PREDEPLOY_REPORTING

+

/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

+

/REPORTING_DB_NAME=”AppVReporting”

+

/REPORTING_SERVER_MACHINE_USE_LOCAL

+

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

-   + ++++ + + + + + + +

To install the Reporting database on a different computer than the Reporting server.

To use the default instance of Microsoft SQL Server, use the following parameters:

+
    +

  • /DB_PREDEPLOY_REPORTING

    • +

  • /REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • +

  • /REPORTING _DB_NAME

    • +

  • /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT

    • +

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • +
+

To use a custom instance of Microsoft SQL Server, use these parameters:

+
    +

  • /DB_PREDEPLOY_REPORTING

    • +

  • /REPORTING _DB_CUSTOM_SQLINSTANCE

    • +

  • /REPORTING _DB_NAME

    • +

  • /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT

    • +

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • +
+

Using a custom instance of Microsoft SQL Server example:

+

/appv_server_setup.exe /QUIET

+

/DB_PREDEPLOY_REPORTING

+

/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

+

/REPORTING_DB_NAME=”AppVReporting”

+

/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount”

+

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

- - - - - - - - - - - -

To Install the publishing server.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /PUBLISHING_SERVER

    • -

  • /PUBLISHING_MGT_SERVER

    • -

  • /PUBLISHING_WEBSITE_NAME

    • -

  • /PUBLISHING_WEBSITE_PORT

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/PUBLISHING_SERVER

-

/PUBLISHING_MGT_SERVER=”http://ManagementServerName:ManagementPort”

-

/PUBLISHING_WEBSITE_NAME=”Microsoft AppV Publishing Service”

-

/PUBLISHING_WEBSITE_PORT=”8081”

+**Parameter Definitions** -   +**General Parameters** - - - - - - - - - - - -

To Install the Reporting server and Reporting database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /REPORTING _DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _ADMINACCOUNT

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_CUSTOM_SQLINSTANCE

    • -

  • /REPORTING _DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-
    -

  • /appv_server_setup.exe /QUIET

    • -

  • /REPORTING_SERVER

    • -

  • /REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”

    • -

  • /REPORTING_WEBSITE_PORT=”8082”

    • -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

    • -

  • /REPORTING_DB_NAME=”AppVReporting”

    • -
+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/QUIET

Specifies silent install.

/UNINSTALL

Specifies an uninstall.

/LAYOUT

Specifies layout action. This extracts the MSIs and script files to a folder without actually installing the product. No value is expected.

/LAYOUTDIR

Specifies the layout directory. Takes a string. For example, /LAYOUTDIR=”C:\Application Virtualization Server”

/INSTALLDIR

Specifies the installation directory. Takes a string. E.g. /INSTALLDIR=”C:\Program Files\Application Virtualization\Server”

/MUOPTIN

Enables Microsoft Update. No value is expected

/ACCEPTEULA

Accepts the license agreement. This is required for an unattended installation. Example usage: /ACCEPTEULA or /ACCEPTEULA=1.

-   +**Management Server Installation Parameters** - - - - - - - - - - - -

To Install the Reporting server and using an existing Reporting database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

    • -

  • /EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /EXISTING_REPORTING _DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _ADMINACCOUNT

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

    • -

  • /EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE

    • -

  • /EXISTING_REPORTING _DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/REPORTING_SERVER

-

/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”

-

/REPORTING_WEBSITE_PORT=”8082”

-

/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

-

/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/EXITING_REPORTING_DB_NAME=”AppVReporting”

+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/MANAGEMENT_SERVER

Specifies that the management server will be installed. No value is expected

/MANAGEMENT_ADMINACCOUNT

Specifies the account that will be allowed to Administrator access to the management server This account can be an individual user account or a group. Example usage: /MANAGEMENT_ADMINACCOUNT=”mydomain\admin”. If /MANAGEMENT_SERVER is not specified, this will be ignored. Specifies the account that will be allowed to Administrator access to the management server. This can be a user account or a group. For example, /MANAGEMENT_ADMINACCOUNT="mydomain\admin".

/MANAGEMENT_WEBSITE_NAME

Specifies name of the website that will be created for the management service. For example, /MANAGEMENT_WEBSITE_NAME=”Microsoft App-V Management Service”

MANAGEMENT_WEBSITE_PORT

Specifies the port number that will be used by the management service will use. For example, /MANAGEMENT_WEBSITE_PORT=82.

-   +**Parameters for the Management Server Database** - - - - - - - - - - - -

To Install the Reporting server using an existing Reporting database on a remote machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME

    • -

  • /EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /EXISTING_REPORTING _DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _ADMINACCOUNT

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME

    • -

  • /EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE

    • -

  • /EXISTING_REPORTING _DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/REPORTING_SERVER

-

/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”

-

/REPORTING_WEBSITE_PORT=”8082”

-

/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME=”SqlServerMachine.DomainName”

-

/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/EXITING_REPORTING_DB_NAME=”AppVReporting”

+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/DB_PREDEPLOY_MANAGEMENT

Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected

/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

Indicates that the default SQL instance should be used. No value is expected.

/MANAGEMENT_DB_ CUSTOM_SQLINSTANCE

Specifies the name of the custom SQL instance that should be used to create a new database. Example usage: /MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”MYSQLSERVER”. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored.

/MANAGEMENT_DB_NAME

Specifies the name of the new management database that should be created. Example usage: /MANAGEMENT_DB_NAME=”AppVMgmtDB”. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored.

/MANAGEMENT_SERVER_MACHINE_USE_LOCAL

Indicates if the management server that will be accessing the database is installed on the local server. Switch parameter so no value is expected.

/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT

Specifies the machine account of the remote machine that the management server will be installed on. Example usage: /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”domain\computername”

/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

Indicates the Administrator account that will be used to install the management server. Example usage: /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT =”domain\alias”

-   +**Parameters for Installing Publishing Server** - - - - - - - - - - - -

To install the Reporting database on the same computer as the Reporting server.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /REPORTING _DB_NAME

    • -

  • /REPORTING_SERVER_MACHINE_USE_LOCAL

    • -

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_CUSTOM_SQLINSTANCE

    • -

  • /REPORTING _DB_NAME

    • -

  • /REPORTING_SERVER_MACHINE_USE_LOCAL

    • -

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/DB_PREDEPLOY_REPORTING

-

/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/REPORTING_DB_NAME=”AppVReporting”

-

/REPORTING_SERVER_MACHINE_USE_LOCAL

-

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/PUBLISHING_SERVER

Specifies that the Publishing Server will be installed. No value is expected

/PUBLISHING_MGT_SERVER

Specifies the URL to Management Service the Publishing server will connect to. Example usage: http://<management server name>:<Management server port number>. If /PUBLISHING_SERVER is not used, this parameter will be ignored

/PUBLISHING_WEBSITE_NAME

Specifies name of the website that will be created for the publishing service. For example, /PUBLISHING_WEBSITE_NAME=”Microsoft App-V Publishing Service”

/PUBLISHING_WEBSITE_PORT

Specifies the port number used by the publishing service. For example, /PUBLISHING_WEBSITE_PORT=83

-   +**Parameters for Reporting Server** - - - - - - - - - - - -

To install the Reporting database on a different computer than the Reporting server.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /REPORTING _DB_NAME

    • -

  • /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT

    • -

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_CUSTOM_SQLINSTANCE

    • -

  • /REPORTING _DB_NAME

    • -

  • /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT

    • -

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/DB_PREDEPLOY_REPORTING

-

/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/REPORTING_DB_NAME=”AppVReporting”

-

/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount”

-

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

+ ++++ + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/REPORTING_SERVER

Specifies that the Reporting Server will be installed. No value is expected

/REPORTING_WEBSITE_NAME

Specifies name of the website that will be created for the Reporting Service. E.g. /REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService"

/REPORTING_WEBSITE_PORT

Specifies the port number that the Reporting Service will use. E.g. /REPORTING_WEBSITE_PORT=82

  -   +**Parameters for using an Existing Reporting Server Database** - **Parameter Definitions** + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

Indicates that the Microsoft SQL Server is installed on the local server. Switch parameter so no value is expected.

/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME

Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_REPORTING_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1"

/EXISTING_ REPORTING _DB_SQLINSTANCE_USE_DEFAULT

Indicates that the default SQL instance is to be used. Switch parameter so no value is expected.

/EXISTING_ REPORTING_DB_CUSTOM_SQLINSTANCE

Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /EXISTING_REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER"

/EXISTING_ REPORTING _DB_NAME

Specifies the name of the existing Reporting database that should be used. Takes a string. E.g. /EXISITING_REPORTING_DB_NAME="AppVReporting"

  - **General Parameters** +**Parameters for installing Reporting Server Database** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/QUIET

Specifies silent install.

/UNINSTALL

Specifies an uninstall.

/LAYOUT

Specifies layout action. This extracts the MSIs and script files to a folder without actually installing the product. No value is expected.

/LAYOUTDIR

Specifies the layout directory. Takes a string. For example, /LAYOUTDIR=”C:\Application Virtualization Server”

/INSTALLDIR

Specifies the installation directory. Takes a string. E.g. /INSTALLDIR=”C:\Program Files\Application Virtualization\Server”

/MUOPTIN

Enables Microsoft Update. No value is expected

/ACCEPTEULA

Accepts the license agreement. This is required for an unattended installation. Example usage: /ACCEPTEULA or /ACCEPTEULA=1.

+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/DB_PREDEPLOY_REPORTING

Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected

/REPORTING_DB_SQLINSTANCE_USE_DEFAULT

Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER"

/REPORTING_DB_NAME

Specifies the name of the new Reporting database that should be created. Takes a string. E.g. /REPORTING_DB_NAME="AppVMgmtDB"

/REPORTING_SERVER_MACHINE_USE_LOCAL

Indicates that the Reporting server that will be accessing the database is installed on the local server. Switch parameter so no value is expected.

/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT

Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. E.g. /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername"

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. E.g. /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias"

-   +**Parameters for using an existing Management Server Database** - **Management Server Installation Parameters** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/MANAGEMENT_SERVER

Specifies that the management server will be installed. No value is expected

/MANAGEMENT_ADMINACCOUNT

Specifies the account that will be allowed to Administrator access to the management server This account can be an individual user account or a group. Example usage: /MANAGEMENT_ADMINACCOUNT=”mydomain\admin”. If /MANAGEMENT_SERVER is not specified, this will be ignored. Specifies the account that will be allowed to Administrator access to the management server. This can be a user account or a group. For example, /MANAGEMENT_ADMINACCOUNT="mydomain\admin".

/MANAGEMENT_WEBSITE_NAME

Specifies name of the website that will be created for the management service. For example, /MANAGEMENT_WEBSITE_NAME=”Microsoft App-V Management Service”

MANAGEMENT_WEBSITE_PORT

Specifies the port number that will be used by the management service will use. For example, /MANAGEMENT_WEBSITE_PORT=82.

- -   - - **Parameters for the Management Server Database** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/DB_PREDEPLOY_MANAGEMENT

Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected

/MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

Indicates that the default SQL instance should be used. No value is expected.

/MANAGEMENT_DB_ CUSTOM_SQLINSTANCE

Specifies the name of the custom SQL instance that should be used to create a new database. Example usage: /MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”MYSQLSERVER”. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored.

/MANAGEMENT_DB_NAME

Specifies the name of the new management database that should be created. Example usage: /MANAGEMENT_DB_NAME=”AppVMgmtDB”. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored.

/MANAGEMENT_SERVER_MACHINE_USE_LOCAL

Indicates if the management server that will be accessing the database is installed on the local server. Switch parameter so no value is expected.

/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT

Specifies the machine account of the remote machine that the management server will be installed on. Example usage: /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”domain\computername”

/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

Indicates the Administrator account that will be used to install the management server. Example usage: /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT =”domain\alias”

- -   - - **Parameters for Installing Publishing Server** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/PUBLISHING_SERVER

Specifies that the Publishing Server will be installed. No value is expected

/PUBLISHING_MGT_SERVER

Specifies the URL to Management Service the Publishing server will connect to. Example usage: http://<management server name>:<Management server port number>. If /PUBLISHING_SERVER is not used, this parameter will be ignored

/PUBLISHING_WEBSITE_NAME

Specifies name of the website that will be created for the publishing service. For example, /PUBLISHING_WEBSITE_NAME=”Microsoft App-V Publishing Service”

/PUBLISHING_WEBSITE_PORT

Specifies the port number used by the publishing service. For example, /PUBLISHING_WEBSITE_PORT=83

- -   - - **Parameters for Reporting Server** - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/REPORTING_SERVER

Specifies that the Reporting Server will be installed. No value is expected

/REPORTING_WEBSITE_NAME

Specifies name of the website that will be created for the Reporting Service. E.g. /REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService"

/REPORTING_WEBSITE_PORT

Specifies the port number that the Reporting Service will use. E.g. /REPORTING_WEBSITE_PORT=82

- -   - - **Parameters for using an Existing Reporting Server Database** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

Indicates that the Microsoft SQL Server is installed on the local server. Switch parameter so no value is expected.

/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME

Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_REPORTING_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1"

/EXISTING_ REPORTING _DB_SQLINSTANCE_USE_DEFAULT

Indicates that the default SQL instance is to be used. Switch parameter so no value is expected.

/EXISTING_ REPORTING_DB_CUSTOM_SQLINSTANCE

Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /EXISTING_REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER"

/EXISTING_ REPORTING _DB_NAME

Specifies the name of the existing Reporting database that should be used. Takes a string. E.g. /EXISITING_REPORTING_DB_NAME="AppVReporting"

- -   - - **Parameters for installing Reporting Server Database** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/DB_PREDEPLOY_REPORTING

Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected

/REPORTING_DB_SQLINSTANCE_USE_DEFAULT

Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER"

/REPORTING_DB_NAME

Specifies the name of the new Reporting database that should be created. Takes a string. E.g. /REPORTING_DB_NAME="AppVMgmtDB"

/REPORTING_SERVER_MACHINE_USE_LOCAL

Indicates that the Reporting server that will be accessing the database is installed on the local server. Switch parameter so no value is expected.

/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT

Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. E.g. /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername"

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. E.g. /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias"

- -   - - **Parameters for using an existing Management Server Database** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected.If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME

Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_MANAGEMENT_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1"

/EXISTING_ MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

/EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE

Specifies the name of the custom SQL instance that will be used. Example usage /EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”AppVManagement”. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

/EXISTING_MANAGEMENT_DB_NAME

Specifies the name of the existing management database that should be used. Example usage: /EXISITING_MANAGEMENT_DB_NAME=”AppVMgmtDB”. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

-

-

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).

- -   + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterInformation

/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected.If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME

Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_MANAGEMENT_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1"

/EXISTING_ MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

/EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE

Specifies the name of the custom SQL instance that will be used. Example usage /EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”AppVManagement”. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

/EXISTING_MANAGEMENT_DB_NAME

Specifies the name of the existing management database that should be used. Example usage: /EXISITING_MANAGEMENT_DB_NAME=”AppVMgmtDB”. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

+

+

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 diff --git a/windows/manage/appv-deploy-the-appv-server.md b/windows/manage/appv-deploy-the-appv-server.md index c85f273c6c..16d49c34e8 100644 --- a/windows/manage/appv-deploy-the-appv-server.md +++ b/windows/manage/appv-deploy-the-appv-server.md @@ -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**
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. diff --git a/windows/manage/appv-deploying-appv.md b/windows/manage/appv-deploying-appv.md index 14a78375a1..85384b2568 100644 --- a/windows/manage/appv-deploying-appv.md +++ b/windows/manage/appv-deploying-appv.md @@ -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. diff --git a/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md b/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md index 87112ed665..fe452de031 100644 --- a/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md @@ -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). diff --git a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md index 1664333c9f..f441e4af00 100644 --- a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md @@ -133,7 +133,7 @@ The following table describes the recommended methods for excluding specific Off

Use the ExcludeApp setting when you create the package by using the Office Deployment Tool.

@@ -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

How do I package and publish Visio 2013 and Project 2013 with Office?

You must include Visio 2013 and Project 2013 in the same package with Office.

-

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).

+

If you aren’t deploying Office, you can create a package that contains Visio and/or Project.

How can I deploy Visio 2013 and Project 2013 to specific users?

@@ -841,7 +841,7 @@ The following table describes the requirements and options for deploying Visio 2

  1. Create a package that contains Office, Visio, and Project.

  2. Deploy the package to all users.

    3. -

  3. Use [Microsoft AppLocker](http://technet.microsoft.com/library/dd723678.aspx) to prevent specific users from using Visio and Project.

    4. +

  4. Use [AppLocker](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/applocker-overview) to prevent specific users from using Visio and Project.

@@ -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). - -  - -  - - - - - diff --git a/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md b/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md index 67811c04b2..ca135a0bea 100644 --- a/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md +++ b/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md @@ -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) diff --git a/windows/manage/appv-deploying-the-appv-sequencer-and-client.md b/windows/manage/appv-deploying-the-appv-sequencer-and-client.md index 809872cdec..f4c7790c8f 100644 --- a/windows/manage/appv-deploying-the-appv-sequencer-and-client.md +++ b/windows/manage/appv-deploying-the-appv-sequencer-and-client.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). diff --git a/windows/manage/appv-deploying-the-appv-server.md b/windows/manage/appv-deploying-the-appv-server.md index c690b835bd..b1b97bc1be 100644 --- a/windows/manage/appv-deploying-the-appv-server.md +++ b/windows/manage/appv-deploying-the-appv-server.md @@ -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**
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. diff --git a/windows/manage/appv-deployment-checklist.md b/windows/manage/appv-deployment-checklist.md index 2da5471851..b972beff77 100644 --- a/windows/manage/appv-deployment-checklist.md +++ b/windows/manage/appv-deployment-checklist.md @@ -41,7 +41,7 @@ This checklist outlines the recommended steps and items to consider when deployi Checklist box -

Review the App-V supported configurations information to make sure selected client and server computers are supported for App-V feature installation.

+

Review the App-V supported configurations information.

[App-V Supported Configurations](appv-supported-configurations.md)

diff --git a/windows/manage/appv-dynamic-configuration.md b/windows/manage/appv-dynamic-configuration.md index 9f39eb5a86..29d3819f7a 100644 --- a/windows/manage/appv-dynamic-configuration.md +++ b/windows/manage/appv-dynamic-configuration.md @@ -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

ScriptRunner.exe

-

The script launcher application that is installed as part of the App-V client installation.

+

The script launcher application that is included in the App-V client.

Note   -

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.

+

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.

  diff --git a/windows/manage/appv-for-windows.md b/windows/manage/appv-for-windows.md index 17e12bb59e..b714e9c734 100644 --- a/windows/manage/appv-for-windows.md +++ b/windows/manage/appv-for-windows.md @@ -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) diff --git a/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md b/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md index f02ef3fd54..77ee61220b 100644 --- a/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md +++ b/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.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) diff --git a/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md b/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md index 9558f87d73..9f74a81f7a 100644 --- a/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md +++ b/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.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 diff --git a/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md b/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md index 433492faf0..28cdb2f0b8 100644 --- a/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md +++ b/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md @@ -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 diff --git a/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md b/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md index 64a5da1508..414c59f646 100644 --- a/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md +++ b/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md @@ -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: - `` + ```syntax + + + - ` ` + + + - ` ` + - ` ` + - ` ` + - ` ` + + ``` - ` ` +## Have a suggestion for App-V? - `` - -**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **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 diff --git a/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md b/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md index 92d0971f36..db35c6f9aa 100644 --- a/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md +++ b/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md @@ -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 diff --git a/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md b/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md index b54a3e959a..461ae4e6d3 100644 --- a/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md +++ b/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md @@ -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: diff --git a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md index a0df7a5306..0c954a7bf8 100644 --- a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md +++ b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md @@ -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. ## 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. - - ---- - - - - - - - - - - - - - - - - -
TaskMore Information

Upgrade your environment to the latest version of App-V 4.6

[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).

Sequence and roll out App-V packages. As needed, unpublish App-V 4.6 packages.

[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).

- -  - -**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 -

Upgrade your environment to the latest version of App-V 4.6.

-

[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).

+

Review prerequisites.

+

[App-V Server prerequisite software](appv-prerequisites.md#app-v-server-prerequisite-software).

-

Deploy App-V version of the client.

+

Enable the App-V client.

[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).

-

Install App-V server server.

-

[How to Deploy the App-V server Server](appv-deploy-the-appv-server.md).

+

Install App-V Server.

+

[How to Deploy the App-V Server](appv-deploy-the-appv-server.md).

Migrate existing packages.

-

See the Converting packages created using a prior version of App-V section of this article.

+

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.

diff --git a/windows/manage/appv-performance-guidance.md b/windows/manage/appv-performance-guidance.md index 0154fa543b..4091c997e0 100644 --- a/windows/manage/appv-performance-guidance.md +++ b/windows/manage/appv-performance-guidance.md @@ -171,9 +171,9 @@ The following table displays the required steps to prepare the base image and th

-

Windows Server 2012

+

Windows Server 2016

The following prerequisite software is already installed: