- Customer requirements and capacity planning
- Hypothetical examples
- Using SMS Capacity Planner to meet service level agreements
SELECT * FROM replicatedobjects WHERE sitesystemrole = ‘MP’
(Total Package Size) × (Percentage of Software Distribution) / (Bandwidth).
- Do not deploy more than 100 DPs per site, and use considerably fewer over slow, unreliable networks (slower than 256Kbps) or in high software distribution environments (which will require frequent distributions of numerous large applications).
- Never deploy more than 500 secondary sites per primary site and generally try to keep this ratio to approximately 250 or 300 to 1. Remember that the primary site has to replicate all software distribution packages to all child sites. This best practice is especially critical over slow or unreliable links.
- If the company regularly deploys a number of large applications, you will find that a secondary site-based solution will generally prove more efficient than just a DP alone.
- Secondary site overhead increases in proportion to the number of collections, packages, and advertisements at the parent primary site.
- A secondary site can support up to 5,000 clients, depending upon connection performance to the parent site, company SLA requirements, and server hardware.
- A primary site can support 100,000 directly assigned advanced clients (although this number will be considerably less with legacy clients), depending upon connection performance to parent and child servers, company SLA requirements, and server hardware.
- A central site server can support 200,000 indirectly reporting clients (not utilizing the site server database for advertisement requests), depending upon connection performance to child servers, company SLA requirements, and server hardware.
One of the great things about the Capacity Planner tool is it allows you to change column values (see Figure A) and then reevaluate all or just one location. This allows the user to perform what-if analysis by modifying such options as increasing/decreasing bandwidth, increasing/decreasing the number of client machines at a location, and deciding whether to locate an administrator at a particular location (and thus enabling an SMS primary site to be located at that location).
- The shorter the SLA, the closer the administrative site server (the one used to initiate the software distribution) should be to the receiving clients.
- The shorter the SLA, the smaller the DP to client ratio should be. DPs can typically support up to 4,000 clients per hour (in optimal network and performance conditions) for emergency/patch applications. For larger packages though, this limit can be a good deal lower. It’s always best to err on the side of caution.
- The shorter the SLA, the shorter the policy request polling interval should be. Remember that this affects the MP scalability support statement.
- The shorter the SLA, the flatter the SMS hierarchy should be. Fewer tiers to replicate advertisements and packages results in better SLAs.
- TechNet Events: Planning and Deploying Systems Management Server 2003
This webcast presents the best practices for deployment and introduces the tools available to assist you with your SMS 2003 installation.
- Planning and Deployment FAQ
This site includes frequently asked questions that arise during SMS planning and deployment.
- Scenarios and Procedures for SMS 2003: Planning and Deployment
Here you’ll find sample scenarios and recommended best practices to help you in deploying SMS.
- TechNet Webcast: Planning and Deploying SMS 2003 (Level 200)
This online webcast gives an overview of SMS planning and deployment, as well as a demonstration of the SMS 2003 Capacity Planner.