Just a quick tip, nobody likes to read much during holidays 
If you want to troubleshoot a client deployment, a command prompt can be very handy. To get into one, just hit F8 during WinPE startup, it even works during operating system installation.
At the command prompt you can verify network settings, check log files during operating system install and so on.
FYI
Kim Oppalfens, who is a SCCM MVP, has released a neat utility called SccmAutoDoc. SccmAutoDoc is a command line utility that automatically documents an SCCM site into a human-readable form with minimal user input. Only the useful information is included, as opposed to items that are largely used internally. SccmAutoDoc’s requirements are spelled out on its site:
SCCMAutoDoc requires a machine with Word 2007 installed and access to the ConfigMgr site server and ConfigMgr Sms Provider. Word 2007 does NOT need to be installed on the Site server/SQL server or Sms Provider computer. The program can work from a remote machine running Windows XP, Vista or Windows 7.
Word 2007 does need to have the primary interop assemblies installed, but these are part of a default word 2007 install. If you don’t have the primary interop assemblies for office 2007 installed, you can always download them at http://www.microsoft.com/downloads/details.aspx?familyid=59DAEBAA-BED4-4282-A28C-B864D8BFA513&displaylang=en.
…
SccmAutoDoc requires a user with Read permissions on the site object of the Configuration Manager site to be documented. The commandline allows you to optionally pass a username and password as arguments to perform the documentation. If you don’t specify a username and password than the currently logged in credentials are used.
SccmAutoDoc can be downloaded from http://scug.be/media/g/sccmautodoc/default.aspx.
SccmAutoDoc is currently available as a free beta, but its site notes that it may become a paid tool in the future.
In the case I’m not the last one in the world to know this site, appdeploy.com provides useful info and tips & tricks about packaging common applications…
This must be the shorted post ‘till now 
I guess this message is not new for all of you out there, but it was for me…
The thing is that I was creating a collection with two queries in, where one is based on the file version, when I got the message:
To override the default setting of 2000 results, you must create a new dword value called ValueLimit in the registry under HKLM\software\microsoft\configmgr\adminUI\Queryprocessors and specify a number that will meet your needs.
Do this on the machine(s) where you have the SCCM admin console installed
Well, I just lost an hour figuring out why I could not connect to the SCCM db this morning while other co-workers have no problem at all, so I thought to share the troubleshooting steps…
the exact error is: The ConfigMgr console could not connect to the ConfigMgr site database. Verify that this computer has network connectivity to the SMS Provider computer and that your user account has Remote Activation permissions on both the ConfigMgr site server and SMS Provider computers.
-logon to a site server and open the admin console with the same account : no problem
-logon to another client with the admin console installed (same account): no problem
-launch dcomcnfg and verify that “enable distributed com on this computer” is checked (you can find that when you open the properties of your computer) : ok
-launch wbemtest and try to connect to \\siteserver\root\sms (modify the siteserver with your servername) : nok
-launch wmidiag and verify if all is well : nok
-check the smsadminui.log on your client
what do we find here:
[9][3/12/2009 9:38:36] :Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException\r\nThe ConfigMgr Administrator console could not connect to the ConfigMgr site database. Verify your user has read permissions to the ConfigMgr site and then try to connect again.
\r\n at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)
at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.BuildTreeWorker()\r\nAccess is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))
\r\nSystem.UnauthorizedAccessException\r\nAccess is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))\r\n at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
-last step: delete the profile under which you are attempting to launch the admin console
this did the trick for me!