SCCM 2007 Client troubleshooting – Part 3: Client Assignment

In order for Configuration Manager Clients to function properly, they need to detect what Site they’re in and communicate with their assigned Management Point. Sometimes SCCM Client Assignment doesn’t work as it is supposed to be.

David Stein By David Stein - Tue, April 16, 2013 - 0 comments google+ icon

David is an author and consultant, working for Endurance IT Services in Virginia Beach, Virginia, specializing in Microsoft enterprise systems and Business Process Automation.

Articles in this series

SCCM 2007 Client troubleshooting

While a client can be installed with parameters that dictate their Site Code assignment, it’s usually best (and more common) to allow the automatic client assignment processes do its job and determine the appropriate Site Code.

Configuration Manager Site Code

Configuration Manager Site Code

Symptoms

  1. Clients do not appear in the management console or on inventory reports
  2. Clients show up under the wrong Site in the management console
  3. The Client Agent applet (Control Panel) has no Site Code assignment value
  4. The Client Agent applet has an incorrect Site Code assignment value

Potential causes

  1. Incorrect client installation parameters (manual or automatic assignment)
  2. Faulty or unavailable Server Locator Point
  3. Active Directory Schema was not extended (and no alternate for SLP was configured)
  4. Client is not part of the same AD Forest as the Site Server, or Client is no longer trusted by the same AD Forest as the Site Server
  5. DNS or WINS name resolution issues
  6. The “System Management” container was not created properly in AD
  7. The “System Management” container permissions do not allow Site Servers to post updates
  8. Network connectivity issues
  9. Missing or incorrectly configured Site Boundaries
  10. Improper client version per Site assignment

Suggestions

There are a million methods for diagnosing assignment problems, simply because of the range of potential underlying causes. If the problem appears sporadically, rather than among batches of computers, start with the device and work your way up. If it appears to be some sort of pattern, start with the big picture and work your way down.

  1. Verify network connectivity.
  2. Verify client installation settings. If the client installation was performed with a script or a configured command-line parameter set, verify that the parameters being passed to the client are correct.
  3. Verify client Site Code was not manually entered incorrectly.
  4. Verify name resolution (DNS, WINS): ping, nslookup, tracert, etc.
  5. Check the client CCM logs (%WINDIR%\system32\ccm\logs, or %WINDIR%\SysWOW64\ccm\logs). In particular, the “ClientLocation.log” and “LocationServices.log” files
  6. Check the client’s Windows System and Application Event Logs.
  7. Verify the TCP/IP configuration settings to eliminate obstacles to name resolution. I’ve seen issues where users assigned incorrect static settings, as well as administrators making incorrect settings to DHCP scopes and scope options. Sometimes it can be as simple as clearing the client’s cache.
  8. If you need more granular tools for diagnosing network communication, consider DIG, WireShark, NMap, Snort, WinPCAP and other similar utilities.

Helpful links

In the next post of this Configuration Manager Client troubleshooting series we will cover inventory reporting problems.

Series NavigationSCCM 2007 Client troubleshooting – Part 2: Client Push installation - SCCM 2007 Client troubleshooting – Part 4: Inventory reporting

-1+1 - Rate this post
Loading ... Loading ...
Your question wasn't answered? Ask in the new 4sysops forum!
===Leave a Comment===

Login

Lost your password?