Infrastructure Planning and Design Guides—Microsoft Application Virtualization 4.6 disponible


The Infrastructure Planning and Design team has released an updated guide: Microsoft Application Virtualization 4.6.

This IPD guide, updated for App-V 4.6, provides actionable guidance for planning your application virtualization infrastructure. With App-V, your organization can respond to the complex challenge of managing applications. This guide simplifies your App-V planning process; updates now include support for Windows 7 and Windows Server 2008 R2, including such features as BranchCache; support for 64-bit clients; and server-sizing data.

Strategically planning your infrastructure can help you avoid problems before they begin, allowing you to serve your customers more accurately and reliably, as well as saving you time and money.

Download the IPD Guide for App-V 4.6 at

Infrastructure Planning and Design series guides streamline the planning process by:

  • Defining the technical decision flow through the planning process.

App-V 4.6 Decision Flow.jpg

  • Listing the decisions to be made and the commonly available options and considerations.

    • Relating the decisions and options to the business in terms of cost, complexity, and other characteristics.

    • Framing decisions in terms of additional questions to the business to ensure a comprehensive alignment with the appropriate business landscape.

The Infrastructure Planning and Design Guide for Microsoft Application Virtualization 4.6 includes the following six-step process:

Step 1: Determining the Project Scope

Before designing a Microsoft Application Virtualization infrastructure, an organization needs to determine the project’s scope: that is, determine which applications will be available virtually and identify the target user population, and their locations, that will access them. The output of this step is used to determine what type of App-V infrastructure should be implemented in Step 2 and to drive the sizing and placement of the servers in Steps 5 and 6.

Step 2: Determining Which Model(s) Will Be Needed

A model refers to the process by which virtualized applications are published and delivered to users.

Deciding how to deploy virtualized applications will come down to determining what model or combination of models for distribution will be required in the organization’s environment to support the business scope defined in Step 1. The distribution models discussed in this step are the Standalone Model, the Streaming Model, and the Full Infrastructure Model.

Step 3: Determining How Many Instances Will Be Needed for Each Model

Step 3 focuses on determining how many instances of each model will be required. (This step can be skipped if the Standalone Model has been selected as the Standalone Model can be used wherever it is needed in the organization since no infrastructure is required.)

Step 4: Client and Sequencer Considerations

This step discusses certain considerations relating to clients and sequencers that need to be taken into account when utilizing Microsoft Application Virtualization in a production environment. Although these considerations do not affect the decisions around the infrastructure design, they do have an impact on the day-to-day performance and functioning of the environment.

Step 5: Designing the Streaming Infrastructure

Streaming is the term used to describe the process of obtaining content from a sequenced application package, starting with Feature Block 1, and then obtaining additional blocks as needed. In this step, the method that the Microsoft Application Virtualization Management System will use to stream the virtual application packages, or .SFT files, from the server to the clients is determined for each location defined in the scope in Step 1.

Step 6: Designing the Full Infrastructure

If it was determined in Step 2 that the Full Infrastructure Model is needed, this step determines the server resource scaling requirements and fault tolerance for each role.

Skip to main content