The Biggest thing that comes to my mInd when I try to compare two versions of this wonderful Tool called SCCM ( System Center Configuration Manager ) is ” Cost Optimization ( Cost Efficient ) ” .
True !! As the Above Figure Shows : SCCM 2012 is without any doubts ” Cheaper , Faster and Good ” 🙂
SCCM 2012 is a more Cost Efficient Solution as compared to SCCm 2007 . Why ? Well !! this question must have hit your Mind by now !!
The Answer is here :
Multiple Forests Support with One SCCM Primary , Role Based Access Control ( In SCCM 2007 there were certain scenarios where you might have Different Sites for Managing Server and Clients Machines ) , Not Anymore with SCCM 2012 RBAC( Role Based Access Control ) feature .
Multiple Language Support is yet another reason where you might not need Extra SCCM Sites .
In this Post we will talk about a new Feature that was not there in SCCM 2007 . It is ” SCCM Forest Discovery Method” . Let us assume that you are being asked to Implement SCCM 2007 in an environment where you have two forests , then since there is no in place method , you might need to do some extra work . However , with Active directory forest discovery method being introduced in SCCM 2012 , all you have to do is to Enable the SCCM Forest Discovery method and you are done . The System Center Configuration Manager Forest Discovery method can help you identify as many forests as you can . So , now you can have just one SCCM Server and Manage Multiple Forests ( Subject to other conditions being true) . Let us have a look at the below figure :
yes , this is what you will say when you will come to know that you would no longer need to edit the ugly looking SMS_def.mof files for customization in Hardware Inventory !! All you need to add some new data in hardware is using the below Pop Up :
I already tweeted last week that I really, really like the new Distribution Points in ConfigMgr 2012. Around that time they started writing some really good posts at the ConfigMgr OSD Blog about the new Distribution/PXE Point and Content Management. Even though these posts give really good information I still feel like I have to write down what I really, really like about it. So in this post I will sum up some of the cool new features/ properties of the new Distribution Point in ConfigMgr 2012.
Distribution Point Role: The Distribution Point Role is now merged into one single type that can be used on workstations and server. Also there is now the ability to choose (and prioritize) two drives for the use of the Distribution Point. To me this is a logic choice as there are now no vague difference anymore in what is supported with which type of Distribution Point.
PXE Service Point Role: The PXE Service Point is now a property of a Distribution Point. To me this is a logic choice, as there was always a Distribution Point needed when there was a PXE Service Point. Besides that it also saves a lot of confusion, because of the extra Server Share Distribution Point that got created (SMSPXEIMAGES$). Adding a Boot Image to the RemoteInstall folder of WDS is now just a property setting of a Boot Image (Deploy this boot image from the PXE Service Point).
Distribution Point Groups: The Distribution Point Groups functionality got a really nice update too. It can still be used to distribute content to multiple Distribution Points at the same time, but now it also directly distributes content (assigned to the group) to new members of the group. To me this is a really nice (and very logic) additions to this functionality, because now all the members of a group always have the same content assigned to it.
Content: The Distribution Point now has the option to show all the content that is assigned to. It also gives the option to validate the content and to manage (redistribute or remove) the content. Also the possibility to validate the content is added. This means as much as, the hash of the content will get checked on a schedule. When the has doesn’t mach this will be reported, but not “fixed”. To me this is a great addition to finally be able to quickly see the assigned content to a Distribution Point. Also no hash mismatches anymore! Well… if the content gets checked on a regularly base and (manual) actions will be taken.
Content Library: The Distribution Point now stores the data in the Content Library (SCCMContentLib). This library is divided in three parts, Data Library (DataLib), File Library (FileLib) and Package Library (PkgLib). The Data Library stores Metadata about files, the File Library stores actual files and the Package Library stores references to files. To me this looks like a good solution to prevent the many different times (and locations) that where used to store data on a Distribution Point.
Boundary Groups: The Distribution Point now gets protected by adding a Boundary Group directly to it. And a Boundary Group can contain multiple Boundaries. To me this is a not necessary addition, because now there will always be the need to create a Boundary Group to be able to create a Protected Distribution Point.