Install multiple management points at each primary site, and enable the sites to publish site data to your Active Directory infrastructure, and to DNS. Multiple management points help to load-balance the use of any single management point by multiple clients. In addition, you can install one or more database replicas for management points to decrease the CPU-intensive operations of the management point, and to increase the availability of this critical site system role. You can install only one management point in a secondary site, which must be located on the secondary site server. If this management point is unavailable, clients can fall back to using a management point in their assigned site. [note]<http://i.technet.microsoft.com/dynimg/IC101471.gif>Note
Mobile devices that are enrolled by Configuration Manager can connect to only one management point in a primary site. The management point is assigned by Configuration Manager to the mobile device during enrollment and then does not change. When you install multiple management points and enable more than one for mobile devices, the management point that is assigned to a mobile device client is non-deterministic. If the management point that a mobile device client uses becomes unavailable, you must resolve the problem with this management point or wipe the mobile device and re-enroll the mobile device so that it can assign to an operational management point that is enabled for mobile devices. From: [email protected] [mailto:[email protected]] On Behalf Of Dzikowski, Michael Sent: Monday, July 01, 2013 9:37 AM To: [email protected] Subject: [mssms] RE: Sizing Question One thing I see is, you really don't need the load balancers for your MP roles in ConfigMgr 2012. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Crown, David T. (DTI) Sent: Monday, July 01, 2013 9:33 AM To: '[email protected]' Subject: [mssms] Sizing Question I know it being Monday and all, I'm wondering if you find folks wouldn't mind double checking my sizing. I changed roles with my employer, and the scale of the configmgr environment I'm used to supporting has grown quite a bit. I'm looking to migrate about 15K, scaling to a potential of 40K, clients from a 2007 and a 2012 (with a CAS for political reasons) to a single 2012 site. The plan is to use a box with 16 cores and 48GB (the plan is get it to 96) of ram with SQL on box and no other roles. For the backing disks, I was looking at three Fibre Channel Luns. One 300~500 gig disk on a high performance lun that can sustain 20K IOPS for the site directory and sql, one 2TB lun on some lower preforming storage for package source and the content library, and a third lun in the same lower performance tier (~1TB) for my backups. I plan on using two to four MP's as vm's behind a load balancer, two unprotected DP's for failback, and one SUP. As the environment is deployed, I plan on bringing in protected DP's, and for my larger sites (500 to 1000 users), I plan on sticking a secondary at the site. So my question is does my proposed environment look like it could support the number of clients I'll be managing?
<<inline: image001.gif>>
