Transcript Slide 1

The G.I. Joe Method for Troubleshooting
Configuration Manager 2007
Rod Trent, CEO, myITforum
26 October 2011
Moderated by:
Sponsored by:
Agenda
• Welcome
– Ron Crumbaker, CTO, myITforum
•
•
•
•
•
Introduction
BDNA & myITforum
Rod Trent, CEO, myITforum
Q&A
Wrap Up
Google+ Hangouts & Forums
• Reed Porter Google+ Hangout:
http://bit.ly/okiIib
• myITforum SCCM GURU webcast
live forum
http://myITforum.com/SCCMguru
BDNA Normalize & SCCM
• Walker White, CTO
myITforum
• Ron Crumbaker, myITforum
– All things “System Center”
– Since 1999
– Large and growing community (over
120,000 visitors a day)
– Huge storehouse of System Center
knowledge
– Noobies to experts
Rod Trent
• Owner of myITforum.com
• Over 25 years in the industry
– Almost 20 dedicated to System Center
• Author
• Speaker
• Evangelist
Knowing is half the battle
• Troubleshooting ConfigMgr is about
knowledge
– Not always about expertise or experience
– How to get answers
– Where to get answers
– Understanding the basic concepts
History of ConfigMgr
• Working knowledge of ConfigMgr
history is a huge plus
– Early days
– My story
– History of SMS/ConfigMgr:
http://myitforum.com/myitforumwp/service
s/wiki/
Basic concepts
• Consider the components for failure:
– Client OS (multiple versions)
– Server OS
– Active Directory
– Network infrastructure
– ConfigMgr client (dependent on all)
Basic concepts
• At it’s core, ConfigMgr is a delivery
system
– Alerts, reporting, queries – all dependent
on delivery accuracy
– Software and patches (of course)
– Many moving parts
– Many areas for potential problems
It’s a war
• ConfigMgr people are the smartest
people in the world
• Are you equipped?
• Tools, utilities, solutions, and
community
Troubleshooting basics
• Down-and-dirty Visualization
– Hierarchy map
• Flowchart (Visio)
http://myitforum.com/myitforumwp/groups/conf
igmgr-downloads/documents/
• SuperFlows (documentation)
http://technet.microsoft.com/enus/library/ff385001.aspx
• Console
• Paper!
Troubleshooting basics
• Tried-and-true troubleshooting tools
– SCCM Client Center
http://sourceforge.net/projects/smsclictr/
– Jason Sandys CM Startup Script
http://myitforum.com/cs2/blogs/jsandys/ar
chive/2010/12/30/updated-configmgrstartup-script.aspx
Troubleshooting basics
•
•
•
•
•
•
•
Identify
Isolate
Navigate
Research
Resolve
Duplicate
Document
Breaking it down
• Client Existence
– Control Panel > Configuration Manager
– Task Manager (ctrl+shift+esc) > Processes >
CcmExec.exe
– Task Manager > Services > CcmExec
– Control Panel > Admin Tools > Services > SMS
Agent Host
– c:\windows\system32\ccm (32bit)
– c:\windows\syswow64\ccm (64bit)
– HKLM\SOFTWARE\Microsoft\SMS\Mobile
Client\Product Version (32bit)
– HKLM\SOFTWARE\Wow6432Node\Microsoft\SMS\
Mobile Client\Product Version (64bit)
Breaking it down
• Client functions
– Policy updates and application
– Manage downloads (software/updates)
– System scans (hardware and software)
– Inventory reports (scans)
Breaking it down
• Client installation success
requirements
– Resolvable hostname (proper DNS entry)
– Service account with local admin rights
– RPC access to OS components (examples:
registry, WMI)
– Admin$ shares
– WUA (Windows Update Agent)
Breaking it down
• Lifeblood of troubleshooting: LOG
FILES
• How to read them:
– Notepad (Wally Mead’s favorite)
– Visual Log Parser:
http://visuallogparser.codeplex.com/
– VB Script (Paul Thomsen)
http://myitforum.com/cs2/blogs/pthomsen/
archive/2008/01/27/111954.aspx
Breaking it down
• How to read them (continued):
– SMS Trace (System Center Configuration
Manager 2007 Toolkit V2):
http://www.microsoft.com/download/en/det
ails.aspx?displaylang=en&id=9257
– Specops Log Viewer:
http://www.specopssoft.com/documentatio
n/specops-deploydocumentation/specops-logvieweroverview
Breaking it down
• Focus today
– Client log files and tips
• Why? Majority of ConfigMgr issues are
client issues
Log Files
• Where to find them
– Management Points, the client logs are
located in the
%ProgramFiles%\SMS_CCM\Logs folder
– All other computers, the client logs are
located in the
%Windir%\System32\CCM\Logs folder or the
%Windir%\SysWOW64\CCM\Logs
Server Log Files
• Where to find them
– Most located in <InstallationPath>\LOGS
– IIS %Windir%\System32\Logfiles\W3SVC1
• Review the IIS log file for additional errors that
relate to client access to the IIS server
Client Log Files – in depth
• CAS.log
– Content Access service. Maintains the local
package cache.
• CcmExec.log
– Records activities of the client and the SMS
Agent Host service.
Client Log Files – in depth
• CertificateMaintenance.log
– Maintains certificates for Active Directory
directory service and management points.
• ClientIDManagerStartup.log
– Creates and maintains the client GUID.
Client Log Files – in depth
• ClientLocation.log
– Site assignment tasks.
• ContentTransferManager.log
– Schedules the Background Intelligent Transfer
Service (BITS) or the Server Message Block
(SMB) to download or to access SMS
packages.
Client Log Files – in depth
• DataTransferService.log
– Records all BITS communication for policy or
package access.
• Execmgr.log
– Records advertisements that run.
Client Log Files – in depth
• FileBITS.log
– Records all SMB package access tasks.
• Fsinvprovider.log
– Windows Management Instrumentation (WMI)
provider for software inventory and file
collection.
Client Log Files – in depth
• InventoryAgent.log
– Creates discovery data records (DDRs) and
hardware and software inventory records.
• LocationServices.log
– Finds management points and distribution
points.
Client Log Files – in depth
• Mifprovider.log
– The WMI provider for .MIF files.
• Mtrmgr.log
– Monitors all software metering processes.
• PolicyAgent.log
– Requests policies by using the Data Transfer
service.
Client Log Files – in depth
• PolicyAgentProvider.log
– Records policy changes.
• PolicyEvaluator.log
– Records new policy settings.
• RemoteControl.log
– Logs when the remote control component
(WUSER32) starts.
Client Log Files – in depth
• Scheduler.log
– Records schedule tasks for all client
operations.
• Smscliui.log
– Records usage of the Systems Management
tool in Control Panel.
Client Log Files – in depth
• StatusAgent.log
– Logs status messages that are created by the
client components.
• SWMTRReportGen.log
– Generates a usage data report that is
collected by the metering agent. (This data is
logged in Mtrmgr.log.)
Client Log Files – Tips
• Troubleshooting Client Health
– CcmExec.Log: first stop for bad installations
– ClientLocation.log: verify client has a healthy
install with a site server
– StatusAgent.log: status messages for client
components and connectivity issues
Client Log Files – Tips
• Troubleshooting Policy
– PolicyAgent.log: contains policy request
information, success/failure.
– PolicyEvaluator.log: identifies issues applying
policies
Client Log Files – Tips
• Troubleshooting Connectivity
– InternetProxy.log: if using unprotected DPs
– Mpcontrol.log: contains information about the
state of the Management Point
– LocationServices.log: provides information
about attempted connectivity to MPs and DPs
Client Log Files – Tips
• Troubleshooting Licenses/Registration
– Hman.log: client registration with the site
• Troubleshooting Installation
– Ccmsetup.log: client installation information
contained here
– Client.msi.log: information recorded here from
the installer
SCCM Client Troubleshooting
Tips
• WMI Error codes
– 0x800410xx - 0x800440 - Errors that originate
in WMI itself
– 0x8007xxx - Errors originating in the core
operating system
– 0x80040xxx (DCOM)
– 0x80005xxx – ADSI/LDAP
SCCM Client Troubleshooting
Tips - Installation
• Firewall
– Add exceptions for File and Printer Sharing,
WMI
• GPO not retrieving install properties from AD
– Check SCCM boundaries are correct
• Software Update Point installation
– Check for AD policy override
– Software Update Point no configured correctly
SCCM Client Troubleshooting
Tips – Client Assignment
• Clients assign to a Site but are
unmanaged
– Reinstall client using Push for automatic
configuration
• Clients fail to assign to correct Site
– Boundaries
SCCM Client Troubleshooting
Tips – More
• Cannot locate MP
– MP not configured correctly
• Client gets assignment from: AD (if extended for SCCM),
DNS (if SCCM configured for DNS publishing), Server locator
point, WINS (mixed mode only)
• Error codes in reports
– http://support.microsoft.com/kb/944375/en-us
• VPN clients not getting updates
– Configure client to a “fast” boundary
– Choose to “download” and run locally
– Use a 3rd party network mgmt solution
Be Warlike
• Know your limits
• Assume that for every problem, a
solution already exists
• Command your army
Top Resources
• Email lists
http://myitforum.com/myitforumwp/support/email-lists/
• Forums
http://myitforum.com/myitforumwp/support/forums/
• Community groups
http://myitforum.com/myitforumwp/groups/
Top Resources
• Instruction
http://myitforum.com/myitforumwp/support/tv/
• MVPs – most of which participate at
myITforum
• Microsoft Management Summit
http://www.mms-2011.com/
Wrap Up
Next SCCM GURU Webcast:
• Wednesday, November 16th, 2011
• Michael Niehaus
Systems Design Engineer
Microsoft Core Infrastructure Solutions

www.bdna.com/sccm-guru
Thanks for attending!
To thank you for participating in our SCCM
GURU webcast, we’d like to offer EVERYONE
on the webcast a super cool SCCM GURU
Webcast T-shirt. Please register here:

www.bdna.com/rod
Questions, Contact Info
For more information…
BDNA
Matt Lefer
[email protected]
+1 (650) 641-6017
myITforum
Rod Trent
[email protected]
+1 (513) 217-7122