diff --git a/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md b/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md new file mode 100644 index 0000000000..373cd9aa7b --- /dev/null +++ b/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md @@ -0,0 +1,947 @@ +--- +title: App-V Capacity Planning (Windows 10) +description: App-V Capacity Planning +author: MaggiePucciEvans +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +ms.date: 04/19/2017 +--- +# App-V Capacity Planning + +>Applies to Windows Server 2016. + +The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V infrastructure. + +>[!IMPORTANT] +>Use the information in this section only as a general guide for planning your App-V deployment. Your system capacity requirements will depend on the specific details of your hardware and application environment. Additionally, the performance numbers displayed in this document are examples and your results may vary. + +## Determine the project scope + +Before you design the App-V infrastructure, determining which applications will be available virtually, and also identify the target users and their locations. This information will determine what type of App-V infrastructure your project should implement. Your should base your decisions about your project's scope on your organization's specific needs. + + ++++ + + + + + + + + + + + + + + + + +
TaskMore Information

Determine Application Scope

Depending on the applications to be virtualized, the App-V infrastructure can be set up in different ways. The first task is to define what applications you want to virtualize.

Determine Location Scope

Location scope refers to the physical locations (for example, enterprise-wide or a specific geographic location) where you plan to run the virtualized applications. It can also refer to the user population (for example, a single department) who will run the virtual applications. You should obtain a network map that includes the connection paths as well as available bandwidth to each location and the number of users using virtualized applications and the WAN link speed.

+ +## Determine Which App-V Infrastructure is Required + +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 System Center 2012 Configuration Manager. + + - When network bandwidth limitations inhibit electronic software distribution. + +- **Full Infrastructure Model** - The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V Full Infrastructure Model consists of one or more App-V management servers. The Management Server can be used to publish applications to all clients. The publishing process places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about installing the management server see, [Planning for App-V Server Deployment](appv-planning-for-appv-server-deployment.md). The full infrastructure model is recommended for the following scenarios: + + >**Important**   + The App-V full infrastructure model requires Microsoft SQL Server to store configuration data. For more information see [App-V Supported Configurations](appv-supported-configurations.md). + +   + + - When you want to use the Management Server to publish the application to target computers. + + - For rapid provisioning of applications to target computers. + + - When you want to use App-V reporting. + +## End-to-end Server Sizing Guidance + + +The following section provides information about end-to-end App-V sizing and planning. For more specific information, refer to the subsequent sections. + +**Note**   +Round trip response time on the client is the time taken by the computer running the App-V client to receive a successful notification from the publishing server. Round trip response time on the publishing server is the time taken by the computer running the publishing server to receive a successful package metadata update from the management server. + +  + +- 20,000 clients can target a single publishing server to obtain the package refreshes in an acceptable round trip time. (<3 seconds) + +- A single management server can support up to 50 publishing servers for package metadata refreshes in an acceptable round trip time. (<5 seconds) + +## App-V Management Server Capacity Planning Recommendations + + +The App-V publishing servers require the management server for package refresh requests and package refresh responses. The management server then sends the information to the management database to retrieve information. For more information about App-V management server supported configurations see [App-V Supported Configurations](appv-supported-configurations.md). + +**Note**   +The default refresh time on the App-V publishing server is ten minutes. + +  + +When multiple simultaneous publishing servers contact a single management server for package metadata refreshes, the following three factors influence the round trip response time on the publishing server: + +1. Number of publishing servers making simultaneous requests. + +2. Number of connection groups configured on the management server. + +3. Number of access groups configured on the management server. + +The following table displays more information about each factor that impacts round trip time. + +**Note**   +Round trip response time is the time taken by the computer running the App-V publishing server to receive a successful package metadata update from the management server. + +  + + ++++ + + + + + + + + + + + + + + + + + + + + +
Factors impacting round trip response timeMore Information

The number of publishing servers simultaneously requesting package metadata refreshes.

+
    +

  • A single management server can respond to up to 320 publishing servers requesting publishing metadata simultaneously.

    • +

  • Round trip response time for 320 pub servers is ~40 seconds.

    • +

  • For <50 publishing servers requesting metadata simultaneously, the round trip response time is <5 seconds.

    • +

  • From 50 to 320 publishing servers, the response time increases linearly (approximately 2x).

    • +

The number of connection groups configured on the management server.

+

+
    +

  • For up to 100 connection groups, there is no significant change in the round trip response time on the publishing server.

    • +

  • For 100 - 400 connection groups, there is a minor linear increase in the round trip response time.

    • +

The number of access groups configured on the management server.

+

+
    +

  • For up to 40 access groups, there is a linear (approximately 3x) increase in the round trip response time on the publishing server.

    • +
+ +  + +The following table displays sample values for each of the previous factors. In each variation, 120 packages are refreshed from the App-Vmanagement server. + + ++++++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ScenarioVariationNumber of connection groupsNumber of access groupsNumber of publishing serversNetwork connection type publishing server / management serverRound trip response time on the publishing server (in seconds)CPU utilization on management server

Publishing servers simultaneously contacting management server for publishing metadata.

Number of publishing servers

+
    +

  • 0

    • +

  • 0

    • +

  • 0

    • +

  • 0

    • +

  • 0

    • +

  • 0

    • +

+
    +

  • 1

    • +

  • 1

    • +

  • 1

    • +

  • 1

    • +

  • 1

    • +

  • 1

    • +

+
    +

  • 50

    • +

  • 100

    • +

  • 200

    • +

  • 300

    • +

  • 315

    • +

  • 320

    • +

+
    +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

+
    +

  • 5

    • +

  • 10

    • +

  • 19

    • +

  • 32

    • +

  • 30

    • +

  • 37

    • +

+
    +

  • 17

    • +

  • 17

    • +

  • 17

    • +

  • 15

    • +

  • 17

    • +

  • 15

    • +

Publishing metadata contains connection groups

Number of connection groups

+
    +

  • 10

    • +

  • 50

    • +

  • 100

    • +

  • 150

    • +

  • 300

    • +

  • 400

    • +

+
    +

  • 1

    • +

  • 1

    • +

  • 1

    • +

  • 1

    • +

  • 1

    • +

  • 1

    • +

+
    +

  • 100

    • +

  • 100

    • +

  • 100

    • +

  • 100

    • +

  • 100

    • +

  • 100

    • +

+
    +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

+
    +

  • 10

    • +

  • 11

    • +

  • 11

    • +

  • 16

    • +

  • 22

    • +

  • 25

    • +

+
    +

  • 17

    • +

  • 19

    • +

  • 22

    • +

  • 19

    • +

  • 20

    • +

  • 20

    • +

Publishing metadata contains access groups

Number of access groups

+
    +

  • 0

    • +

  • 0

    • +

  • 0

    • +

  • 0

    • +

+
    +

  • 1

    • +

  • 10

    • +

  • 20

    • +

  • 40

    • +

+
    +

  • 100

    • +

  • 100

    • +

  • 100

    • +

  • 100

    • +

+
    +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

+
    +

  • 10

    • +

  • 43

    • +

  • 153

    • +

  • 535

    • +

+
    +

  • 17

    • +

  • 26

    • +

  • 24

    • +

  • 24

    • +
+ +  + +The CPU utilization of the computer running the management server is around 25% irrespective of the number of publishing servers targeting it. The Microsoft SQL Server database transactions/sec, batch requests/sec and user connections are identical irrespective of the number of publishing servers. For example: Transactions/sec is ~30, batch requests ~200, and user connects ~6. + +Using a geographically distributed deployment, where the management server & publishing servers utilize a slow link network between them, the round trip response time on the publishing servers is within acceptable time limits (<5 seconds), even for 100 simultaneous requests on a single management server. + + ++++++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ScenarioVariationNumber of connection groupsNumber of access groupsNumber of publishing serversNetwork connection type publishing server / management serverRound trip response time on the publishing server (in seconds)CPU utilization on management server

Network connection between the publishing server and management server

1.5 Mbps Slow link Network

+
    +

  • 0

    • +

  • 0

    • +

+
    +

  • 1

    • +

  • 1

    • +

+
    +

  • 50

    • +

  • 100

    • +

+
    +

  • 1.5Mbps Cable DSL

    • +

  • 1.5Mbps Cable DSL

    • +

+
    +

  • 4

    • +

  • 5

    • +

+
    +

  • 1

    • +

  • 2

    • +

Network connection between the publishing server and management server

LAN / WIFI Network

+
    +

  • 0

    • +

  • 0

    • +

+
    +

  • 1

    • +

  • 1

    • +

+
    +

  • 100

    • +

  • 200

    • +

+
    +

  • Wifi

    • +

  • Wifi

    • +

+
    +

  • 11

    • +

  • 20

    • +

+
    +

  • 15

    • +

  • 17

    • +
+ +  + +Whether the management server and publishing servers are connected over a slow link network, or a high speed network, the management server can handle approximately 15,000 package refresh requests in 30 minutes. + +## App-V Reporting Server Capacity Planning Recommendations + + +App-V clients send reporting data to the reporting server. The reporting server then records the information in the Microsoft SQL Server database and returns a successful notification back to the computer running App-V client. For more information about App-V Reporting Server supported configurations see [App-V Supported Configurations](appv-supported-configurations.md). + +**Note**   +Round trip response time is the time taken by the computer running the App-V client to send the reporting information to the reporting server and receive a successful notification from the reporting server. + +  + + ++++ + + + + + + + + + + + + + + + + + + + + +
ScenarioSummary

Multiple App-V clients send reporting information to the reporting server simultaneously.

+
    +

  • Round trip response time from the reporting server is 2.6 seconds for 500 clients.

    • +

  • Round trip response time from the reporting server is 5.65 seconds for 1000 clients.

    • +

  • Round trip response time increases linearly depending on number of clients.

    • +

Requests per second processed by the reporting server.

+

+
    +

  • A single reporting server and a single database, can process a maximum of 139 requests per second. The average is 121 requests/second.

    • +

  • Using two reporting servers reporting to the same Microsoft SQL Server database, the average requests/second is similar to a single reporting server = ~127, with a max of 278 requests/second.

    • +

  • A single reporting server can process 500 concurrent/active connections.

    • +

  • A single reporting server can process a maximum 1500 concurrent connections.

    • +

Reporting Database.

+

+
    +

  • Lock contention on the computer running Microsoft SQL Server is the limiting factor for requests/second.

    • +

  • Throughput and response time are independent of database size.

    • +
+ +  + +**Calculating random delay**: + +The random delay specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between **0** and **ReportingRandomDelay** and will wait the specified duration before sending data. + +Random delay = 4 \* number of clients / average requests per second. + +Example: For 500 clients, with 120 requests per second, the Random delay is, 4 \* 500 / 120 = ~17 minutes. + +## App-V Publishing Server Capacity Planning Recommendations + + +Computers running the App-V client connect to the App-V publishing server to send a publishing refresh request and to receive a response. Round trip response time is measured on the computer running the App-V client. Processor time is measured on the publishing server. For more information about App-V Publishing Server supported configurations see [App-V Supported Configurations](appv-supported-configurations.md). + +**Important**   +The following list displays the main factors to consider when setting up the App-V publishing server: + +- The number of clients connecting simultaneously to a single publishing server. + +- The number of packages in each refresh. + +- The available network bandwidth in your environment between the client and the App-V publishing server. + +  + + ++++ + + + + + + + + + + + + + + + + + + + + +
ScenarioSummary

Multiple App-V clients connect to a single publishing server simultaneously.

+
    +

  • A publishing server running dual core processors can respond to at most 5000 clients requesting a refresh simultaneously.

    • +

  • For 5000-10000 clients, the publishing server requires a minimum quad core.

    • +

  • For 10000-20000 clients, the publishing server should have dual quad cores for more efficient response times.

    • +

  • A publishing server with a quad core can refresh up to 10000 packages within 3 seconds. (Supporting 10000 simultaneous clients)

    • +

Number of packages in each refresh.

+

+
    +

  • Increasing number of packages will increase response time by ~40% (up to 1000 packages).

    • +

Network between the App-V client and the publishing server.

+

+
    +

  • Across a slow network (1.5 Mbps bandwidth), there is a 97% increase in response time compared to LAN (up to 1000 users).

    • +
+ +  + +**Note**   +The publishing server CPU usage is always high during the time interval when it has to process simultaneous requests (>90% in most cases). The publishing server can handle ~1500 client requests in 1 second. + +  + + ++++++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ScenarioVariationNumber of App-V clientsNumber of packagesProcessor configuration on the publishing serverNetwork connection type publishing server / App-V clientRound trip time on the App-V client (in seconds)CPU utilization on publishing server (in %)

App-V client sends publishing refresh request & receives response, each request containing 120 packages

Number of clients

+
    +

  • 100

    • +

  • 1000

    • +

  • 5000

    • +

  • 10000

    • +

+
    +

  • 120

    • +

  • 120

    • +

  • 120

    • +

  • 120

    • +

+
    +

  • Dual Core

    • +

  • Dual Core

    • +

  • Quad Core

    • +

  • Quad Core

    • +

+
    +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

+
    +

  • 1

    • +

  • 2

    • +

  • 2

    • +

  • 3

    • +

+
    +

  • 100

    • +

  • 99

    • +

  • 89

    • +

  • 77

    • +

Multiple packages in each refresh

Number of packages

+
    +

  • 1000

    • +

  • 1000

    • +

+
    +

  • 500

    • +

  • 1000

    • +

+
    +

  • Quad Core

    • +

  • Quad Core

    • +

+
    +

  • LAN

    • +

  • LAN

    • +

+
    +

  • 2

    • +

  • 3

    • +

+
    +

  • 92

    • +

  • 91

    • +

Network between client and publishing server

1.5 Mbps Slow link network

+
    +

  • 100

    • +

  • 500

    • +

  • 1000

    • +

+
    +

  • 120

    • +

  • 120

    • +

  • 120

    • +

+
    +

  • Quad Core

    • +

  • Quad Core

    • +

  • Quad Core

    • +

+
    +

  • 1.5 Mbps Intra-Continental Network

    • +

+
    +

  • 3

    • +

  • 10 (with 0.2% failure rate)

    • +

  • 17 (with 1% failure rate)

    • +

+ +  + +## App-V Streaming Capacity Planning Recommendations + + +Computers running the App-V client stream the virtual application package from the streaming server. Round trip response time is measured on the computer running the App-V client, and is the time taken to stream the entire package. + +**Important**   +The following list identifies the main factors to consider when setting up the App-V streaming server: + +- The number of clients streaming application packages simultaneously from a single streaming server. + +- The size of the package being streamed. + +- The available network bandwidth in your environment between the client and the streaming server. + +  + + ++++ + + + + + + + + + + + + + + + + + + + + +
ScenarioSummary

Multiple App-V clients stream applications from a single streaming server simultaneously.

+
    +

  • If the number of clients simultaneously streaming from the same server increases, there is a linear relationship with the package download/streaming time.

    • +

Size of the package being streamed.

+

+
    +

  • The package size has a significant impact on the streaming/download time only for larger packages with a size ~ 1GB. For package sizes ranging from 3 MB to 100 MB, the streaming time ranges from 20 seconds to 100 seconds, with 100 simultaneous clients.

    • +

Network between the App-V client and the streaming server.

+

+
    +

  • Across a slow network (1.5 Mbps bandwidth), there is a 70-80% increase in response time compared to LAN (up to 100 users).

    • +
+ +  + +The following table displays sample values for each of the factors in the previous list: + + ++++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ScenarioVariationNumber of App-V clientsSize of each packageNetwork connection type streaming server / App-V clientRound trip time on the App-V client (in seconds)

Multiple App-V clients streaming virtual application packages from a streaming server.

Number of clients.

+
    +

  • 100

    • +

  • 200

    • +

  • 1000

    • +

    • +

  • 100

    • +

  • 200

    • +

  • 1000

    • +

+
    +

  • 3.5 MB

    • +

  • 3.5 MB

    • +

  • 3.5 MB

    • +

    • +

  • 5 MB

    • +

  • 5 MB

    • +

  • 5 MB

    • +

+
    +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

    • +

  • LAN

    • +

  • LAN

    • +

  • LAN

    • +

+
    +

  • 29

    • +

  • 39

    • +

  • 391

    • +

    • +

  • 35

    • +

  • 68

    • +

  • 461

    • +

Size of each package being streamed.

Size of each package.

+
    +

  • 100

    • +

  • 200

    • +

    • +

  • 100

    • +

  • 200

    • +

+
    +

  • 21 MB

    • +

  • 21 MB

    • +

    • +

  • 109

    • +

  • 109

    • +

+
    +

  • LAN

    • +

  • LAN

    • +

    • +

  • LAN

    • +

  • LAN

    • +

+

33

+

83

+

+

100

+

160

Network connection between client and App-V streaming server.

1.5 Mbps Slow link network.

+
    +

  • 100

    • +

    • +

  • 100

    • +

+
    +

  • 3.5 MB

    • +

    • +

  • 5 MB

    • +

+
    +

  • 1.5 Mbps Intra-Continental Network

    • +

+

102

+

+

121

+ +  + +Each App-V streaming server should be able to handle a minimum of 200 clients concurrently streaming virtualized applications. + +**Note**   +The actual time to it will take to stream is determined primarily by the number of clients streaming simultaneously, number of packages, package size, the server’s network activity, and network conditions. + +  + +For example, an average user can stream a 100 MB package in less than 2 minutes, when 100 simultaneous clients are streaming from the server. However, a package of size 1 GB could take up to 30 minutes. In most real world environments streaming demand is not uniformly distributed, you will need to understand the approximate peak streaming requirements present in your environment in order to properly size the number of required streaming servers. + +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 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. + +Ignoring scaling requirements, the minimum number of servers necessary to provide a fault-tolerant implementation is four. The management server, and Microsoft SQL Server roles support being placed in fault-tolerant configurations. The management server service can be combined with any of the roles, but remains a single point of failure. + +Although there are a number of fault-tolerance strategies and technologies available, not all are applicable to a given service. Additionally, if App-V roles are combined, certain fault-tolerance options may no longer apply due to incompatibilities. + +## Have a suggestion for App-V? + + +Add or vote on suggestions on the [Application Virtualization feedback site](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 + + +[App-V Supported Configurations](appv-supported-configurations.md) + +[Planning for High Availability with App-V](appv-planning-for-high-availability-with-appv.md) + +[Planning to Deploy App-V](appv-planning-to-deploy-appv.md) + +  + +  + + + + + diff --git a/windows/application-management/app-v/revision-heidi/appv-planning-to-deploy-appv.md b/windows/application-management/app-v/revision-heidi/appv-planning-to-deploy-appv.md new file mode 100644 index 0000000000..6d9f809920 --- /dev/null +++ b/windows/application-management/app-v/revision-heidi/appv-planning-to-deploy-appv.md @@ -0,0 +1,57 @@ +--- +title: Planning to Deploy App-V (Windows 10) +description: Planning to Deploy App-V +author: MaggiePucciEvans +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +ms.date: 04/19/2017 +--- +# Planning to Deploy App-V for Windows 10 + +>Applies to Windows 10, version 1607. + +There are several different deployment configurations and requirements to consider before you deploy App-V for Windows 10. Review this topic for information about what you'll need to make a deployment plan that best meets your needs. + +## App-V supported configurations + +[App-V supported configurations](appv-supported-configurations.md) describes the minimum hardware and operating system requirements for each App-V components. For information about software that you must install before you install App-V, see [App-V Prerequisites](appv-prerequisites.md). + +## App-V capacity planning + +[App-V capacity planning](appv-capacity-planning.md) describes the available options for scaling your App-V deployment. + +## Planning for high availability with App-V + +[Planning for high availability with App-V](appv-planning-for-high-availability-with-appv.md) describes the available options for ensuring high availability of App-V databases and services. + +## Planning to Deploy App-V with an Electronic Software Distribution System + +[Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md) describes the options and requirements for deploying App-V with an electronic software distribution system. + +## Planning for App-V server deployment + +[Planning for the App-V server deployment](appv-planning-for-appv-server-deployment.md) describes the planning considerations for the App-V Server components and their functions. + +## Planning for the App-V Sequencer and Client deployment + +[Planning for the App-V Sequencer and Client deployment](appv-planning-for-sequencer-and-client-deployment.md) describes planning considerations you should make for deploying the App-V Client and the Sequencer software, which you use to create virtual applications and application packages. + +## Planning for migrating from a previous version of App-V + +[Migrating to App-V from a previous version](appv-migrating-to-appv-from-a-previous-version.md) describes the recommended path for migrating from previous versions of App-V without disrupting your existing server configurations, packages, and clients. + +## Planning for using App-V with Office + +[Planning for using App-V with Office](appv-planning-for-using-appv-with-office.md) describes the requirements for using App-V with Office and the supported scenarios, including information about coexisting versions of Office. + +## Planning to use folder redirection with App-V + +[Planning to use folder redirection with App-V](appv-planning-folder-redirection-with-appv.md) explains how folder redirection works with App-V. + +## Other Resources for App-V Planning + +* [Planning for App-V](appv-planning-for-appv.md) + +* [Performance Guidance for Application Virtualization](appv-performance-guidance.md) diff --git a/windows/application-management/app-v/revision-heidi/appv-security-considerations.md b/windows/application-management/app-v/revision-heidi/appv-security-considerations.md index 64eb79bd48..96e9ecb23b 100644 --- a/windows/application-management/app-v/revision-heidi/appv-security-considerations.md +++ b/windows/application-management/app-v/revision-heidi/appv-security-considerations.md @@ -113,13 +113,4 @@ During App-V setup, setup log files are created in the **%temp%** folder of the ## Related topics -[Preparing Your Environment for App-V](appv-preparing-your-environment.md) - -  - -  - - - - - +[Preparing Your Environment for App-V](appv-preparing-your-environment.md) \ No newline at end of file diff --git a/windows/application-management/app-v/revision-heidi/appv-supported-configurations.md b/windows/application-management/app-v/revision-heidi/appv-supported-configurations.md new file mode 100644 index 0000000000..030a3b0a91 --- /dev/null +++ b/windows/application-management/app-v/revision-heidi/appv-supported-configurations.md @@ -0,0 +1,223 @@ +--- +title: App-V Supported Configurations (Windows 10) +description: App-V Supported Configurations +author: MaggiePucciEvans +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +ms.date: 04/19/2017 +--- +# App-V Supported Configurations + +>Applies to Windows 10, version 1607; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; and Windows Server 2008 R2. + +This topic specifies the requirements to install and run App-V in your Windows 10 environment. For information about prerequisite software such as the .NET Framework, see [App-V prerequisites](appv-prerequisites.md). + +## App-V Server system requirements + +This section lists the operating system and hardware requirements for all App-V server components. + +### Unsupported App-V server scenarios + +The App-V server does not support the following scenarios: + +* Deployment to a computer that runs the Server Core installation option. + +* Deployment to a computer that runs a previous version of the App-V server components. You can only install App-V side-by-side with the App-V 4.5 Lightweight Streaming Server (LWS) server. This scenario doesn't support side-by-side deployment of App-V and the Application Virtualization Management Service (HWS) 4.x. + +* Deployment to a computer running Microsoft SQL Server Express edition. + +* Deployment to a domain controller. + +* Short paths. If you plan to use a short path, you must create a new volume. + +### Management server operating system requirements + +You can install the App-V Management server on a server running Windows Server 2008 R2 with SP1 or later. + +>[!IMPORTANT] +>Deploying a Management server role to a computer with Remote Desktop Services enabled is not supported. + +### Management server hardware requirements + +* A 64-bit (x64) processor that runs at 1.4 GHz or faster. + +* 1 GB RAM (64-bit). + +* 200 MB of available hard disk space, not including the content directory. + +### Management server database requirements + +The following table lists the SQL Server versions that the App-V Management database installation supports. + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + +
SQL Server versionService packSystem architecture

Microsoft SQL Server 2014

32-bit or 64-bit

Microsoft SQL Server 2012

SP2

32-bit or 64-bit

Microsoft SQL Server 2008 R2

SP3

32-bit or 64-bit

+ +### Publishing server operating system requirements + +The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later. + +### Publishing server hardware requirements + +App-V adds no additional requirements beyond those of Windows Server. + +* A 64-bit (x64) processor that runs at 1.4 GHz or faster. + +* 2 GB RAM (64-bit). + +* 200 MB of available hard disk space, not including the content directory. + +### Reporting server operating system requirements + +You can install the App-V Reporting server on a server running Windows Server 2008 R2 with SP1 or later. + +### Reporting server hardware requirements + +App-V adds no additional requirements beyond those of Windows Server. + +* A 64-bit (x64) processor that runs at 1.4 GHz or faster. + +* 2 GB RAM (64-bit). + +* 200 MB of available hard disk space, not including the content directory. + +### Reporting server database requirements + +The following table lists the SQL Server versions that are supported for the App-V Reporting database installation. + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + +
SQL Server versionService packSystem architecture

Microsoft SQL Server 2014

32-bit or 64-bit

Microsoft SQL Server 2012

SP2

32-bit or 64-bit

Microsoft SQL Server 2008 R2

SP3

32-bit or 64-bit

+ +## App-V client and Remote Desktop Services client requirements + +With Windows 10, version 1607 and later releases, the App-V client is included with Windows 10 Enterprise and Windows 10 Education. The App-V client is no longer part of the Microsoft Desktop Optimization Pack. Before you can use the App-V client, it must be enabled, as described in [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). + +Similarly, the App-V Remote Desktop Services (RDS) client is included with Windows Server 2016 Standard and Windows Server 2016 Datacenter. + +## Sequencer system requirements + +The following table lists the operating systems that the App-V Sequencer installation supports. + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Operating systemService packSystem architecture

Microsoft Windows Server 2012 R2

64-bit

Microsoft Windows Server 2012

64-bit

Microsoft Windows Server 2008 R2

SP1

64-bit

Microsoft Windows 10

32-bit and 64-bit

Microsoft Windows 8.1

32-bit and 64-bit

Microsoft Windows 8

32-bit and 64-bit

Microsoft Windows 7

SP1

32-bit and 64-bit

+ +### Sequencer hardware requirements + +See the Windows or Windows Server documentation for the hardware requirements. + +## Supported versions of System Center Configuration Manager + +The App-V client works with System Center Configuration Manager versions starting with Technical Preview for System Center Configuration Manager, version 1606. + +## Related topics + +* [Planning to deploy App-V](appv-planning-to-deploy-appv.md) +* [App-V prerequisites](appv-prerequisites.md) \ No newline at end of file