Presentation on theme: "Capacity Planning: App-V BPA:"— Presentation transcript:
Capacity Planning: App-V BPA: Performance Guidance (SP2 HF4): App-V Supported Configurations : Planning for Server Deployment:
Local Desktop Virtual Desktop End Point
License Management by App-V Management Server Feature tied to legacy protocol Provider Policies Create another access layer that created many support incidents Application Permissions Use Applocker Policies Text Logging Logging: Now Decentralized and ETW-based Canned Reports within Management Interface Use SSRS or your favorite report viewer instead
You manage web services IIS console is operations management and troubleshooting resource Services run as worker processes
1.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.
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.
Scheduled 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.
Server Stretch 12,000 packages Client Stretch 2,500 packages on a single machine 500 packages published to single user
Size 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 Bytes Aggregate of Manifests = # of packages * 1Mb average manifest size Custom 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.
Network Load Balancing Guide
Failover Clustering Guide Creating a Windows Server 2012 Failover Cluster
Setting up SQL Mirroring Connection String Clarification on-the-failover-partner-in-the-connectionstring-in-database- mirror-setup.aspx
Microsoft Desktop Optimization Pack (MDOP) microsoft.com/mdop