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 index dcb94aa781..8bcfe1390f 100644 --- a/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md +++ b/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md @@ -21,28 +21,10 @@ The following recommendations can be used as a baseline to help determine capaci 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. -
Task | -More information | -
---|---|
Determine application scope |
-The App-V infrastructure can be set up in different ways depending on which applications you want to virtualize. This means your first task is to define which applications you want to virtualize. |
-
Determine location scope |
-"Location scope" refers to the physical locations where you plan to run the virtualized applications (for example, enterprise-wide or a specific geographic location). It can also refer to the user population that will run the virtual applications (for example, a single department). You should obtain a network map that includes the connection paths, the available bandwidth for each location, the number of users using virtualized applications, and the WAN link speed. |
-