Everyone who is working on ConfigMgr will be interested in knowing what type of hardware Microsoft IT used for ConfigMgr. Here are the details shared by Shitanshu is his blog. He has shared every minute details regarding server configuration like client count,raid configuration,CPU, hard disk and for both physical and virtual platform.
The P2V Migration for Software Assurance can now be implemented using System Center Configuration Manager 2007 Operating System Deployment as well as native Lite Touch Installation with the Microsoft Deployment Toolkit 2010. Computer refresh, replace and restore task sequence templates for Configuration Manager are included and documented in this Beta release.
Additional optimizations beyond Configuration Manager functionality included in this release are:
You can find the Beta Download here
Users may be unable to view and execute the System Center Configuration Manager 2007 reports hosted on SQL Reporting Services.
Problem 1: Trying to access http://<SQLServerName>/reports returns blank window.
Problem 2: When trying to execute one of the reports you get the following error:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source ‘{5C6358F2-4BB6-4a1b-A16E-8D96795D8602}’. (rsErrorOpeningConnection)
For more information about this error navigate to the report server on the local server machine, or enable remote errors.
This can occur due to a lack of permissions on the Reporting Server and the Database.
The basic configuration to allow an end user to view and execute the Configuration Manager Reports hosted via Reporting Services Point are as follows:
1. Create a Global Security Group for users with Read access to the Reports.
2. Add all of the users to this group who need to access to the Reports.
3. Open the Reports website with admin privileges (e.g. http://<SQLServerName>/reports).
4. Click on the Properties Tab > Click on New Role Assignment.
5. In the Group or User name box type in the domain\<GlobalSecurityGroup> you created in step 1.
This will allow those users to view the reports but will fail to execute them. They will get the error described in Problem 2.
To resolve Problem 2 follow the below steps:
1. Add the Global Security Group in SQL using the SQL Server Management Studio Security > Logins > New Login > User Mapping.
2. Check the box for the SCCM DB and Check “db_datareader” role.
Source :-http://support.microsoft.com/default.aspx?scid=kb;EN-US;2428400
Provides detailed steps that you can use to prepare for and install the Configuration Manager 2007 client. This SuperFlow also provides you with the dataflow for background processes, additional resources related to client installation, and troubleshooting information for common issues.
Old workflows are motioned in http://microsoftteched.com/2010/02/26/download-sccm-2007-superflows/
Symptoms
When using System Center Configuration Manager 2007, some clients may be assigned to the incorrect sitecode. You may also see entries similar to those below in the locationservices.log file:
Note that in the example above, the client should have been assigned to site P01 but was instead assigned to site P04.
Cause
This can occur if Active Directory references more than one site with the same site boundary.
Resolution
Remove or correct the site that contains objects using the same boundaries. To identify sites using the same boundaries, run ldifde -f output.txt from a command prompt and search the text file for the related boundary (ADSite1 in the example above).
Directly copied from http://support.microsoft.com/kb/2002059
Thanks And Regards | Abhishek Joshi
ConfigManager 2012 Technet