Microsoft Application Virtualization 4.5 .

Uploaded on:
What Is IPD?. Arranging and outline direction that intends to clear up and streamline the arranging and plan process for Microsoft
Slide 1

Microsoft ® Application Virtualization 4.5 Infrastructure Planning and Design Series

Slide 2

What Is IPD? Arranging and outline direction that means to clear up and streamline the arranging and configuration handle for Microsoft ® framework innovations IPD: Defines choice stream Describes choices to be settled on Relates choices and alternatives for the business Frames extra inquiries for business understanding

Slide 3

Getting Started Microsoft ® Application Virtualization 4.5

Slide 4

Purpose and Agenda Purpose To aid the choice procedure to arrange an effective application virtualization execution Agenda Determine which model(s) are required for a Microsoft Application Virtualization (App-V) engineering Determine what number of occasions are required for each model Client and Sequencer Considerations Design the Streaming Infrastructure Design the Full Infrastructure

Slide 5

Application Management Challenges Application life-cycle administration Deployment Update Support Termination Deploying applications to numerous conditions Desktop Windows Vista ® Microsoft Windows ® XP Microsoft Windows Server ® Terminal Server

Slide 6

What Is Microsoft Application Virtualization? Microsoft Application Virtualization (App-V) is a virtualization arrangement that: Enables associations to react to the administration challenge by giving the capacity to make applications accessible to end-client PCs without installing the applications specifically on those PCs.

Slide 7

Example of App-V Architecture

Slide 8

App-V Design Flow

Slide 9

Determine Model(s) Needed App-V gives three techniques to conveying application virtualization: Option 1: Standalone Model by means of sequencing and customer Option 2: Streaming Model utilizing the local gushing capacities of App-V Option 3: Full Infrastructure Model gives programming appropriation, administration, and announcing abilities (incorporates application spilling)

Slide 10

Option 1: Example Standalone Model Architecture

Slide 11

Option 1: Standalone Model Creates a .msi bundle as a major aspect of utilization sequencing The sequencer makes MSI bundle, which contains the production data, alternate ways, and installer schedules Use the Standalone Model: With separated remote clients who can\'t associate with App-V framework Where programming administration frameworks, for example, SCCM 2007 and SMS 2003, are as of now set up Where arrange transfer speed confinements avert electronic programming dissemination

Slide 12

Option 2: Example of Streaming Model Architecture

Slide 13

Option 2: Streaming Model Applications are spilled in highlight pieces Allows a snappy application begin; needs just Feature Block 1 (FB1) to load application Uses existing server foundation Use the Streaming Model: Where ConfigMgr 2007 SP1 with R2 is as of now set up and the association will utilize it for overseeing virtual application distributing and conveyance Where Active Directory or SQL Server-based servers are not set up, but rather the association needs to exploit spilling virtual applications

Slide 14

Option 3: Example of Full Infrastructure Model Architecture

Slide 15

Option 3: Full Infrastructure Model Requires critical extra foundation Consists of at least one System Center Application Virtualization Management Servers Requires Microsoft SQL Server database Application Virtualization Management Console required on an administration server or an assigned administration workstation Use Full Infrastructure Model: Where the association needs to utilize the Management Server to distribute the application easy routes to the customers Where the extra revealing abilities of the Management Server are fancied When gathering based application distributing is required When permit authorization is required For fast provisioning of uses to customers

Slide 16

Determine Number of App-V Instances Determine number of occurrences for each model Full Infrastructure Model occasion moored by single SQL Server database. Isolate databases characterize isolate occasions. Spilling Model example is characterized by Streaming Server that gives virtualized applications to an area. Every area requires a Streaming Server sent locally.

Slide 17

Assess Client Considerations App-V Desktop Clients Ensure reserve is sufficiently substantial Terminal Server Clients Ensure customers are pre-stored on Terminal Server for execution reasons App-V Clients Are constrained to 32-bit working frameworks And must be pre-introduced for all models

Slide 18

Sequencer Considerations Sequencer ought to be set in a segregated situation No operators or foundation applications Virtual machine or physical CPU Must have a moment drive with a letter that matches the virtual drive utilized by the customer Default is drive Q Deploying to an arranging domain is suggested

Slide 19

Design Streaming Infrastructure Three distinctive Streaming Server sorts:

Slide 20

Determine Streaming Server Scaling and Fault Tolerance Streaming Server size is exceedingly subject to condition in which it\'s set Start with one gushing server (or two if required for adaptation to non-critical failure) Fault resilience for Streaming Servers utilizing RTSP/S accomplished by load adjusting the servers For data about adaptation to internal failure alternatives accessible to record servers and IIS, see IPD – Windows Server 2008 File Services and Internet Information Services 7.0

Slide 21

Design Full Infrastructure Model App-V Full Infrastructure Model case incorporates these server parts: App-V Management Server Streaming Server running App-V Management Web Service SQL Server Active Directory App-V Management Console Sequencer for making virtualized application bundles App-V Client introduced on frameworks requiring application virtualization (desktops, VMs, or Terminal Servers)

Slide 22

Determine Full Infrastructure Server Resource Scaling No complete numbers accessible so should decide asset necessities for each App-V part by utilizing execution observing devices in Windows Server Decisions to make : Management Server Service — Service can be set all alone server, or be set on the Management Server SQL Server — App-V Data Store can be situated on a committed SQL Server case, or in a mutual database server Management Server Scaling — To scale out, utilize stack adjusting

Slide 23

Determine Full Infrastructure Fault Tolerance for Each Role and Combining Roles Decisions to make: Management Server Service — Service can be on same server with Management Console unless Management Server is load adjusted Microsoft SQL Server — Several SQL Server(s) forms accessible to give adaptation to internal failure, and additionally plausibility of grouping Management Server — Two load adjusting choices for Management Server: programming based and equipment stack adjusting Combining Server Roles: Compatible Fault-Tolerant Role Combinations

Slide 24

Summary and Conclusion A blend of models might be required to convey virtual applications inside the association Carefully consider prerequisites for spilling foundation Planning is scratch Provide input to

Slide 25

Find More Information Download the full archive and other IPD guides: http:/ Contact the IPD group: The Microsoft Solution Accelerators Web website:

View more...