A customer I work with alot has an opening in their Oklahoma City location for a ConfigMgr administrator.  They are great folks, they are aggressive with new technology and this would be a great opportunity for the right person.  If you have an interest email me and I'll put you in contact.  breben @ microsoft . com

Configuration Manager has (and has had for a very long time) the 'All Systems' collection.  It contains discovered computers as well as actual clients.  In ConfigMgr 2012, what you see in this collection (especially at 'child' primary sites) may be a bit unexpected. 

For example, in ConfigMgr 2007, if you had a central ConfigMgr site (say site code CEN) and two primary sites (say site codes PR1 and PR2) and you viewed the 'All Systems' collection on PR1, all you see are the discovered objects and clients of that site.  Same holds true for PR2, which may have been configured to discover a different AD domain, OU, whatever.  Look at the 'All Systems' collection on the CEN site and would see all of the objects that PR1 and PR2 know about.  But, PR1 would have no knowledge of the computers discovered on PR2, and vice versa. Makes sense.

Now, in Configuration Manager 2012, EVERY primary knows about ALL objects.  PR1 knows about devices discovered on PR2, PR2 knows about devices discovered on PR1, and the CAS knows everthing too.  Welcome to the world of DRS in ConfigMgr 2012.  If you don't plan RBAC properly (or at all), this might pose some issues, especially around targeting baselines, packages, client agent settings, etc.

This week we are putting together the final touches on the Microsoft System Center 2012 Configuration Manager migration and application deployment workshop that my group at Microsoft (Premier Field Engineering) will be offering soon (hopefully within 60-90 days of ConfigMgr 2012 GA).  We will cover the new features of Configuration Manager 2012 and will go deep on migration from 2007 to 2012 and will also go into the new application model.  If you are a premier customer and are interested in attending this workshop once released, let your Microsoft Technical Account Manager (TAM) know and they can contact me for availability (breben @ microsoft.com).   

You may encounter the error "SQL Server x is not running version SQL Server 2008 or SQL Server 2008 R2" even though the server IS running the correct version of SQL server.  Try the steps provided in this article and it should resolve the issue.
http://support.microsoft.com/default.aspx?scid=kb%3bEN-US%3b956013.  Note that your path may be a bit different than the one shown in the KB.