I was installing SQL Server 2012 RTM on my Windows Server 2008 R2 SP1 machine. I selected the following option on Setup Role:

I selected all features that are available:

I went ahead and choose the default values on all the screens, and here is the System Configuration Check

report that got generated:

Rule Name		Rule Description	Result	Message/ Corrective Action
GlobalRules: SQL Server 2012 Setup configuration checks for rules group 'GlobalRules'
	NoRebootPackageDownLevel	This rule determines whether the computer has the required update package for .NET Framework 2.0 or .NET Framework 3.5 SP1 that is needed for a successful installation of Visual Studio components that are included in SQL Server.	NA	This rule does not apply to your system configuration.
	ServerCore64BitCheck	Checks if this version of SQL Server is 64bit.	NA	This rule does not apply to your system configuration.
	ServerCorePlatformCheck	Checks if this version of SQL is supported on the currently running Windows Server Core OS.	NA	This rule does not apply to your system configuration.
	AclPermissionsFacet	Checks if the SQL Server registry keys are consistent.	P	SQL Server registry keys are consistent and can support SQL Server installation or upgrade.
	HasSecurityBackupAnd DebugPrivilegesCheck	Checks whether the account that is running SQL Server Setup has the right to back up files and directories, the right to manage auditing and the security log and the right to debug programs.	P	The account that is running SQL Server Setup has the right to back up files and directories, the right to manage auditing and security log and the right to debug programs.
	MediaPathLength	Checks whether the SQL Server installation media is too long.	P	The SQL Server installation media is not too long.
	NoRebootPackage	This rule determines whether the computer has the required update package for .NET Framework 2.0 or .NET Framework 3.5 SP1 that is needed for a successful installation of Visual Studio components that are included in SQL Server.	P	This computer has the required update package.
	RebootRequiredCheck	Checks if a pending computer restart is required. A pending restart can cause Setup to fail.	P	The computer does not require a restart.
	SetupCompatibilityCheck	Checks whether the current version of SQL Server is compatible with a later installed version.	P	Setup has not detected any incompatibilities.
	ThreadHasAdmin PrivilegeCheck	Checks whether the account running SQL Server Setup has administrator rights on the computer.	P	The account running SQL Server Setup has administrator rights on the computer.
	WmiServiceStateCheck	Checks whether the WMI service is started and running on the computer.	P	The Windows Management Instrumentation (WMI) service is running.
InstallGlobalRules: SQL Server 2012 Setup configuration checks for rules group 'InstallGlobalRules'
	ServerCoreBlock UnsupportedSxSCheck	Checks if an earlier version of SQL Server is currently installed.	NA	This rule does not apply to your system configuration.
	AclPermissionsFacet	Checks if the SQL Server registry keys are consistent.	P	SQL Server registry keys are consistent and can support SQL Server installation or upgrade.
	Bids2008InstalledCheck	Checks if any of SQL Server 2008 Business Intelligence Development Studio installation exists.	P	SQL Server 2008 Business Intelligence Development Studio is not installed.
	DenaliCTPbyCTPSxS	This rule determines whether an instance of SQL Server "Denali" CTP0 exists.	P	SQL Server 2012 can be installed side by side with the existing version of SQL Server.
	FacetDomainControllerCheck	Checks whether the computer is a domain controller. Installing SQL Server 2012 on a domain controller is not recommended.	P	This computer is not a domain controller.
	FacetWOW64PlatformCheck	Determines whether SQL Server Setup is supported on this operating system platform.	P	SQL Server Setup is supported on this operating system platform.
	FusionRebootCheck	Checks if a computer restart is required because of broken fusion ATL. A pending restart can cause SQL Server Setup to fail.	P	The computer does not require a restart.
	SSMS_IsInternetConnected	Verifies that the computer is connected to the Internet. When a Microsoft .NET application like Microsoft Management Studio starts, there maybe be a slight delay while the .NET security check validates a certificate.	P	The computer is connected to the Internet and .NET security checks can be completed.
	IsFirewallEnabled	Checks whether the Windows Firewall is enabled.	W	The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at http://go.microsoft.com/ fwlink/?LinkId=94001 for information about ports to open for each feature.
InstallFeatureSpecificRules: SQL Server 2012 Setup configuration checks for rules group 'InstallFeatureSpecificRules'
	ASSPIExistingFarm UnconfiguredWarningCheck	Checks whether SharePoint is configured, and if not, recommends adding the Database Engine to the installation.	NA	This rule does not apply to your system configuration.
	ASSPIInstanceName NotInUseCheck	Checks for the required instance name.	NA	This rule does not apply to your system configuration.
	ASSPINewFarmConfigured WarningCheck	Checks whether SharePoint is un-configured. If the farm is configured, this rule recommends that you skip the Database Engine installation.	NA	This rule does not apply to your system configuration.
	ASSPIRequires CompleteFarmCheck	Checks whether SharePoint Server 2010 was installed with the "Farm", "Complete" option.	NA	This rule does not apply to your system configuration.
	ASSPIRequiresMossBitsCheck	Checks whether SharePoint server is installed.	NA	This rule does not apply to your system configuration.
	ASSPIRequiresO14 MossEnterpriseCheck	Checks whether SharePoint is the correct version and edition.	NA	This rule does not apply to your system configuration.
	ASSPIRequiresO14 MossSP1Check	SharePoint 2010 Service Pack 1 (SP1) requirement.	NA	This rule does not apply to your system configuration.
	InternetConnectionToNETFX4 DownloadSite	SQL Server media for Express packages does not include Microsoft .NET Framework 4.0 package. If Microsoft .NET Framework 4.0 is not already installed on the computer, SQL Server setup for the Express packages requires connection to Microsoft .NET Framework 4.0 dowload center to download and install .NET 4.0 Framework through Web setup. Ensure internet connection to Microsoft .NET Framework 4.0 download center on this computer. If you do not want to open up the internet connection, as a workaround pre-install Microsoft .NET Framework 4.0 on this computer before running SQL Server setup.	NA	This rule does not apply to your system configuration.
	PowerShellCheck	Checks whether Windows PowerShell 2.0 is already installed on system. Windows PowerShell is needed by some SQL Server features.	NA	This rule does not apply to your system configuration.
	ServerCoreBlock UnsupportedFeaturesCheck	Checks if all selected features are supported on Windows Server Core.	NA	This rule does not apply to your system configuration.
	ServerCoreNetFxCheck	Checks if The Microsoft .NET Framework 4 Server Core is already installed on this computer or is available for installation.	NA	This rule does not apply to your system configuration.
	SlipstreamMediaInfoCheck	Checks whether the language of the original media is the same language as the specified service pack.	NA	This rule does not apply to your system configuration.
	DEV10RTMDetected	This rule determines whether the computer has any prior installations of Visual Studio 2010 that might require Service Pack 1 update.	P	No prior installation of Visual Studio 2010 that requires Service Pack 1 update was found.
	RS_IsDotNet3_5Installed	This rule determines if the Microsoft .NET Framework 3.5 Service Pack 1 is required on the system, based on the features you selected and whether Microsoft .NET Framework 3.5 Service Pack 1 is already installed.	P	The Microsoft .NET Framework 3.5 Service Pack 1 is already installed.
InstallFeatureSpecificConfigRules: SQL Server 2012 Setup configuration checks for rules group 'InstallFeatureSpecificConfigRules'
	InstanceClashRule	Checks whether the specified instance name is already used by an existing SQL Server instance.	NA	This rule does not apply to your system configuration.
	ASIsValidEditionFor DeploymentModeCheck	Checks whether the SQL Server edition supports the currently selected Analysis Services server mode.	P	SQL Server Analysis Services server mode and edition check passed validation.
	BlockCrossLanguageInstall	Checks whether the Setup language is the same as the language of existing SQL Server features.	P	There are no existing SQL Server features, or the Setup language is as same as the language of existing SQL Server features.
	BlockMixedArchitectureInstall	Checks whether the installing feature(s) are the same CPU architecture as the specified instance.	P	The CPU architecture of the installing feature(s) matches the specified instance.
	FAT32FileSystemCheck	Checks whether the specified drive is FAT32 file system volume. Installing on a FAT32 file system is supported but not recommended as it is less secure than the NTFS file system.	P	The specified drive is not the FAT32 file system.
	RS_DoesCatalogExist	Checks whether the Reporting Services catalog database file exists.	P	The Reporting Services catalog database file does not already exist.
	RS_DoesCatalogTempDBExist	Checks whether the Reporting Services catalog temporary database file exists.	P	The Reporting Services catalog temporary database file does not already exist.
	StandaloneInstall_HasClustered OrPreparedInstanceCheck	Checks if the selected instance name is already used by an existing cluster-prepared or clustered instance on any cluster node.	P	No clustered or cluster-prepared instance with the selected instance name is installed on any cluster node.

NA = Not Applicable

P = Passed

W = Warning

The System Configuration Check report basically contains details of all the validations the SQL Server Setup does while installing SQL Server. This depends on the Setup operation (Install, Upgrade, Uninstall) we choose, and the report might vary for each Setup operation. You can find System Configuration Check report at the location: %programfiles%\Microsoft SQL Server\110\Setup Bootstrap\Log\<YYYYMMDD_HHMM>\ for SQL Server 2012.