Some Usefull Information about SCCM 2012

ConfigMgr went under the knife the past couple years. The result? An environment that can scale to unimaginable heights. CM2012 is built to manage any size environment.

Here’s some stats:

A Central Administration site supports up to 25 child primary sites. The site database (if using SQL Enterprise) supports up to 400,000 clients. If using SQL Standard – it supports up to 50,000 clients.

NOTE: Kenny Buntix has a nice “warning” about a CAS server and planning. Make sure you read through it if you are trying to determine if SQL Standard will be enough for you: Important SQL information for a Configmgr 2012 CAS and Primary site

A CM2012 Primary site supports up to 250 secondary sites. BTW: Plan your database location effectively. If the database is installed on the same server as the Primary site, it supports up to 50,000 clients, however, if you offload the database to another server it supports up to 100,000 clients.

On a standard install with appropriate hardware, a Secondary site supports up to 2,500 clients. By adjusting the hardware limits you can increase this a bit. The max client support on a Secondary site is 4,000 clients.

UPDATE 3/5/2012: Sherry Kissinger spoke with the docs team recently and they suggested that the max client support will be raised to 5,000 clients. See Sherry’s comment here: Can you promote Primary to CAS? I’ll update this post as soon as the communication from Microsoft takes place.

Management points in CM2012 are another area where planning is key. By itself, a single management point assigned to a single primary site can support up to 25,000 clients. Just by adding management points, you can bump up the supportability number by another 25,000 clients. A single primary site supports up to 10 management points, hence, a single primary *could* (with the proper specs and implementation) support up to 250,000 clients. A Secondary site only supports a single management point and that management point must be installed on the same server as the Secondary site. The Secondary site management point will only support as many clients as the Secondary site does.

As we get further down the CM2012 site system role checklist, its important to get a handle on your Distribution point layout. A Distribution point generally supports up to 4,000 clients, but its most important to understand how they can be distributed within the environment. Both a primary site and a secondary site support up to 250 Distribution points on their own, however, a primary site can support a combined total of 5,000 Distribution points, based on how the hierarchy (primary sites and secondary sites) is laid out.

When installed on the site server itself, a Software update point can support up to 25,000 clients, however, when installed on a computer remote to the site server, the Software update point supports up to 100,000 clients. In the CM2012 hierarchy, each site supports four Software update points.

The Fallback Status Point in CM2012 allows you to proactively manage client problems in the organization. And, while it is an optional server role, it is recommended. Each Fallback Status point supports up to 100,000 clients and each primary site supports one Fallback Status point.

Both the Application Catalog website point and the Application Catalog service point support the same number of clients (400,000), however, for optimum performance plan to only support 50,000 per role. Microsoft recommends installing both the website point and the service point on the same site system and multiple instances are supported on a single primary site.

In CM2012, the System Health Validator point supports up to 100,000 clients.

Those are some serious numbers thrown around, but the gist is that no matter what size organization you have, CM2012 can handle it. And, with proper planning, even the largest installations will be served.

Scalability numbers can seem a bit daunting, particularly for smaller organizations. But, the thing to remember is that a product like CM2012 can grow with you. It will support any size organization and offers deep features to maximize the environment and minimize management headaches.

File Copy Over Network Using VB-Script

‘ VBScript
Option explicit
Dim objFSO, strSourceFile, strTargetFile, booOverWrite, strResult
strSourceFile = “\\\Vasant\*.vbs
strTargetFile = “c:\Backup”
Set objFSO = CreateObject(“Scripting.FileSystemObject”)
If objFSO.FileExists( strTargetFile) Then
strResult = “The file exists, overwritten”
booOverWrite = vbTrue
objFSO.CopyFile strSourceFile & “\*”, strTargetFile & “\”, booOverWrite
strResult = “The file does not exist, created”
booOverWrite = vbFalse
objFSO.CopyFile strSourceFile, strTargetFile, booOverWrite
End If

Wscript.Echo strResult