ConfigMgr has evolved from the old SMS 1.2
days, where software distribution (using the good old Package Command
Manager) and inventory seemed to be the key components of the product.
Today, software distribution and inventory are very important, but just
part of the full suite. Operating System Deployment, Software Updates
management, and DCM are several of the new components of ConfigMgr.
Fortunately, the ConfigMgr client has over 30 log files for different
client components.The next sections discuss general troubleshooting scenarios,
online resources (typically the best method for troubleshooting
assistance), common issues such as resolving conflicting hardware IDs
and dealing with duplicate records, and using the ConfigMgr Toolkit.
1. General Scenarios
This section discusses several general troubleshooting scenarios. Table 1 lists several common issues to help get you started.
Table 1. Common Client Issues and Suggestions for Solutions
| Issue | Comments |
|---|
| ConfigMgr client doesn’t have an assigned site. | Launch
the Configuration Manager control panel applet, and from the Advanced
tab click Discover. If automatic site assignment fails, verify the
client is in a designated site boundary and has access to Active
Directory (or the SLP, specified during client installation). If you’re
using AD sites for your site boundaries, verify the AD site includes
the client subnet. |
| | Review ClientLocation.log and CCMExec.log. |
| Client unable to download content for software distribution/patch management. | Review execmgr.log, CAS.log, and LocationServices.log for more information from the client.
Verify the client should be able to obtain content (local/remote DPs, protected boundaries on site systems, and so on).
Also verify content for the package has the correct source version by
verifying the source version in package properties. Also, check the
distribution points in Package Status to verify package source version
and verify that the desired distribution point is targeted and
installed for the package source. |
| Software updates scan failing. | Verify the client’s primary site has a valid and healthy software update point.
Verify that there is no group policy enforced that specifies the WSUS location (ConfigMgr needs to manage this location).
Review WUAHandler.log, ScanAgent.log, UpdatesStore.log, and %windir%\windowsupdate.log. |
| Software Updates deployment failing. | Verify
the client has successfully scanned with the latest catalog (compare
the latest content version in ScanAgent.log with the latest content
version in wsyncmgr.log on the ConfigMgr site). Clients that have not
scanned with the latest content may not see the latest patches. Review
UpdatesDeployment.log, WUAHandler.log, UpdatesHandler.log,
%windir%\windowsupdate.log, UpdatesStore.log, and execmgr.log. |
2. Online Assistance
The Internet is your best friend for both ConfigMgr documentation and ConfigMgr troubleshooting. Table 2 provides some favorite tools and sites for online assistance.
Table 2. Online Assistance for ConfigMgr Client Troubleshooting
| Website/Utility | Comments |
|---|
| myitforum.com | Developed and maintained by Rod Trent, and considered the premier independent site for ConfigMgr assistance.
Subscribe to blogs at http://www.myitforum.com/cs2/blogs.
The very popular ConfigMgr email discussion lists can be found at http://www.myitforum.com/lists/.
You will learn a lot just by monitoring this list. You can also post
your question to some of the best ConfigMgr experts on the planet.
The Community forums are located at http://www.myitforum.com/forums/. Great forums on System Center products, as well as Windows, VBScript, and more.
Spend some time on www.myitforum.com to experience many of the other resources, such as myitforum.tv, myitwiki, and more. |
| Microsoft Configuration Manager Document Library | The ConfigMgr Document Library at http://technet.microsoft.com/en-us/library/bb680651.aspx
contains almost the same documentation as the ConfigMgr integrated help
(the F1 key in the console). The major difference is that the content
online is updated almost every month! You can also upgrade the
ConfigMgr integrated help using the ConfigMgr 2007 Help File Update
Wizard at http://www.microsoft.com/downloads/details.aspx?FamilyID=71816b0f-de06-40e0-bce7-ad4b1e4377bb&displaylang=en. |
| Troubleshooting ConfigMgr documentation | The troubleshooting documentation at http://technet.microsoft.com/en-us/library/bb632812.aspx
can provide a bit of insight into processes and error messages. The
Microsoft TechCenter has also recently added a Community Content
section on the bottom of each web page that allows you to submit your
own content. |
| Troubleshooting Client Push Installation | Although the document at http://support.microsoft.com/kb/925282 was created for SMS 2003, most of the troubleshooting steps and techniques apply in ConfigMgr also. |
| System Center Content Search gadget | This
gadget allows you to easily search for System Center information
because it uses Live Search macros to search specific sites instead of
the entire Internet. The gadget is available for download at http://gallery.live.com/LiveItemDetail.aspx?li=49e26ad0-113d-4f3da711-57f6530c75d9. |
| ConfigMgr Toolkit | Use the toolkit to view logs, inspect client policy, and manage Desired Configuration Management baselines. Download the current ConfigMgr Toolkit from http://www.microsoft.com/downloads/details.aspx?FamilyID=948e477e-fd3b-4a09-9015-141683c7ad5f&DisplayLang=en (or at www.microsoft.com/downloads, search for ConfigMgr Toolkit). |
3. Conflicting Hardware IDs
ConfigMgr
creates unique hardware IDs to define unique computers. Based on 10
computer properties (SCSI adapter, processor serial number, MAC
address, and so on), a unique hardware ID is created. If a system is
reimaged (and no hardware replaced), the hardware ID will be consistent
from the previous install to the new install.
When this occurs, ConfigMgr will have two records for the same resource, often called duplicate hardware IDs.
