Hi, I'm having trouble with a new installation of the RC of System Center 2012 Configuration Manager. Everything installed fine, computers and users are discovered, but the site component manager is failing to install and i can't find the reason neither in the event viewer nor in the mpMSI.log file. Event Viewer is logging: (Event ID: 1016) On 10/31/11 09:02:25, component SMS_SITE_COMPONENT_MANAGER on computer SERVER9B.SISTEMASESCO.COM reported: Site Component Manager failed to install this component on this site system. Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in minutes. To force Site Component Manager to immediately retry the installation, stop and restart Site Component Manager using the Configuration Manager Service Manager. However none of the previous entries give any useful information. I even tried to install it manually but still fails without giving any clue at all... I anyone can shed any light on this, i'll appreciate it. Searching for the "Return Value 3" inside the mpMSI.log, yields the following: Action start 10:24:41: CcmMigratePolicySettingsInit. [10:24:41] Getting settings from WMI and storing in C:\Program Files\SMS_CCM\polmig.mof MSI (s) (78:48) [10:24:41:668]: Machine policy value 'DisableRollback' is 0 MSI (s) (78:48) [10:24:41:668]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 10:24:41: CcmMigratePolicySettingsInit. Return value 3. Some extra info: Single Server Installation. Windows 2008 SP2 x64 SQL Server 2008 R2 SP1. All the prerequisites were met. Best regards, Alan

Problem solved ! http://social.technet.microsoft.com/wiki/contents/articles/4709.aspx Cause: ConfigMgr 2007 Client was installed on this machine previously. It was uninstalled using Programs and Features but some 'part' remain in system. Resolution: Run ccmsetup /uninstall (you could find a ccmsetup in '%systemroot%\ccmsetup' folder) and restart a site server.