SCCM 2012 Replication Data

From SCCM 2012 site to site replication is moved to SQL replication, Where as in SCCM 2007 it was file based.

Below chart explains the What kind of Data type will be replicated between sites with Replication Types.


What is there in Global Data & Site Data ?


When do we need a CAS (Central Administration) 2012 Site

  • If you have more than one Primary Site in a single hierarchy
  • For Central Reports and administration for your primary sites management.

Question:- Can i install CAS on existing SCCM 2007 Server?

No it is recommended to install on new (hardware) box

When do we need a local Distribution Point? In SCCM 2012?


Below are the three key points to consider a local distribution Point’s

  • BITS not enough to control the WAN traffic
  • Multicast for Operating System Deployment
  • To stream APP-V Applications

Ok..  Now when we do not need a local Distribution points in SCCM 2012?

Below are the key considerations…

  • Clients are well managed with-in BITIS provided control for WAN traffic
  • If BranchCache deployed(below points are pre-requirements for BranchCache)
    • DP’s on 2008 R2
    • Vista Sp2 with KB960568 and above OS’s(windows7 & 8)

Note:- Distribution Point role can be enabled on Client OS or Server OS.
Note:- Branch Distrubution Point Role is removed in SCCM 2012.

When do we need a Secondary Site – SCCM 2012


Below are the three key considerations to setup a secondary site.

  • To manage Upward-flowing WAN traffic
  • Tiered content Routing for deep network topologies
  • No local administrators

When do I need SCCM 2012 Primary Site?

To Manage Clients/Devices
Add More Primary sites for

  • To scale more than 100,000 Clients
  • Reduce impact of primary site failures in case of DR(Disaster recovery)
  • Local Point of Connectivity for Administration & Political Reasons
  • Content Regulations

Ok….. When you do not need a primary site compared with SCCM 20007 ?

  • Decentralized administration
  • Logical data segmentation
  • Client settings
  • Language Settings
  • Content routing for deep hierarchies

What is Empower Users in SCCM 2012


Enabling any device from any where

Changes from SCCM 2012 to SCCM 2012 SP1

Below are the changes from SCCM 2012 to SCCM 2012 SP1


What is Windows To Go?

Windows To Go is a feature in Windows 8 Enterprise that allows Windows 8 Enterprise to boot and run from mass storage devices such as USB flash drives and external hard disk drives.It is a fully manageable corporate Windows 8 environment. Using Group Policy, Windows Store can be enabled for a Windows To Go workspace (limited to one PC) and Store apps can be used on that workspace.

Is windows 8 supported for sccm ?

Yes from sccm 2012 sp1. The bad news is windows xp no more supported.

Read this related to windows 8 support .... Into

One of the most significant changes is support for Windows 8 for Configuration Manager clients. Configuration Manager SP1 supports Windows 8 in the following ways:

You can install the Configuration Manager client on Windows 8 computers and deploy Windows 8 to new computers or to upgrade previous client operating versions. Configuration Manager also supports Windows To Go.

You can configure user data and profiles configuration items for folder redirection, offline files, and roaming profiles.

You can configure new deployment types for Windows 8 applications, which support stand-alone applications (.appx files) and links to the Windows Store.

Configuration Manager supports Windows 8 features, such as metered Internet connections and Always On Always Connected.

What is not changed in sccm 2012 when compared with sccm 2007 ?

Wake on LAN

Windows Embedded devices

The Active Directory schema extensions for System Center 2012 Configuration Manager are unchanged from those used by Configuration Manager 2007. If you extended the schema for Configuration Manager 2007, you do not need to extend the schema again for System Center 2012 Configuration Manager.

What is Application management in sccm ?

Provides a set of tools and resources that can help you create, manage, deploy, and monitor applications in the enterprise.

Why you want sccm ?

You can perform all below with help of sccm:

Deploy operating systems, software applications, and software updates.

Monitor and remediate computers for compliance settings.

Monitor hardware and software inventory.

Remotely administer computers.

Migrate reports from SCCM 2007 to SCCM 2012

sync SSRS report between two report servers:

The built-in migration wizard in ConfigMgr 2012 can migrate most objects but not reports. In ConfigMgr 2012 classical ASP reports (as we know them from earlier versions) are no longer supported.
Migrate the classical reports to SQL Reporting Services in SCCM 2007
Below is a walk thru of how you migrate your existing classical reports to SQL reporting Services in SCCM 2007. Notice that you will still be able to run all classical reports after the migration.
  1. On you SCCM 2007 site server install either SCCM 2007 R2 or SCCM 2007 R3, both will add SQL Reporting Services support for SCCM 2007.
  2. In the ConfigMgr. console, navigate to Site Database, Site Management, A01 (where A01 is the sitecode), Site Systems. Right click the Site system server that will become a Reporting Services Point and click New Roles. Select Reporting Services Point and finish the wizard using the default values. 
  3. In the ConfigMgr. console, navigate to Site Database, Computer Management, Reporting, Reporting Services, and expand the node.
  4. Right-click SCCM1 (where SCCM1 is the name of your server), and then click Properties.
  5. On the Data Source Settings tab, specify SCCM1 as the database server and SMS_A01as the database name (where SMS_A01 is the name of your SCCM 2007 database. ClickTest.
  6. On the Data Source Authentication tab, select Windows integrated security.
  7. Click OK.
Copy reports to SQL Reporting Services
  1. Right-click SCCM1, and select Copy Reports to Reporting Services.
  2. On the Data Source Settings page, accept the default settings, and click Next.
  3. On the Data Source Authentication page, accept the default settings, and click Next.
  4. On the Select Reports page, accept the default settings, and click Next.
  5. On the Security page, accept the default settings, and click Next.
  6. On the Summary page, click Next.
  7. On the Progress page - once all of the reports have copied - click Next and then clickClose.
Migrate the SCCM 2007 reports to SCCM 2012
You can’t use the built-in migration tools to migrate reports from SCCM 2007 to SCCM 2012. This leaves you with two choices; 1) Download each RDL file one by one from SCCM 2007 and upload them to SCCM 2012 or 2) Use one of the free community tools that can download multiple folders at the time. In my last project I used this tool – ReportSync - to assist me.
  1. Launch ReportSync
  2. In Source server type in the name of the SCCM 2007 Report server in form of http://CM01/ReportServer. Provide credentials and click Load
  3. In Destination server type in the name of the SCCM 2012 Report server in form of http://CM02/ReportServer. Provide credentials and click Load
  4. Select the folders or individual reports you want to migrate and click Sync
  5. Once the process is finished click OK and your reports are now ready in SCCM 2012.
  6. This tool keeps the old Data source which will generate an error the first time you run the report.
  7. Open the report properties (by clicking on the report link)
  8. Select Data Sources, click Browse and select the shared SCCM 2012 data source. The data source is found in Home\ConfigMgr_Sitecode. The data source is the object with long GUID. Select the data source click OK and Apply.
  9. Run the report and verify that it works. There is no guarantee the all SCCM 2007 reports work out of the box in SCCM 2012.

Download link :

All credits goes to Kent.