Top five features in System Center Configuration Manager 2. Earlier this month Microsoft released System Center Configuration Manager 2. RC to TAP customers. A Release Candidate RC is feature complete code that has the potential to be the final RTM code unless any unexpected bugs emerge. This means that we are getting close to a final product. Ive worked with SMS and SCCM since 1. Beta 2 was released at MMS in March, Ive been getting familiar with SCCM 2. Microsoft has made it extremely easy to get your feet wet by providing the download of SCCM 2. Beta 2 in a prebuilt Hyper V virtual machine. There is a lot of great new functionality in the new version but I will limit myself to what, in my opinion, are the top five new features. User centric management. One of the big themes in SCCM 2. User Centric Management. This theme is carried forward throughout the product. Software distributions can now be targeted at users rather than just at devices. Zx27AGpFII/UpMjmUkbfZI/AAAAAAAADYw/P-Xu6AXmkQs/s1600/8.png' alt='Install System Center Configuration Manager 2012 Client' title='Install System Center Configuration Manager 2012 Client' />Think about a call center or a security desk, where multiple users share the same hardware. Previously when targeting a software distribution, SCCM limited you to collections based on systems but now software distributions can be directed at specific users or groups of users. Additionally, users can define a primary device or you can set up rules to determine a primary device and have a different software policy for primary and non primary devices. Consider the scenario where a manager logs onto a subordinates workstation temporarily, if the system is not designated as his primary device, any applications specifically targeted at managers primary devices, will not be available to him on that system. Configuration settings remediation. Desired Configuration Monitoring has been available since SMS 2. Desired Configuration Management and enhanced in SCCM 2. The ability to report and alert on compliance has been useful in monitoring and managing configuration drift. SCCM 2. 01. 2 takes the concept of managing configuration drift to the next level. First of all, the feature is now called Configuration Settings and can be applied to desktops, servers, mobile devices and users see point one above. My favourite new functionality is the ability to remediate WMI, registry, and script settings that are not compliant. Automated remediation can drastically reduce the time that a non compliant configuration stays out of compliance. Collection based configuration settings. In SMS and SCCM 2. If different client agent settings are required for different devices then a separate site is required. Install System Center Configuration Manager 2012' title='Install System Center Configuration Manager 2012' />Consider an environment where developers machines would have minimal agents inventory only perhaps, or where servers have different requirements. In SCCM 2. 01. 2, client settings can be customized and targeted at specific collections within the same site. This will reduce the complexity of many site hierarchies. Dependency based software distribution. In SMS and SCCM 2. Typically, an administrator would create a collection that meets the pre requisites for the application being deployed using a query and then associate the package to the collection with a n advertisement. This worked fine when the paradigm was device centric as long as the collection was built correctly. With user centric software distribution, it can be difficult to determine which device a particular software distribution will ultimately be targeted at. In SCCM 2. 01. 2 Requirement Rules andor Global Conditions are used to specify preconditions for a deployment such as available hardware e. Office must be installed as a prerequisite for Office SP1, user affinity Is this the users primary device. This is a much more elegant approach to application management, especially when coupled with the new concept of Deployment Types. An application can have multiple deployment types such as an upgrade, uninstall, virtual app, local install, mobile device version and the deployment type can be triggered based on the Requirement Rules or Global Conditions. Software Center and Application Catalog. Keeping with the user centric theme, the Software Center and Application Catalog is essentially an application that allows users to set some configurable settings as well as request  and install available applications. This App Store model can minimize some of the challenges associated with managing devices and applications for mobile technology savvy users that are used to fending for themselves. Note Some of the terminology may change between Beta 2 and RTM. These are my current favourite features but as time goes on I might find others that deprecate these. Over the next few months, Ill be sharing some more of my SCCM 2. Do you have a favourite new SCCM feature Is there a feature that you have been waiting forCM1. SP1 Management Point will not install on Server 2. Hi,I am using Windows Server 2. SQL 2. 01. 2 SP1 and SCCM 2. I have one Primary site with a remote site server that will host the DP and MP role. I am trying to install the Management Point using HTTP for client connections but it fails. SCCM 2. CM0. 7 and that was the in the end the issue. The CM0. 7 client left traces. I recently posted how to delete work items in bulk in System Center 2012 Service Manager SCSM and in that post, promised I would post how to do the same with. Or How I learned to stop worrying when Configuration Manager didnt show up in the Control Panel So Ive been playing with Windows Thin PC lately at the. System Center Operations Manager SCOM is a crossplatform data center monitoring system for operating systems and hypervisors. It uses a single interface that shows. Installing Update 1706 of System Center Configuration Manager,SCCM version 1706,install configuration manager update 1706,SCCM update 1606. System Center Configuration Manager Upgrade Paths, SCCM 2012 R2 upgrade paths for system center configuration manager,SCCM upgrade paths. Looking throught the msisetup log which said a previous version was detected, I used ccmsetup uninstall to remove the client which gets rid of it from control panel, and then removed the MP, rebooted and tried to install the MP again. However, the MP still wouldnt install. Failed to compile D SMSCCMCcm. ExecGlobal. mof Phase 3, Object 5, Lines 7. Error 8. 00. 41. Compiled D SMSCCMCCMVDI. Compiled D SMSCCMccmauthmessagehook. Compiled D SMSCCMLocation. Services. mof 9 5. Compiled D SMSCCMNetwork. System Center 2012 Configuration Manager introduces many exciting new features for deploying software that benefit both administrators and end users. With. How to Install a System Center Configuration Manager 2012 Primary Site Beta 2. Install System Center Configuration Manager 2012 Sp1' title='Install System Center Configuration Manager 2012 Sp1' />Config. Failed to compile D SMSCCMPolicy. Defaults. mof Phase 3, Object 4, Lines 4. Error 8. 00. 41. Compiled D SMSCCMPolicy. Agent. Events. mof 9 5. Failed to compile D SMSCCMState. Msg. Schema. mof Phase 3, Object 6, Lines 8. Error 8. 00. 41. Failed to compile D SMSCCMData. Transfer. Service. Phase 3, Object 5, Lines 3. Error 8. 00. 41. Compiled D SMSCCMCcm. SCCM 2016 Training 01 System Center Configuration Manager SCCM 2016 Videos Training. Install System Center Configuration Manager 2012 ConsoleExecMPFramework. Compiled D SMSCCMSms. Common. mof 9 5. Compiled D SMSCCMXml. Store. mof 9 5. Compiled D SMSCCMInventory. Agent. Events. mof 9 5. Compiled D SMSCCMSWMtr. Events. mof 9 5. Compiled D SMSCCMSWDist. Events. mof 9 5. Compiled D SMSCCMSrc. Update. Events. mof 9 5. Compiled D SMSCCMPatch. Mgmt. Events. mof 9 5. Compiled D SMSCCMSMSNap. Events. mof 9 5. Compiled D SMSCCMMp. Status. Forwarder. Defaults. mof 9 5. Failed to compile D SMSCCMCcm. ExecMP. mof Phase 3, Object 1, Lines 3. Error 8. 00. 41. Compiled D SMSCCMmppss. Compiled D SMSCCMmpccm. Config. mof 9 5. Compiled D SMSCCMmpccm. ConfigDefaults. mof 9 5. Compiled D SMSCCMMp. Events. mof 9 5. Compiled D SMSCCMOSDEvent. Classes. mof 9 5. Compiled D SMSCCMDPStatus. Compiled D SMSCCMImg. Deploy. Events. mof 9 5. Compiled D SMSCCMDCMClient. Events. mof 9 5. Compiled D SMSCCMSUMEvents. Compiled D SMSCCMOOBMgmt. Events. mof 9 5. Compiled D SMSCCMPwr. Events. mof 9 5. ERR 2. MSI s 8. C 1. C 0. Product Config. Mgr Management Point Error 2. Setup was unable to compile the file Ccm. ExecGlobal. mof The error code is 8. Error 2. 51. 40. Setup was unable to compile the file Ccm. Free Download Adobe Flash Player For Netbook Review. ExecGlobal. mof The error code is 8. Custom. Action Ccm. Register. Wmi. Mof. File returned actual error code 1. MSI s 8. C 7. Note 1 2. MSI s 8. C 7. User policy value Disable. Rollback is 0 MSI s 8. C 7. 0 0. 9 5. Machine policy value Disable. Rollback is 0 Action ended 0. Install. Finalize. Return value 3. MPsetup. SMSMP Setup Started. Parameters D SCCMbinx. SCCM0. 1 SMSMP 0 lt 0. Installing Pre Reqs for SMSMP lt 0. Installing Pre Reqs for Role SMSMP lt 0. Found 2 Pre Reqs for Role SMSMP lt 0. Pre Req MSXML6. 0 found. No versions of MSXML6. Would install new MSXML6. Enabling MSI logging. D SCCMlogsmsxml. MSI. Installing D SCCMbinx. Installation was successful. Pre Req Sql. Native. Client found. lt 0. Sql. Native. Client already installed Product Code D9. DDE0. F8 0. CFD 4. C0. F 8. A0. 7 C8. DE4. 7FF4. D. Would not install again. Pre Req Sql. Native. Client is already installed. Skipping it. lt 0. Completed Installation of Pre Reqs for Role SMSMP lt 0. Installing the SMSMP lt 0. Passed OS version check. IIS Service is installed. No versions of SMSMP are installed. Installing new SMSMP. Enabling MSI logging. D SCCMlogsmp. MSI. Installing D SCCMbinx. CCMINSTALLDIRD SMSCCM CCMSERVERDATAROOTD SCCM USESMSPORTSTRUE SMSPORTS8. USESMSSSLPORTSTRUE SMSSSLPORTS4. USESMSSSLTRUE SMSSSLSTATE6. CCMENABLELOGGINGTRUE CCMLOGLEVEL1 CCMLOGMAXSIZE1. CCMLOGMAXHISTORY1 lt 0. Backing up D SCCMlogsmp. MSI. log to D SCCMlogsmp. MSI. log. Last. Error lt 0. Fatal MSI Error mp. Role. Setup. lt 0. Solution I ran ccmclean, didnt work for me initially. But this did the trick In an elevated Powershell window, run this Get WMIObject namespace root query SELECT FROM Namespace where name ccm remove wmiobject. It removes any last trace of CCM from WMI. In my case Id already uninstalled an old client and scoured the machine for any file or registry traces of ccm, but finally this worked. Hope it helps ,Kenny Buntinx.