|
| |
General SMS 2003 troubleshooting
Softwareverteilung
- Wikipedia
How to troubleshoot
SMS Administrator console connectivity
One or more site
objects may be missing after you expand a site hierarchy node in a remote System
Management Server 2003 Administrator Console
Definition of Terms
- Collection - "logical" Group of Clients or Computers e.g. "all Clients RAM
greater 512Mb AND Windows XP running" can be based e.g. on Hardware or/and
Software Inventory
- Package - Source Files (executables) necessary for the Installation, unless
already located and run on the client / accessible Network Share.
- Program - a Package may consist of one or more programs - e.g.
Install, Uninstall, Repair, Config etc...
the Program is the information needed to run.
- Advertisement - Notifies Computers / Users of available (and executable)
Programs
- Distribution Point
- Primary Site - The first Primary Site is also called "Central Site". A
Primary Site needs a SQL Database
- Secondary Site - For Load Balancing and other purposes, A Secondary Site
does not have a SQL Database - it communicates with it's Primary Site.
- BITS - Background Intelligent Transfer Service, used to Transport Data
with Bandwidth limitation / in Idle times.
SMS 2003 Server Inboxes
SMS 2003 Server Log Files
This is a list of known Log files written by SMS 2003 Server
|
Adsysdis.log |
Active Directory System Discovery |
|
Adsysgrp.log |
Active
Directory System Group Discovery |
|
Adusrdis.log |
Active Directory User Discovery |
|
Ccm.log |
Client
Configuration Manager |
|
Cidm.log |
Client Install Data Manager |
|
Colleval.log |
Collection Evaluator |
|
Compsumm.log |
Component Status Summarizer |
|
Cscnfsvc.log |
Courier
Sender Confirm |
|
Dataldr.log |
Data Loader (Inventory) |
|
Ddm.log |
Discovery Data Manager |
|
Despool.log |
Despooler (communication from child or parent Site) |
|
Distmgr.log |
Distribution Manager |
|
Hman.log |
Hierarchy Manager |
|
Inboxast.log |
Inbox
Manager Assistant |
|
Inboxmgr.log |
Inbox Manager |
|
Invproc.log |
Inventory Processor |
|
Mpcontrol.log |
Management Point Control |
|
Mpfdm.log |
Management Point File Dispatch |
|
Netdisc.log |
Network Discovery |
|
Ntsvrdis.log |
Windows NT Server Discovery Agent |
|
Offermgr.log |
Offer
Manager |
|
Offersum.log |
Offer Status Summarizer |
|
Sitectrl.log |
Site
Control Manager |
|
Sitestat.log |
Site System Status Summarize |
|
SMSdbmon.log |
SMS
Database Monitor |
|
SMSexec.log |
SMS Executive |
|
Statmgr.log |
Status
Manager |
|
Swmproc.log |
Software Metering Processor |
SMS 2003 Legacy Client Log Files
%windir%\MS\SMS\Logs
SMS2003 Advanced Client Log Files
(alphabetical Order)
%windir%\system32\ccm
|
CAS.log |
Content Access Service log File, showing when an advanced
client tries to access package content or advertised programs from a
Distribution Point. The log shows if the advanced client can find the
Distribution Point and whether or not the client can access the content on
the Distribution Point. |
|
CCMExec.log |
Agent Host log File. After the advanced client has generated
discovery, inventory, status data, etc. data, this log file shows any
communications errors with the Management Point. (Example: WINHTTP ERROR may
appear when a client can't talk to the Management Point) |
|
CertificateMaintenance.log |
Used for retrieving certificates for the Management Point,
performed periodically to verify that the certificates are correct for the
Management Point. |
|
ClientIDManagerStartup.log |
Manages the
SMS Unique ID. Each client maintains a unique ID and if the client
determines that the unique ID is in a cloning scenario or needs to changed,
the event is logged here, including what had changed on the client to
trigger the GUID change. |
|
ClientLocation.log |
This log files determines the assigned
SMS site. This is the first place to look when a client isn't reporting
data. A client won't do anything until it has been assigned to a primary
site. It could be that auto-discovery isn't functioning successfully (AD
schema not extended or
SMS data not published in AD or a Server Locator Point cannot be located). |
|
ContentTransferManager.log |
Shows the management of the local cache for downloaded and
executed programs, and then the aging of that content out of the cache when
it is no longer needed. |
|
DataTransferService.log |
Shows the actual download of policies that are retrieved from
the Management Point (including the URL used by the client to retrieve the
data). The Data Transfer Service is what actually completes the download of
those policies. Check this log file for advanced client problems
transferring or obtaining polices from the Management Point. |
|
Execmgr.log |
Running advertised programs, similar to the SMSapm32.log file
from the
SMS 2.0. Command lines executed, successful or not, and exit codes will
appear in this log file. Check this log for issues with advertisements. |
|
FileBITS.log |
When using Server Message Blocks (SMBs) to download and
execute content retrieval from the Distribution Point, this file tracks all
activity. This implies that the Distribution Point is not BITS-enabled (or
WebDAV is not enabled), thus using SMBs to download the content. |
|
Fsinvprovider.log |
File Software Inventory Provider. This log file is used for
software inventory. Look in this log file to observe the software inventory
scanning process. Renamed to FileSystemFile.log in SMS 2003 SP1. |
|
InventoryAgent.log |
This log is for discovery, hardware and software inventory
processing of the Advanced Client. There is a single agent on the advanced
client that is used for all three of these processes. This log file shows
properties being discovered in HINV as well as paths in SINV being
discovered. Look for the mp_xxxxEndpoint to see what data is being sent to
the management point. |
|
LocationServices.log |
Use this log file if advanced clients are downloading
policies or looking for distribution points to access package source files.
This log is also used to determine if clients are finding the default
Management Point. Messages that you want to look for are like: Attempting to
retrieve default Management Point from AD (Attempting to retrieve default
Management Point from WINS); Attempting to retrieve proxy Management Point (Attempts
to find a local (resident) management point when roaming). When a Management
Point is found, this log file will show messages like: Retrieved default
Management Point from AD; Persisted Management Point in WMI; Retrieved
default Management Point from AD; and, Retrieved Management Point from WINS.
It then displays the computer name of the Management Point (or its IP
address if the management point is retrieved from WINS). This log file is
also used to locate Distribution Points. The client sends a content location
request, location services goes to Management Point to request content
location from the Management Point regarding Distribution Points available
to the client. |
|
Mtrmgr.log |
Software Metering |
|
PatchUIMonitor.log |
User Interface SMS 2003 patch management. |
|
PolicyAgent.log |
Policy Agent Log File, updated each hour it logs policy
requests and downloads.
If you have made a change to the SMS site and you want to verify that the
advanced client is working, look in this log file after performing “Initiate
Action” for Machine Policy Retrieval & Evaluation Policy from the SMS
program in control panel (Actions Tab). This will show whether the new
policy has been successfully retrieved from the Management Point. Look for
“Requesting Machine Assignments” and then actual policy IDs (as GUIDs). |
|
SMSCliUi.log |
SMS (Control Panel) Client User Interface Actions Log File. |
|
SrcUpdateMgr.log |
MSI (Windows Installer) source locations |
|
StatusAgent.log |
Status Messages Creation |
|
SWMTRReportGen.log |
Software Metering Usage Report Generator |
Communication between Sites
via Despoolr.box\receive (shared as "SMS_SITE") - needs modify rights for used
Account.
Active Directory Integration
You can use SMS to query some AD (Active
Directory Service - Wikipedia) related Information, such as AD System Group
Discovery, AD Security Group Discovery.
contact me, if You need more Information
SMS Queries / WQL
.NET Automation SMS2003
currently I'm developing Tools automating SMS 2003 Tasks such as Managing
Servers, creating collections, advertisements, queries, packages, programs. If
You are interested, contact me.
Remove orphaned SMS Sites
If You need to remove orphaned SMS Sites (e.g. a Server
has been decommissioned, but not removed in Site hierarchy
Preinst.exe /DELSITE <SiteToRemove> <Primary Site>
Preinst.exe /DELJOB <SiteToRemove>
make sure that You run these commands with administrator
rights for the site class (SMS Administrator Console - Site Database - Security)
The
Hierarchy Maintenance Utility (the Preinst.exe tool) does not verify group
membership in SMS 2003
SMS
Assigning Class and Instance Security Rights with the SMS User Wizard
|
