Sizing App-V 5:Planning and Designing a Highly Available, Scalable, & Resilient Management and Delivery SystemSteve Thomas

Session Code

Session Objective(s): Understand the Criticality of each App-V Infrastructure RoleUnderstand the Information/Data Flow of an App-V Based Application Delivery SystemUnderstand how to Architect App-V for Redundancy and Resiliency

Key TakeawaysIdentify the load-balancing, failover, replication, mirroring, and rapid provisioning options for various components of the App-V infrastructure.Implement recommended practices for streaming bandwidth management and Shared Content Store Design.Understand how to size and plan the App-V 5 management and publishing infrastructure.

Session Objectives And Takeaways

About MeBlog:http://blogs.technet.com/b/gladiatormsft/

Twitter:http://twitter.com/madvirtualizer

LinkedIn:http://www.linkedin.com/steveth

Facebook:http://www.facbook.com/madvirtualizer

AgendaIntroductionDelivery ArchitecturesEvolution of ArchitectureFeedback from FieldComponents of the App-V MGT/Pub System

Management, Publishing, and Reporting ServicesDeployment ResourcesSizing HA TechnologiesOutages

Audience PollNew to App-V?App-V 5 Experience?App-V 4.x ExperienceSoftgrid 3.x and Earlier Experience?

Assumptions

Where are the Doc’s?

DOC

Capacity Planning:http://technet.microsoft.com/en-us/library/dn595131.aspx

App-V BPA:http://www.microsoft.com/en-us/download/details.aspx?id=38844

Performance Guidance (SP2 HF4):http://technet.microsoft.com/en-us/library/dn659478.aspx

App-V Supported Configurations :http://technet.microsoft.com/en-us/library/jj713426.aspx

Planning for Server Deployment:http://technet.microsoft.com/en-us/library/jj713496.aspx

Right Here!

Delivery Architectures

App-V 5.0 Delivery OptionsApp-V Publishing InfrastructureFully Integrated

Configuration Manager 2012 SP1 IntegrationFully Integrated

Stand-Alone (default)(often coupled w/Alternative Publishing)Independent File\Web Streaming

Local Desktop

Virtual Desktop

Login xxx Login xxx

End Point

In-Scope: App-V Management InfrastructureDelivers Desktop Configuration ControlDelivers Applications and Virtual EnvironmentsTargets Users and/or ComputersRestful APISupports ReportingResilient and Scalable Rich UI (XAML,PoSh)

Out of Scope: Configuration Manager 2012 SP1Targets User and ComputersDelivers Applications and Virtual EnvironmentsAllows use of existing ESD

The best choice – especially if you already have CM deployed*

Out of Scope: Stand-AloneClient Runs Standalone by DefaultApplications delivered through MSI or PoSh/COM/WMI API’sApplications managed by Custom Scripting/programming3rd-Party ESD’s (i.e. Altiris)Ideal for Alternative Conduits

Evolution:Key Architectural Changes from 4.6

“The cheese has been moved.” – App-V MVP

ImprovementsRole Segmentation and Separation

Segmentation of Management, Reporting, and Publishing DataSQL No Longer Single Point of FailurePublishing Data is flat XML

ProtocolsRTSP replaced with HTTP(s) for primary publishing and SMB/HTTP(s) for streamingMore scalable, cloud and firewall friendly

Flexible Shared Content StoreManagement

Can target machines and usersIn-band Connection Group Management

Deprecated FeaturesLicense Management by App-V Management ServerFeature tied to legacy protocol

Provider PoliciesCreate another access layer that created many support incidents

Application PermissionsUse Applocker Policies

Text LoggingLogging: Now Decentralized and ETW-based

Canned Reports within Management InterfaceUse SSRS or your favorite report viewer instead

Let go of the past

From the field: Early Implementations

What you Should be UsingClient App-V 5.0 SP2 HF4http://support.microsoft.com/kb/2956985

- Better Publishing Experience- Impersonation- Numerous Bug fixes and “retro-DCRs”

ServerApp-V 5.0 SP1 HF4http://support.microsoft.com/kb/2940354

- Silverlight Scroll Issue

App-V 5 Datacenter TrendsSession Desktops\Published Apps

Virtual Desktops

Type Vapp Delivery InfrastructurePersistent RDS\XenApp Servers CM IntegrationNon-Persistent XenApp\RDS App-V Publishing*

Type Vapp Delivery InfrastructurePersistent\Static VDI\XD CM IntegrationNon-Persistent\Pooled VDI\XD App-V Publishing

Typical Enterprise Deployment

Client Orchestration

Publishing Catalog/

Agent

Reporting Agent

AppV Package

Root Store

App-V Reporting Server

App-V Publishing Server

Redundant Content Server (SMB)

[DFS-R also available]

App-V Management Server

Redundant Content Server (HTTP/HTTPS)

SQL Database Server (Mirroring or Failover Clustering)

Management Database

Reporting Database

Universal App-V Package Store

Stream to Disk or Memory

Critical Levels of Redundancy and AvailabilityContent StoresThe Streamed ContentThe Shared Content Store

Publishing ServersStatelessWeb-based AppEasy to Scale, Cheap to Deploy

Session HostsCritical for Extranets, Tablets, IOS, Android

DatabaseEliminate SQL as a single point of failure

Expected Causes of Critical Situations (Historically From the Field)Content/Management Service OutagesResource Depletion on RDS ServersSQL DataStore Failure

Unexpected Causes of Critsits (From the Field)Permission Changes (Content/DFS)Port ExhaustionPorts/Firewall Policy ChangesSQL Fiefdoms GPO Modification Errors

Components of the App-V Management System

Logical DesignAdmin

CLIENT ECOSYSTEM

POSH XAML

App-V Infrastructure ComponentsKey DataContent StorePublishing CatalogManagement Data StoreReporting Data Store

Server Roles SQL ServerContent ServerManagement ServerPublishing ServerReporting Server

SQL ServerManagement DatabaseAsset Registration

PackagesConnection Groups

Assignments/EntitlementsGroupsMachines

ConfigurationUser and Deployment

List of APP-V AdministratorsList of publishing servers

Reporting DatabaseUploaded XML for use by SSRS/Excel, etc.

Content ServerStreaming SourcePackage SourceShared Content StoreStream to Memory instead of Stream to DiskStorage reduction 80-95%No additional management requirements

Shared Content vs. StreamingCompatible Streaming Feature

YesProlonged stream fault

Failed stream fault

Loss of network connectivity indicator

“Pre-Mount” (Pre-Load)

Publishing feature block (FB0)File streamingUNC streamingHTTP streaming

NoFB1

Streaming progress indicator

Allow offline option

Management, Publishing, and Reporting Services

You manage web servicesIIS console is operations management and troubleshooting resourceServices run as worker processes

LEARN IIS!!!!

Management ServerManaged Web ServiceWCF

ControlWeb UI ConsoleXAML (Silverlight)PowerShell

EntitlementsApp-V AdminsAdd/Remove PackagesModify Configuration XML of ApplicationChange Publishing Servers

Publishing ServerCatalogPublished PackagesPublished Connection GroupsUser/Deployment Configuration

FunctionalityAs a part of publishing refresh, clients speak with their associated publishing servers to get publishing metadataAdministrators can use Group Policy or client PowerShell command-lets to associate publishing servers with the clientPublishing server is stateless

Location

Entitlement to Publish1. Publishing Services and Management

Services run in separate IIS Worker Processes

2. Admin adds Package, Configuration, Connection Group(s) and assigns to AD Group.

3. DB and Publishing Sequence Number updated.

4. Publishing Server syncs with Management Server.

5. Clients sync with Publishing Server.

Reporting ServerCollects reporting data from the clients and stores it in the databaseReporting does not have UI built-inNo interaction with the management server or publishing serverOptional- only need to install if using reportingCustomers use SSRS or Preferred RV to view reporting dataSamples:http://www.microsoft.com/en-us/download/details.aspx?id=42630

Client Roles/AssetsPublishing AgentReporting AgentCatalog/ManifestsGlobal-%PROGRAMDATA%\Microsoft\AppV\Client\CatalogUser-%APPDATA%\Microsoft\AppV\Client\Catalog

Integration Junction PointsGlobal-%PROGRAMDATA%\Microsoft\AppV\Client\IntegrationUser-%LOCALAPPDATA%\Microsoft\AppV\Client\Integration

PackagesPackageGroups (CG)

Deployment Resources

Client ConfigurationInstaller Switcheshttp://technet.microsoft.com/en-us/library/jj713460.aspx

PowerShellSet-AppVClientConfiguration

Group Policyhttp://www.microsoft.com/en-us/download/details.aspx?id=41183

Table of Options:http://technet.microsoft.com/en-us/library/jj687745.aspx

Server ResourcesHow to Deploy the App-V 5.0 Server Using a Scripthttp://technet.microsoft.com/en-us/library/jj684302.aspx

How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Serviceshttp://technet.microsoft.com/en-us/library/jj713404.aspx

How to install the Reporting Server on a Standalone Computer and Connect it to the Databasehttp://technet.microsoft.com/en-us/library/jj684303.aspx

Server Deployment Resources (Cont.)How to Install the Publishing Server on a Remote Computerhttp://technet.microsoft.com/en-us/library/jj713416.aspx

How to install the Management Server on a Standalone Computer and Connect it to the Databasehttp://technet.microsoft.com/en-us/library/jj713469.aspx

How to install the App-V 5.0 Database and Management Server using SQL scripts on the DBhttp://blogs.technet.com/b/appv/archive/2013/05/06/how-to-install-the-app-v-5-0-database-and-management-server-using-sql-scripts-on-the-db.aspx

Sizing

Sizing Document Published!http://technet.microsoft.com/en-us/library/dn595131.aspx

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)A single reporting server can process 500 concurrent/active connections.A single reporting server can process a maximum 1500 concurrent connections.

Single Maximums

Sizing: MaximumsXML DataSupporting 500,000 client machines with:      5 publishing servers      2 reporting servers (caveat with 4 hours random delay)      2 management servers (for availability)      1 database

Package Manifest Size (# of files) and Extension Points affect time-to-publish as well.SP2 HF4 – PreserveUserIntegrationsOnLoginUE-V

Reporting DelayScheduled Task - 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.

Sizing: DB StretchServer Stretch 12,000 packages

Client Stretch2,500 packages on a single machine500 packages published to single user

Sizing: Management DatabaseSize of DB = (X+Y+Z) accelerated by Change History Growth.

X= Package Records + Aggregate of Manifests + Custom Configuration

[(# of packages * 512 Bytes) + (# of packages * 1Mb average manifest size) + (# of packages * 10K for custom configuration)]

Package Records = # of packages * 512 BytesAggregate of Manifests = # of packages * 1Mb average manifest sizeCustom Configuration = # of packages * 10K for custom configuration

Custom Configuration based on estimation from ( ½K per policy element; 12 elements); 2 policies per packages;)

Y= Package Entitlements: 1K per entitlement (group SID)Z = Connection Groups: 2K per CG.

Change History Estimation = 1K per record which correlates to instance. If 100 changes a week are estimated, factor in 100K growth.

Sizing: Reporting DatabasePlan for Growth:Launch Record - Averages 256-512 bytesClient Data (RDS and Desktops) - 512 bytesPackage and Package Groups (From Clients) - 1K

RDS will report a lot more :)

I was told there would be no math . . .

Sizing: ContentApplication AssetsPerformanceFile Server TuningNetwork Stack Tuning

Sizing: Shared Content StoreApplication LoadBandwidth, Bandwidth, Bandwidth

Application UseMemory, Memory, Memory

PublishingSparse File Creation adds to Publishing time

App-V 5’s Shared Content StoreDesignDesigned for VDI be it a Microsoft solution, Citrix solution, or the other one. Storage configuration on the back-end can be flexibleAgnostic to the RDS or VDI broker.

Sizing Variablesx of users + # of average apps runningAverage App Size in terms of assetsBandwidth for 1st launch will depend on average package size MLTAverage app memory requirementPersonas, Personas, Personas!

Drastic Disk Space ReductionIssues with Publishing Delaysreduced in App-V 5 SP2 HF4PreserveUserIntegrationsOnLogon

http://technet.microsoft.com/en-us/library/dn659478.aspx

Those Large Apps

Sizing: Network/StreamingHTTP/HTTPS Stream to DesktopExtranet StreamingVPN’sFB1 not really beneficial (APPX)

SMB 2.0SMB 3.0

Beware of the “AllowHighCostLaunch” Gotcha in Win8/8.1

USE THIS IN DATA CENTERS!!!!!

Sizing: RDSMemoryCPURDS Load Simulation: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c3f5f040-ab7b-4ec6-9ed3-1698105510ad

Session Host Capacity Planninghttp://www.microsoft.com/en-us/download/details.aspx?id=17190

DOC

High Availability and Fault Tolerant Technologies

Network Load BalancingProvides Scalability (App-V and IIS)http://technet.microsoft.com/en-us/library/dn343758.aspx#BKMK_IISLoadBal

WLB3rd PartyF5NetScalerCisco

Network Load Balancing Guide

http://technet.microsoft.com/en-us/library/cc754833(v=ws.10).aspx

http://technet.microsoft.com/library/hh831698

DOC

Failover ClusteringNo Data RedundancyReduces Mean-Time-Between-Failures (MBTF)Add Hyper-V Virtualization and Shared Storage to bring Live Migration (No MBTF) or VMWare Vmotion w/ Shared Storage if they insist on using ESXi

Failover Clustering Guide

http://technet.microsoft.com/en-us/library/hh831579.aspx

Creating a Windows Server 2012 Failover Cluster

http://blogs.msdn.com/b/clustering/archive/2012/05/01/10299698.aspx

DOC

DFS-RRedundant, Consistent, Replicated StorageCurrent Recommended Practice for Content Replication

Can be Combined with Failover ClusteringCreate a Shared Folder in a Clustered File Server http://blogs.msdn.com/b/clustering/archive/2012/05/01/10299698.aspxDeploying DFS Replication on a Windows Failover Cluster – Parts I, II, and IIIhttp://blogs.technet.com/b/filecab/archive/2009/06/29/deploying-dfs-replication-on-a-windows-failover-cluster-part-i.aspx

Don’t Stop There!Safely Virtualizing DFS-Rhttp://blogs.technet.com/b/filecab/archive/2013/04/05/safely-virtualizing-dfsr.aspx

MirroringDatabase TechnologyDuplicates Database StorageOften Leverages Log Shipping

DOC

Setting up SQL Mirroringhttp://technet.microsoft.com/en-us/library/ms189047.aspx http://msdn.microsoft.com/en-us/library/ms188712.aspx

Connection String Clarificationhttp://blogs.msdn.com/b/spike/archive/2010/12/08/clarification-on-the-failover-partner-in-the-connectionstring-in-database-mirror-setup.aspx

App-V SQL HA ResourcesSQL Failover Clusteringhttp://technet.microsoft.com/en-us/library/dn343758.aspx#BKMK_SQLCluster

SQL Mirroringhttp://technet.microsoft.com/en-us/library/dn343758.aspx#BKMK_SQLMirroring

Outages

SQL Data StoreRamification of service lossWorthless Management Server, Publishing Server is fine.Although Cannot Manage, Clients still can receive publishing information.

Possible Negative User ExperiencesNo new Entitlements

HA\LB CapabilitiesFailover ClusteringMirroring*

Content StoreRamification of service lossClients cannot Stream New AppsClients cannot launch Any Apps (in SCS Mode)

Possible Negative User ExperiencesClients are not able to use apps. Critical Business Down issue.

HA\LB CapabilitiesDFS-R ShareDFS-R couple with LBFile Share Cluster Resource (SCS)

http://technet.microsoft.com/en-us/library/dn343758.aspx#BKMK_ClusterSCSMode

Ugly Scenario

Management ServerRamification of service lossNo Management Console AccessPossible Negative User ExperiencesNo New EntitlementsHA\LB CapabilitiesLoad Balancing

Publishing ServerRamification of service lossClients Cannot Sync with ServerPossible Negative User ExperiencesNo New Applications, Errors Upon SyncHA\LB CapabilitiesLoad Balancing

In Review: Session Objectives And TakeawaysSession Objective(s): Identify the load-balancing, failover, replication, mirroring, and rapid provisioning options for various components of the App-V infrastructure.Implement recommended practices for streaming bandwidth management and Shared Content Store Design.Understand how to Architect App-V for Redundancy and Resiliency

WIN-B362: Project Virtual Reality Check: Microsoft App-V 5 Performance, Tuning, and Optimization (App-V PTO) - Thursday @10:15WIN-B355: The Circle of Life for an App-V 5.0 Package: From Sequence to Termination – Thursday @13:00WIN-B215: Deploying Microsoft App-V 5 and Citrix XenDesktop 7 – Thursday @14:45WIN-H309: Implementing App-V 5 in Microsoft System Center 2012 R2 Configuration Manager - HOL

Related Content

Windows Enterprise windows.com/enterprise windowsphone.com/business  

Windows Track Resources

Windows Springboard microsoft.com/springboardMicrosoft Desktop Optimization Pack (MDOP)

microsoft.com/mdop Windows To Go microsoft.com/windows/wtgWindows Phone Developer developer.windowsphone.com

“ I have nothing to offer but blood, toil, tears and sweat.”

-Winston Churchill

KITTY SELFIE!!!!!!!

Windows Enterprise windows.com/enterprise windowsphone.com/business  

Windows Track Resources

Windows Springboard microsoft.com/springboardMicrosoft Desktop Optimization Package (MDOP)

microsoft.com/mdop Windows To Go microsoft.com/windows/wtgWindows Phone Developer developer.windowsphone.com

ResourcesLearning

Microsoft Certification & Training Resourceswww.microsoft.com/learning

msdnResources for Developers

http://microsoft.com/msdn

TechNetResources for IT Professionals

http://microsoft.com/technet

Sessions on Demandhttp://channel9.msdn.com/Events/TechEd

Complete an evaluation and enter to win!

Evaluate this session

Scan this QR code to evaluate this session.

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.