Configmgr Sizing Worksheets

Hierarchy Planning Worksheet v2.2

DB Sizing Worksheet v2.2

Several years ago Kent A. and someone else put out a couple spreadsheets on database sizing and server sizing for Configmgr.  I used them off and on for a few years and over time I have revised them based on the newer SQL server best practices (SQL 2012 R2+).

In the days of SQL 2008 and earlier, the common db practice was to have multiple files for the configmgr database files (MDF & NDF files), while the TempDB was configured to use a single file (MDF file).  And all databse transaction log files (LDF Files) were configured to use single files alongside each database.

TempDB or tempdb database: Is a globally used file available and is used for holding temporary objects such as local and global tables, stored procedures, table variables, row versions, and query results. The tempdb is temporary, it gets recreated at each reboot or SQL service start.  It is literally empty at each start, all data is purged and the db cannot be backed up.  The tempdb.mdf is the data file, templog.ldf is the log file for the tempdb.  The tempdb autogrowth setting can cause serious performance issues if the size of the db is too small and it is constantly growing the db.  A common practice when running a SQL server in an Azure VM is to put the temdb files on the D drive since the drive is non-persistent during reboots.

The best practice for SQL 2012 R2 and beyond is to use a single database file for the Configmgr database and multiple files for the TempDB files (MDF & NDF files).  The transaction log files (LDF files) are still configured for a single file as before.  My buddy Steve Thompson points this out in a recent post where he discusses the proper tempdb creation practices.  Steve is also a former SQL MVP, now a Configmgr MVP so he knows both well.

The topic of using a CAS or multiple primaries for a customer came up on a discussion list today and when I replied I had screen shots of my sql sizing spreadsheet and my site sizing spreadsheet and a few people asked me for copies of them.  They can be downloaded now and as they get updated I will do my best to make the new versions available.

Any questions please let me know.

P.S. SQL should always be local.

Azure Active Directory Sync – Beta 2 Details

Azure AD Sync Beta 2 includes new features, scenarios, troubleshooting tools and improves stability.

New in Beta 2

    • Selective synchronization which enables you to only sync attributes required for the services you want to enable
    • AD password reset with multi-forests
    • Exchange hybrid deployment in multi-forests environments which enables you to have mailboxes in Office 365 as well as in your on-premises exchange

Sign up for the beta here.

Azure AD Sync Optional Features
Azure AD Selective Sync












More details can be read in Alex Simons post on the TechNet Blog

Fundamentals of Azure Internal Load balancers ILBs

Fundamentals of Azure Internal Load balancers by Bruno Terkaly 

  1. Internal load balancing (ILB) enables you to run highly available services behind a private IP address
  2. Internal load balancers are only accessible only within a cloud service or Virtual Network (VNet)
    • This provides additional security on that endpoint.

Some questions I am hearing

  1. I am able to access internal load balancer using IP address but not via load balancer or service name?
    • See Accessing the ILB below
  2. Is there any option on Azure portal to view load balancer configuration?
    • Internal load balancing cannot be configured through the portal as of today, this will be supported in the future
    • However, it can be configured using powershell cmdlets.
      • ILB can be used in a deployment inside a Regional Virtual Network as well in a new deployment that is outside the Virtual Network
  3. How do I monitor the traffic and which server it is redirecting it to?
  4. How do I setup the probing and rules/alerts for it?
    • See the links below


  1. Between virtual machines within a cloud service.
  2. Between virtual machines in different cloud services that are themselves contained within a virtual network.
  3. Between on-premises computers and virtual machines in a cross-premises virtual network.

Some diagrams


  1. Multi-Tier Web Appimage001

    Figure 1: Architecture for a Multi-Tier Web App


  1. Traffic from clients on the on-premises network get load-balanced across the set of LOB servers running in a cross-premises virtual network
  2. You don’t need a separate load balancer in the on-premises network or in the virtual networkimage002

    Figure 2: Architecture for an Intranet Network


  1. ILB also allows traffic from servers on the on-premises network to be load-balanced across virtual machines running in a cross-premises virtual network.image003

    Figure 3: Architecture for an On-Premises Network


  1. When used within a Virtual Network the ILB endpoint is also accessible from on-premises and other inter-connected VNets allowing some powerful hybrid scenarios



  1. VMs inside a cloud service have private IP address spaces
  2. You can talk to the ILB using this private IP address


  1. A customer can specify a static VNet IP address
  2. A customer can retrieve the load balanced IP is acquired from a virtual subnet
  3. This allows you to be connected VNets through the secure IP Sec tunnel

Some useful links

Regional Virtual Networks
Internal Load Balancing
Configure an internal load-balanced set
Azure Load Balancer
Configure a load-balanced set

Earn $200 AWS Credit for Evaluating Networking Solutions

AWS Marketplace

*Note: The AWS infrastructure fees for testing are NOT free.

Choose from one or more participants and eval their product for 120 hours or more and received $100 AWS credit.  Earn up to $200 by spending 120 hours on two products.

A10 Networks vThunder – 100 Mbps Base Operating System Linux/Unix, Other 2.7.1 P3 Delivery Method 64-bit Amazon Machine Image (AMI)
aiScaler Dynamic Site Acceleration & Traffic Manager Base Operating System Linux/Unix, Ubuntu 11.1 Delivery Method 64-bit Amazon Machine Image (AMI
Vyatta Virtual Router/Firewall/VPN Base Operating System Linux/Unix, Other 6.5R1 Delivery Method 64-bit Amazon Machine Image (AMI)
Cisco Cloud Services Router (CSR) 1000V – Advanced Technology Package Base Operating System Linux/Unix, Other Cisco IOS XE Delivery Method 64-bit Amazon Machine Image (AMI)
NetScaler VPX Platinum Edition – 10 Mbps Base Operating System Linux/Unix, FreeBSD 6.3 Delivery Method 64-bit Amazon Machine Image (AMI)
VNS3 3.5 Lite Edition Base Operating System Linux/Unix, Other 3.5 Delivery Method 64-bit Amazon Machine Image (AMI)
F5 BIG-IP Virtual Edition for AWS 200Mbps Hourly (Best) Base Operating System Linux/Unix, CentOS 5.6 Delivery Method 64-bit Amazon Machine Image (AMI)
Load Enterprise EC2 Base Operating System Linux/Unix, Amazon Linux Amazon Linux 2012.03 Delivery Method 32-bit Amazon Machine Image (AMI)
NGINX Plus – Amazon Linux AMI Base Operating System Linux/Unix, Amazon Linux 2014.03 Delivery Method 64-bit Amazon Machine Image (AMI)
SteelApp Traffic Manager Standard – 10 Mbps, 1000 SSL TPS Base Operating System Linux/Unix, Ubuntu 12.04 Delivery Method 64-bit Amazon Machine Image (AMI)
Silver Peak Cloud Acceleration – 10 Mbps Base Operating System Linux/Unix, Fedora Core 6/Kernel 2.6.38 Delivery Method 64-bit Amazon Machine Image (AMI)
Ishlangu Load Balancer ADC IS-BFG (Unlimited) Base Operating System Linux/Unix, Ubuntu 12.04 Delivery Method 64-bit Amazon Machine Image (AMI)














“PROMOTION – July 1, 2014 – July 31, 2014 – Subject to the Additional Terms, customers who activate a software free trial for any participating product by July 31, and use the product for a minimum of 120 hours during the software free trial (the “Offer”), will receive a $100 AWS Promotional Credit (“AWS Credits”). Limit two $100 AWS Promotional Credits per customer. To receive two $100 AWS Promotional Credits, you must meet the minimum use threshold with two different participating products. For qualifying customers, the Promotional Credit will be sent to the email address registered to their AWS Marketplace account. Restrictions apply; see full terms below for more details.”