I went into this breakout session not thinking much of it and assuming it would give me a little bit of information but not enough to really squelch the hunger for knowledge. I must say, this session was right on the mark when giving information about the new functionality of roles and communications between them with examples (not shown). As you continue to read on, you will find this new hierarchy is something to really pay attention to with a set of possibilities to lower your cost of ownership and really assist your WAN group with some serious changes that can make a major impact for the larger corporations.

Site Server Characteristics

Central Administration Site

    • Do not need a hierarchy and still support a single site
    • You can create an off-load reporting and administration site for the primary site.
    • For Upgrade, will need new hardware

Primary Site

    • Primary sites are needed to manage any clients
    • Scale more than 100,000 clients
    • Reduce impact of primary site failure
    • Local point of connectivity for administration
    • Political (local or government)
    • Content regulation (the need to separate content by individual locations or groups)

When do I not need a primary site?

  • Decentralized administration
  • Logical data segmentation
  • Client agent settings (can be defined on a collection basis (Custom Client Agent Settings)
  • CAS – Default client Agent Settings
  • CAS – Custom Client Agent Settings
  • CAS – Conflict Resolution that is priority-based model
  • CAS – Resultant Settings can be an aggregation of both default and customer settings.
  • Language (using MUI in beta 2)
  • content routing for deep hierarchies


Secondary Site

    • Bundle Proxy MP and DP for install
    • Tiered content Routing Via Secondary’s
    • SQL Needed, by default SQL Express will be installed unless otherwise stated.

When do I need a secondary site

  • No local Administration
  • If you need to manage traffic


Distribution Points

    • When do I need a DP? Overall, this is the same as ConfigMgr 2007
    • NEW!  Remote DP’s will have throttling and scheduling as like ConfigMgr 2007 secondary

Replication (talking about the new replication)

Replication in v.Next is now thought in 3 different types of replication (SQL), Global Data (SQL), Site Data, and Content (File-based).


  • Content Routing can allow secondary’s to replicate between the two sites.
  • v.Next now has a Topology map that is interactive showing trouble spots by color.
  • v.Next has Database Replication has for for link status and replication.

    Security Settings (ALL NEW!)

    Security settings are easier now! Role-Based Administration is configured through Security Role (Contains Permission (e.g. Read Package), Security Scope (Contains securable objects), and Administrator. This works a little different since you will have a central site and the primary sites. The Central Site is where all of the Administration and reporting purposes sit. Then you can put Primary Sites at locations where you need a separate ConfigMgr site, however, this does connect back to the Central (primary) site and is lower within the hierarchy.

     Minimum hardware and software requirements for ConfigMgr v.Next

    • 64-bit hardware for all site servers and site system roles
    • MS SQL server 2008 SP1 with CU6 (64-bit)
    • Windows Server 2008 (64-bit)

    If you want to start preparing for ConfigMgr v.Next, start looking at flattening hierarchy where possible

    • Plan for Windows Server 2008, SQL 2008, and 64-bit
    • Start Implementing Branch Cache with ConfigMgr 2007 SP2
    • Move from Web reporting to SQL Reporting Services