Are you preparing for SCCM Interview , Below are the ultimate list of Real time

SCCM / SMS Interview Questions with Answers which covers different topics
ranging from Installation, Troubleshooting, OSD, DCM, SUP etc.
Can you change a secondary site to a primary site?
No. A secondary site is always a secondary site. It cannot be upgraded, moved, or changed
without deleting it and reinstalling it. If you delete and reinstall, you lose all secondary site data.
Can you distribute a package to a computer without making it a member of a collection?
No. To distribute software you must have a package, a program and an advertisement.
Advertisements can only be sent to collections, not to computers. If you want to distribute a
package to a single computer, you must create a collection for that computer.
What is Secondary Site?
Four Main characteristics:

A Secondary Site does not have access to a Microsoft SQL Database

Secondary Sites are ALWAYS a Child Site of a Primary Site and can only be
administered via a Primary Site

Secondary Sites cannot have Child Sites of their own

Clients cannot be assigned directly to the Site

What is CENTRAL SITE?

A Central Site is a Configuration Manager Primary Site that resides at the top of the
Configuration Manager hierarchy. All Database information rolls from the child to the parent and
is collected by the Central Sites Configuration Manager Database. The Central Site can
administer any site below it in the hierarchy and can send data down to those sites as well.
What is PRIMARY SITE?
Four main characteristics:

The Site has access to a Microsoft SQL Server Database

Can administer or be administered via the Configuration Manager Console

It can be a child of other Primary Sites and can have Child Sites of its own

Clients can be assigned directly to the Site

How do you install and configure Secondary site server

http://exchangeserverinfo.com/2008/05/02/installation-and-configuration-of-secondary-siteserver.aspx
How do you create a package for Adobe?
the command line msiexec.exe /q ALLUSERS=2 /m MSIHPSJR /i AcroRead.msi
TRANSFORMS=mytransform.mst
How do you distribute a package?

create a package in SCCM, pointing it to the installation sources, and in the package
create an install program (you may have already done this?)

assign Distribution Points to your package so the contents get synched.

create a Collection containing the objects (users/computers) that are allowed to receive
the package.

create an Advertisement for the distribution, linking the package you created to the
collection, decide whether the Adverisement is mandatory (installation enforced) or not
(users have to go to the Run Advertised Programs dialog in Windows and select to
install the program)

How SCCM download the patches?

You need to add the Software Update Point site role to the site, configure the software update
point as active, configure the products, classifications, sync settings, etc. in the Software Update
Point properties. THEN, you can go to the Update Repository node and run the Run
Synchronization action from the central primary site. Once synchronization completes, you will
see the metadata in the Configuration Manager console.
How do you configure the SUP?
In the Configuration Manager console, navigate to System CenterConfiguration
Manager / Site Database /Site Management / &lt;site code> <site name> / Site
Settings / Site Systems
Right-click the site system server name, and then click New Roles.
Select Software update point, and then click Next.
Specify whether the site server will use a proxy server when connecting to the software update
point, and then clickNext.
Select Use this server as the active software update point, and then specify the port settings
configured for the WSUS Web site on this site system.
Specify the synchronization source for the active software update point using one of the
following settings: like Synchronize from Microsoft Update or Synchronize from an
upstream update server
Keep the default setting Do not create WSUS reporting events, and then click Next

Specify whether to synchronize software updates on a schedule by selecting Enable

synchronization on a schedule
Specify the update classifications for which the software updates will be synchronized, and then
click Next.
Specify the products for which the software updates will be synchronized, and then click Next.
Open SUPSetup.log in <InstallationPath>\Logs to monitor the installation progress for the
software update point. When the installation completes, Installation was successful is
written to the log file.
Open WCM.log in <InstallationPath>\Logs to verify that the connection to the WSUS server
was successful.
How do you Backup SCCM Server?
To create a scheduled backup task, expand the Site Settings node and expand the Site
Maintenance node, click on Tasks.
For Manual backup Start SMS_SITE_BACKUP service
What are the client deployments methods?
Client Push Installion, Software update point based installation, Group Policy Installation, Logon
Script Installation, Manual Installation, Upgrade Installation(software Distribution)
Can you discover clients those are in different AD forest?
yes.
Internet-based client management, which supports the following site systems installed in a
separate forest to the site server:
Management point
Distribution point
Software update point
Fallback status point
What are the prerequisite for Software Update Point?
Windows Server Update Services (WSUS) 3.0, WSUS 3.0 Administration Console, Windows
Update Agent (WUA) 3.0,Site server communication to the active software update
point,Network Load Balancing (NLB),Background Intelligent Transfer Server (BITS)
2.5,Windows Installer
What is SMS Provider?
The SMS Provider is a WMI provider that allows both read and write access to the Configuration
Manager 2007 site database. The SMS Provider is used by the Configuration Manager console
The SMS Provider can be installed on the site database server computer, site server computer or
another server class third computer during Configuration Manager 2007 Setup. After setup has
completed, the current installed location of the SMS Provider is displayed on the site properties
general tab
What is ITMU?

SMS 2003 Inventory Tool for Microsoft Updates

What is the use of WSUS (Windows Server Update Service)?
It enables administrators to deploy the latest Microsoft product updates to computers that are
running the Windows operating system.
Difference between SMS 2003 and SCCM 2007
What is WMI (indows Management Instrumentation)?
You can write WMI scripts or applications to automate administrative tasks on remote computers
What is SUP ( Software Update Point)?
This is required component of software updates, and after it is installed, the SUP is displayed as a
site system role in the Configuration Manager console. The software update point site system
role must be created on a site system server that has Windows Server Update Services (WSUS)
3.0 installed.
This is how People come here Searching:

sccm administrator interview questions

what is the difference between sms and sccm

sms sccm interview questions

You want specific users\groups to run specific custom reports. What should you do?
Navigate to System Center Configuration Manager Site Database Security Rights Users
Right click on Users and select Manage ConfigMgr Users
Navigate to the SCCM Support group you created earlier
1. For Collection (All Instances) add the following:
- Delete resource
- Modify resource
- Read
- Read resource
- Use remote tools
2. For Report (All Instances) add the following:
- Read
3. For Computer association (All Instances) add the following:
- Create
- Delete
- Read
- Recover user state
4. Click Next

5. Click Next
6. Click Close
You have been provided with permissions on the SCCM console to create, distribute, modify and
delete packages? However, when distributing a package there is no Distribution points listed in
the Distribution Point Wizard. What should you do?
To designate a distribution point on a new server or server share
1. In the Configuration Manager console, navigate to System CenterConfiguration
Manager / Site Database / Site Management / <site name> / Site Settings.
2. Right-click Site Systems, point to New, and then click Server or Server Share, depending
on which you want to create.
3. If you are creating a new server, use the New Site System Server Wizard to create the
site system server, and select the Distribution Point check box from the Available
Roles on the System Role Selection page to designate this server as a distribution point.
What are the required ports used by Configuration Manager?
http://technet.microsoft.com/en-us/library/bb632618.aspx
You distributed a software application to some systems in your environment and few are failed,
how do u troubleshoot the failure? what steps you will follow on client side and site server
side? How SCCM clients come to know that they have to use SCCM WSUS?
How certificates created in SCCM and what they called?
How SCCM Communicate securely between sites? And where do you define that setting? what
you will keep in mind before configuring SCCM server to manage clients.
What are the causes for a slow Configuration Manager Console connection and what would you
do to make your Configuration Manager Console users experience better?

SCCM Interview Questions 2013

What is the purpose of extended AD schema?

What are MP, SLP and DP?

Why we are using BITS?

If client is not reporting data/info then which point is falls under?

If we want to advertisement a package in a single client then how do to that?

How to create collections?

What is feature of SCCM 2k7? Internet based client, OSD and Wake on LAN.

Where the SMS server and client log file will be store?

What is the direct collection membership?

What is the wake on LAN?

What is the pre-requisites of SCCM 2k7?

What is Wake on LAN and how its works?

What is OSD? And what are the options available?

What is diff. between WSUS & ITMU?

If pkg is not reaching the secondary server then what could be a issue?

What is NAP?

What are the issue faced while distribute the package from primary server to
secondary server?

Which tool are you using to monitor SMS server?

What kind of major issues face on the client side?

What is the different between pkg refresh and update, where the changes will be
happen, how the pkg version will be change?

What is the SMS version are you using, ITMU version?

How MP and DP identified client? Is it possible client can send inventory report to
server if AD not extended?

When AD extended in the SMS server there are entry will be added in the AD, what
is that?

What are the pre-requisites for SMS 2k3 installation?

If DP doesnt work then where we need to look and which are the log files will you
refer?26) How the clients send the info to MP? If it is WMI then which file send the info to
WMI?27) What is the procedure to deploy pkg to client and how it works?

Which log file will indicate if SMS client install successfully?

What is the sender address? Classification of sender, if you use Standard sender then
why we are using it?

What are the role will you enable in the Central Site?

Different between Primary and Secondary site?

What is the reason we are enabling reporting point in Central Site?

What is the flow of pkg distribution?

Some of the clients are not getting patch installed? What could be a reason and how
to find out those clients and troubleshoot?

What are the logs need to look client and server side?

How to client communicate with server?

Through which port client getting download file from server?

How did you know that the particular patch reached client or not?

How many MP and DP can we enable a single site?

When the default profile will be loading in AD user & computers while install SMS?
What are the profile names?

Why are we using SQL2005 enterprise edition? What is the advantage of that and
there are major changes/ Configuration need to be done during the SQL 2005 installation,
what is that?

Scenario: we have a one Forest and two Domains, how the SMS communicate with
them if so, how to configure in boundaries?

There are 4 methods to view the logs and to do troubleshoot also.

What are the discovery methods available?

What is the default schedule time for AD system discovery method?

Which .exe file will use for SMS client installation?

After SMS client installation, there is a one exe will be running continuously, what is
that?

If the client machine not in the domain then how the SMS server communicate and
install SMS client?

Scenario: Total hosts: 20001500 clients assigned status is Yes and 500 client status
is No even all the client got installed SMS client. What are the troubleshoot steps to be
followed for resolving the issue?

How to know that the particular application is running on client machine?

What are the default collections available in SMS?

Can you tell two resource ids? Resource id, Resource Value, Resource type and
system resource.

How to advertisement goes to client?

Which logs should look when communication happen from primary to secondary?
Hman.log and hierarchy manager

Site to site communication? Sitecomp.log, hman.log

How will you check client health status?

What are the steps needs to be following if a pkg needs to distribute production
environment?

There is a one site and it has 100 clients, needs to be deployed one pkg to 10
clients? How will you create a collection?

There is a pkg and it will be rebooting after install the application. Needs to be
suppressing the reboot function in the program?

What kind of client installation method are you using?

We have a 1000 client and 800 clients are installed SMS client, 200 client not
installed. What could be a reason? 61) Why we need to extend AD? What is the name of
file?

What is SLP, BITS, Difference b/w primary and secondary server, native mode and
mixed mode , what is advantage using this

Does internet based client support mixed mode? No64) What is DP and BDP, hw will
backup SCCM, difference b/w SMS and SCCM 65) How to configure software metering for
particular package?

Deployed one package to 10k client, however 1500 machines got failed, how will
troubleshoot?

What are the sites roles configured?

What is desire configure management? Why are we using it?

What are the features avail in SCCM

OSD- how will create a OS

What are the reports will pullout from SCCM

What are the components avail in SCCM

Diff b/w native mode and mixed mode

How will setup new SCCM environment

What is BDP, what are the roles avail in SCCM &their function

What is H/W inventory log file and server log files

Diff b/w ITMU & WSUS

What are the service are running on SCCM server and client

What is SMS execute

What is SMS_site_component_manager

SMS_site_SQL_backup, SMS_Reporting point, SMS_server_locator_point,

SMS_task_sequencer_agent, SMS_agent_host

What are the package can distribute through ITMU or WSUS all Microsoft package,
hot fixes, patch, Service pack

ConfigMgr does not allow for incremental or differential backups and it always adopts
a full backup approach i.e. it backs up everything that is needed to reinstall a site
completely

SCCM 2007 Basics

I've been looking for short notes that facilitate quick understanding knowledge on SCCM
2007. I finally put my efforts to bring a short notes on SCCM 2007 to help those who are

already familiar with Systems Management Server (SMS) 2003 and who wish to quickly
develop understanding knowledge on 'Microsoft System Center Configuration Manager
2007'.

Microsoft SCCM -2007 (ConfigMgr) provides a comprehensive solution for change and
configuration management for the Microsoft platform, enabling organizations to provide
relevant software and updates to users quickly and cost-effectively, Allows IT staff to
monitor and manage the hardware & software in a modern distributed environment.

SCCM 2007 Features

HW/SW Inventory

Software Distribution

Software Update

Software Metering

Operating System Deployment (Image capture/deployment, User State Migration,

Task sequence)

Manage site accounts tool (MSAC)

Asset Intelligence Remote tools

NAP Works with Windows Server 2008 operating system Network Policy Server to restrict
computers from accessing the network if they do not meet specified requirements The
System Center Family, The products included under the System Center umbrella address the
challenges of managing information technology in organizations of different sizes.

What's New

Branch distribution point

Desired configuration management

Wake On LAN

Network Access Protection (NAP)

In addition to SCCM 2007, the System Center products include: System Center Operations
Manager 2007 -Allows IT staff to monitor and manage the hardware and software in a
modern software distributed environment. System Center code name Service Desk When
it released, Service Desk is expected to provide implementations of fundamental IT
Service Management processes, including incident management, problem management, and
change management.

System Center Data Protection Manager 2006 Provides data backup and restore for
Windows file servers. System Center Essentials 2007 Provides tools for less-specialized IT
staff in smaller organizations to manage their environments more effectively with the three
most important management functions: monitoring distributed systems, automating
software updates and installing applications. System Center Virtual Machine Manager Helps
management staff with the process of consolidating applications onto virtualized servers.
System Center Capacity Planner 2006 Capacity Planner is a tool for determining what
hardware resources will be required to run an application, such as Exchange Server 2003, to
meet specific performance and availability goals.

For more information about Microsoft System Center,

SCCM Sites
A site consists of a site server, site system roles, clients, and resources. A site always
requires access to a Microsoft SQL Server database. There are several types of SCCM 2007
sites. A SCCM 2007 site uses boundaries to determine the clients belonging to the site.
Multiple sites can be configured into site hierarchies and connected such that you can
manage bandwidth utilization between sites. A SCCM 2007 site is identified by the threecharacter code and the friendly site name configured during Setup and types of sites as
follows.

Primary Sites-A primary site stores SCCM 2007 data for itself and all the sites beneath it in
a SQL Server database.
Secondary Site-A secondary site has no SCCM 2007 site database. It is attached to and
reports to a primary site. The secondary site is managed by a SCCM 2007 administrator
running a Configuration Manager 2007 console that is connected to the primary site. The
secondary site forwards the information it gathers from Configuration Manager 2007 clients,
such as computer inventory data and Configuration Manager 2007 system status

information, to its parent site. The primary site then stores the data of both the primary and
secondary sites in the SCCM 2007 site database. The advantages of using secondary sites
are that they require no additional SCCM 2007 server license and do not require the
overhead of maintaining an additional database. Secondary sites are managed from the
primary site it is connected to, so they are frequently used in sites with no local
administrator present. The disadvantage of secondary sites is that they must be attached to
a primary site and cannot be moved to a different primary site without deleting and
recreating the site. Also, secondary sites cannot have sites beneath them in the hierarchy.

Parent Site-A parent site is a primary site that has one ore more sites attached to it in the
hierarchy. Only a primary site can have child sites. A secondary site is always a child site. A
parent site contains pertinent information about its lower level sites, such as computer
inventory data and SCCM 2007 system status information, and can control many operations
at the child sites.

Child Sites-A child site is a site that is attached to a site above it in the hierarchy. The site
it reports to is its parent site. A child site can have only one parent site. SCCM 2007 copies
all the data that is collected at a child site to its parent site. A child site is either a primary
site or a secondary site.
Central Site -A central site has no parent site. Typically, a central site has child and
grandchild sites and aggregates all of their client information to provide centralized
management and reporting. A site with no parent and no child site is still called a central
site although it is also referred to as a standalone site. A central site to collect all of the site
information for centralized management.

Site Systems
Each site contains one site server and one or more site systems. The site server is the
computer where you install SCCM 2007 and it hosts services required for SCCM 2007. A site
system is any computer running a supported version of Windows or a shared folder that
hosts one or more site system roles. A site system role is a function required to use SCCM
2007 or to use a feature of SCCM 2007. Multiple site roles can be combined on a single site
system, including running all site roles on the site server, but this is usually appropriate only
for very small and simple environments.

Site System Roles

Management Point- The site system role that serves as the primary point of
contact between SCCM 2007 clients and the Configuration Manager 2007 site server.

Server locator Point -A site system role that locates management points for SCCM
2007 clients.

Distribution Point-A site system role that stores packages for clients to install.
Software Update Point-A site system role assigned to a computer running Microsoft
Windows Server Update Services (WSUS).

Reporting Point-A site system role hosts the Report Viewer component for Webbased reporting functionality.

Fallback Status Point - A site system role that gathers state messages from clients
that cannot install properly, cannot assign to a Configuration Manager 2007 site, or cannot
communicate securely with their assigned management point.

PXE Service Point-A site system role that has been configured to respond to and
initiate operating system deployments from computers whose network interface card is
configured to allow PXE boot requests. User

State Migration Point-A site system role that stores user state data while a
computer is being migrated to a new operating system.

How Site communicates?

Clients communicate with site systems hosting site system roles. Site systems communicate
with the site server and with the site database. If there are multiple sites connected in a
hierarchy, the sites communicate with their parent, child, or sometimes grandchild sites.
Site Boundaries, SCCM 2007 uses boundaries to determine when clients and site systems
are in the site and outside of the site. Boundaries can be IP subnets, IP address ranges,
IPv6 prefixes, and Active Directory sites. Two sites should never share the same boundaries.
Assigning the same IP subnet, IP address range, IPv6 prefix or Active Directory site to two
different sites makes it difficult to determine which clients should be managed in the site.

Inter-Site Communication When you have a separate sites, SCCM 2007 uses senders to
connect the two sites. Senders have sender addresses that help them locate the other site.
When sending data between sites, senders provide fault tolerance and bandwidth
management.
Intra-site Communications They use either server message block (SMB), HTTP, or HTTPS,
depending on various site configuration choices you make. Because all of these
communications are unmanaged, that is, they happen at any time with no consideration for

bandwidth consumption, it is beneficial to make sure these site elements have fast
communication channels.

Discovery Methods

Active Directory System Discovery -Discovers details about the computer

Active Directory System Group Discovery - Discovers details such as

organizational unit, global groups, universal groups, and nested groups.

Active Directory User Discovery-Retrieves Active Directory User Discovery

Active Directory Security Group Discovery-Discovers security groups created in

Active Directory.

Heartbeat Discovery-Refresh Configuration Manager client computer discovery

data in the site database.

Network Discovery-Searches the network for resources that meet a specific profile,
From router's ARP cache, SNMP agent and DHCP Each discovery method creates data
discovery records (DDRs) for resources and sends them to the site database, even if the
discovered resource is not capable of being a SCCM 2007 client.
Active Directory User Discovery and Active Directory Security Group Discovery allow you to
target software distribution packages to users and groups instead of computers.

Client Installation
SCCM 2007 provides several options for installing the client software.
The following table lists the client computer installation methods.

Software update point installation -Uses the Automatic Update configuration of a

client to direct the client computer to a WSUS computer configured as a SCCM 2007
software update point.

Client push installation -Uses an account with administrative rights to access the
client computers and install the SCCM 2007 client software.

Manual client installation -A user with administrative rights can install the client
software by running CCMSetup on the client computer. A variety of switches modify the
installation options.

Group Policy installation -Uses Group Policy software installation to install

CCMSetup.msi.

Imaging -The client software can be added to an image, including images created
and deployed with SCCM 2007 operating system deployment.

Software Distribution -Existing clients can be upgraded or redeployed using SCCM

2007 software distribution.

Mobile devices use different installation methods Client Assignment Clients must be
assigned to a site before they can be managed by that site. Clients can be assigned to a site
during installation or after installation. Assigning a client involves either telling it a specific
site code to use, or configuring the client to automatically assign to a site based on
boundaries. If the client is not assigned to any site during the client installation phase, the
client installation phase completes, but the client cannot be managed by SCCM 2007.

Clients cannot be assigned to secondary sites; they are always assigned to the parent
primary site, but can reside in the boundaries of the secondary site, taking advantage of
any proxy management points and distribution points at the secondary site. This is because
clients communicate with management points and management points must communicate
with a site database. Secondary sites do not have their own site database, They use the site
database at their parent primary site. Authenticating Clients Before SCCM 2007 trusts a

client, it requires some manner of authentication. In mixed mode, clients must be approved,
either by manually approving each client or by automatically approving all clients or all
clients in a trusted Windows domain. In native mode, clients must be issued client
authentication certificates prior to installing the SCCM 2007 client software.

Blocking Clients- If a client computer is no longer trusted, the Configuration Manager

administrator can block the client in the SCCM 2007 console.
Client Agents
Client agents are SCCM 2007 components that run on top of the base client components.

Computer Client Agent Properties-Configures how often client computers retrieve the
policy that gives them the rest of their configuration settings.
Device Client Agent Properties-Configures all of the properties specific to mobile device
clients. Hardware Inventory Client Agent-Enables and configures the agent that collects a
wide variety of information about the client computer.
Software Inventory Client Agent-Enables and configures which files Configuration
Manager inventories and collects.
Advertised Programs Client Agent-Enables and configures the software distribution
feature.
Desired Configuration Management Client Agent-Enables the client agent that
evaluates whether computers are in compliance with configuration baselines that are
assigned to them
Remote Tools Client Agent-Enables Configuration Manager remote control
Network Access Protection Client Agent-Enables Configuration Manager Network Access
Protection

Software Updates Client Agent-Enables the agent that scans for and installs software
updates on client computers.

Administrator Console

You can run the console from the site server or install additional consoles on your desktop or
help desk computers to facilitate management. One console can manage many sites or
many consoles can manage a single site. The SCCM 2007 console runs as a Microsoft
Management Console (MMC) snap-in, although you must run SCCM 2007 Setup on the
computer so that the snap-in is available.

Collections
Collections represent groups of resources and can consist not only of computers, but also of
Microsoft Windows users and user groups as well as other discovered resources. Collections
provide you with the means to organize resources into easily manageable units, enabling
you to create an organized structure that logically represents the kinds of tasks that you
want to perform.

Inventory
Hardware inventory gives you system information Software inventoried file types and
versions present on client computers Queries It uses WBEM query language (WQL) to query
the site database. Query results are returned in the SCCM 2007 console, where they can be
exported using the MMC export list feature.

Reporting
Reporting is a supporting feature to many other SCCM 2007 features. Reports are returned
in Web pages in the browser. With reporting you can create reports that show the inventory
you have collected or the software updates successfully deployed. You can also create
dashboards, which combine several different views of information. Several pre-created
reports are available to support common reporting scenarios. For more information about
the reports provided for each feature, see the feature documentation.

Software Distribution
Software distribution allows you to push just about anything to a client computer. Packages
in software distribution can contain source files to deploy software applications and
commands called programs that tell the client what executable file to run. A single package
can contain multiple programs, each configured to run differently. Packages can also contain
command lines to run files already present on the client, without actually containing
additional source files.

Software updates
The software updates feature provides a set of tools and resources that can help manage
the complex task of tracking and applying software updates to client computers in the
enterprise. Software updates in SCCM 2007 requires a Windows Server Update Services
(WSUS) server to be installed and uses that to scan the client computers for applicable
software updates. The administrator views which updates are needed in the environment
and creates packages and deployments containing the source files for the software updates.
Clients then install the software updates from distribution points and report their status
back to the site database.

Software Metering
Software metering enables you to collect and report software program usage data. The data
provided by these reports can be used by many groups within the organization such as IT
and corporate purchasing. Software metering in SCCM 2007 supports the following
scenarios: Identify which software applications are being used, and who is using them.
Identify the number of concurrent usages of a specified software application. Identify actual
software license requirements. Identify redundant software application installations. Identify
unused software applications which could be relocated.

Operating System Deployment

Operating system deployment enables you to install new operating systems and software
onto a computer. You can use operating system deployment to install operating system
images to new or existing computers as well as to computers with no connection your SCCM
2007 site. By using task sequences and the driver catalog operating system deployment
streamlines new computer installations by allowing you to install software using one
dynamic image that can be installed on different types of computers and configurations.
Operating system deployment provides the following solutions for deploying operating
system images to computers: Provide a secure operating system deployment environment.
Assist with managing the cost of deploying images by allowing one image to work with
different computer hardware configurations. Assist with unifying deployment strategies to
help provide a solid deployment foundation for future operating system deployment
methods.

Desired Configuration Management

Desired configuration management enables you to define configuration standards and
policies, and audit compliance throughout the enterprise against those defined
configurations. Best practices configurations can be used from Microsoft and vendors in the
form of Microsoft System Center SCCM 2007 Configuration Packs. These Configuration Packs
can then be refined to meet customized business requirements. Additionally, desired

configuration management supports an authoring environment for customized

configurations. This feature is designed to provide data for use by many groups within the
organization, including IT and corporate security.

Mobile Device Management

Mobile devices are supported as SCCM 2007 clients. For documentation purposes, mobile
clients are treated as a separate feature. Mobile clients can run a subset of SCCM 2007
features such as inventory and software distribution, but cannot be managed by remote
control and cannot receive operating system deployments like desktop clients.
Remote Tools
Remote tools in SCCM 2007 includes the remote control feature which allows an operator
with sufficient access rights the ability to remotely administer client computers in the SCCM
2007 site hierarchy.

Network Access Protection

Network Access Protection (NAP) is a policy enforcement platform built into the Windows
Vista and Windows Server 2008 operating systems that helps you to better protect
network assets by enforcing compliance with system health requirements. You can configure
DHCP Enforcement, VPN Enforcement, 802.1X Enforcement, IPSec Enforcement, or all four,
depending on your network needs.

Asset Intelligence
Tracking IT asset & reporting -Is an inventory monitoring capability of SCCM 2007

Wake On LAN

The Wake On LAN feature helps to achieve a higher success rate for scheduled SCCM 2007
activities, reducing associated network traffic during business hours, and helps organizations
to conserve power by not requiring computers to be left on for maintenance outside
business hours. Wake On LAN in SCCM 2007 supports the following scenarios:

Sending a wake-up transmission prior to the configured deadline for a software update
deployment. Sending a wake-up transmission prior to the configured schedule of a
mandatory advertisement, which can be for software distribution or a task sequence.

Security Modes
There are two security modes in SCCM 2007.Native mode is the recommended site
configuration for new SCCM 2007 sites because it offers a higher level of security by
integrating with a public key infrastructure (PKI) to help protect client-to-server
communication. PKIs can help companies meet their security and business requirements,
but they must be carefully designed and implemented to meet the current and future needs.
Installing a PKI solely to support SCCM 2007 operations could fulfill certain short term goals
but could hamper a more extensive PKI rollout to support other applications at a later time.
If your organization already has a well-designed, industry-standard PKI, SCCM 2007 should
be able to use certificates from the existing PKI.

Backup and Recovery

Like any enterprise software, your site should be backed up to provide recoverability in case
of unexpected events. Backing up a SCCM 2007 site involves backing up the database, the
file system, and the registry all at the same point in time - backing up just one of these
elements is not sufficient to restore a working site. SCCM 2007 uses the Volume Shadow
Copy Service (VSS) to take small, frequent snapshots of the necessary components, making
it easier to restore a failed site. The Site Repair Wizard walks you through the necessary
steps to complete the site recovery.

SCCM Logs
The client logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR
%\SysWOW64\CCM\Logs (for x64 OS).
The SCCM server log files are located in the <INSTALL_PATH>\Logs or SMS_CCM\Logs folder. IIS logs
can be found in %WINDIR%\System32\logfiles\W3SVC1 folder.

Client Log Files

CAS - Content Access Service. Maintains the local package cache.

Ccmexec.log - Records activities of the client and the SMS Agent Host service.

CertificateMaintenance.log - Maintains certificates for Active Directory directory service and

management points.

ClientIDManagerStartup.log - Creates and maintains the client GUID.

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.

DataTransferService.log - Records all BITS communication for policy or package access.

Execmgr.log - Records advertisements that run.

FileBITS.log - Records all SMB package access tasks.

Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) - Windows

Management Instrumentation (WMI) provider for software inventory and file collection.

InventoryAgent.log - Creates discovery data records (DDRs) and hardware and software
inventory records.

LocationServices.log - Finds management points and distribution points.

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.

PolicyAgentProvider.log - Records policy changes.

PolicyEvaluator.log - Records new policy settings.

Remctrl.log - Logs when the remote control component (WUSER32) starts.

Scheduler.log - Records schedule tasks for all client operations.

Smscliui.log - Records usage of the Systems Management tool in Control Panel.

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.)

Server Log Files

Ccm.log - Client Configuration Manager tasks.

Cidm.log - Records changes to the client settings by the Client Install Data Manager (CIDM).

Colleval.log - Logs when collections are created, changed, and deleted by the Collection
Evaluator.

Compsumm.log - Records Component Status Summarizer tasks.

Cscnfsvc.log - Records Courier Sender confirmation service tasks.

Dataldr.log - Processes Management Information Format (MIF) files and hardware inventory in
the Configuration Manager 2007 database.

Ddm.log - Saves DDR information to the Configuration Manager 2007 database by the
Discovery Data Manager.

Despool.log - Records incoming site-to-site communication transfers.

Distmgr.log - Records package creation, compression, delta replication, and information

updates.

Hman.log - Records site configuration changes, and publishes site information in Active
Directory Domain Services.

Inboxast.log - Records files that are moved from the management point to the corresponding
SMS\INBOXES folder.

Inboxmgr.log - Records file maintenance.

Invproc.log - Records the processing of delta MIF files for the Dataloader component from client
inventory files.

Mpcontrol.log - Records the registration of the management point with WINS. Records the
availability of the management point every 10 minutes.

Mpfdm.log - Management point component that moves client files to the corresponding
SMS\INBOXES folder.

MPMSI.log - Management point .msi installation log.

MPSetup.log - Records the management point installation wrapper process.

Ntsvrdis.log - Configuration Manager 2007 server discovery.

Offermgr.log - Records advertisement updates.

Offersum.log - Records summarization of advertisement status messages.

Policypv.log - Records updates to the client policies to reflect changes to client settings or
advertisements.

Replmgr.log - Records the replication of files between the site server components and the
Scheduler component.

Rsetup.log - Reporting point setup log.

Sched.log - Records site-to-site job and package replication.

Sender.log - Records files that are sent to other child and parent sites.

Sinvproc.log - Records client software inventory data processing to the site database in
Microsoft SQL Server.

Sitecomp.log - Records maintenance of the installed site components.

Sitectrl.log - Records site setting changes to the Sitectrl.ct0 file.

Sitestat.log - Records the monitoring process of all site systems.

Smsdbmon.log - Records database changes.

Smsexec.log - Records processing of all site server component threads.

Smsprov.log - Records WMI provider access to the site database.

SMSReportingInstall.log - Records the Reporting Point installation. This component starts the
installation tasks and processes configuration changes.

SMSSHVSetup.log - Records the success or failure (with failure reason) of installing the System
Health Validator point.

Srvacct.log - Records the maintenance of accounts when the site uses standard security.

Statmgr.log - Writes all status messages to the database.

Swmproc.log - Processes metering files and maintains settings.

Admin Console Log Files

RepairWizard.log - Records errors, warnings, and information about the process of running the
Repair Wizard.

ResourceExplorer.log - Records errors, warnings, and information about running the Resource
Explorer.

SMSAdminUI.log - Records the local Configuration Manager 2007 console tasks when you
connect to Configuration Manager 2007 sites.

Management Point Log Files

MP_Ddr.log - Records the conversion of XML.ddr records from clients, and copies them to the
site server.

MP_GetAuth.log - Records the status of the site management points.

MP_GetPolicy.log - Records policy information.

MP_Hinv.log - Converts XML hardware inventory records from clients and copies the files to the
site server.

MP_Location.log - Records location manager tasks.

MP_Policy.log - Records policy communication.

MP_Relay.log - Copies files that are collected from the client.

MP_Retry.log - Records the hardware inventory retry processes.

MP_Sinv.log - Converts XML hardware inventory records from clients and copies them to the
site server.

MP_Status.log - Converts XML.svf status message files from clients and copies them to the site
server.

Mobile Device Management Log Files

DmClientHealth.log - Records the GUIDs of all the mobile device clients that are
communicating with the Device Management Point.

DmClientRegistration.log - Records registration requests from and responses to the mobile

device client in Native mode.

DmpDatastore.log - Records all the site database connections and queries made by the Device
Management Point.

DmpDiscovery.log - Records all the discovery data from the mobile device clients on the Device
Management Point.

DmpFileCollection.log - Records mobile device file collection data from mobile device clients on
the Device Management Point.

DmpHardware.log - Records hardware inventory data from mobile device clients on the Device
Management Point.

DmpIsapi.log - Records mobile device communication data from device clients on the Device
Management Point.

dmpMSI.log - Records the MSI data for Device Management Point setup.

DMPSetup.log - Records the mobile device management setup process.

DmpSoftware.log - Records mobile device software distribution data from mobile device clients
on the Device Management Point.

DmpStatus.log - Records mobile device status messages data from mobile device clients on
the Device Management Point.

FspIsapi.log - Records Fallback Status Point communication data from mobile device clients and
client computers on the Fallback Status Point.

Mobile Device Client Log Files

DmCertEnroll.log - Records certificate enrollment data on mobile device clients.

DMCertResp.htm (in \temp) - Records HTML response from the certificate server when the
mobile device Enroller program requests a client authentication certificate on mobile device
clients.

DmClientSetup.log - Records client setup data on mobile device clients.

DmClientXfer.log - Records client transfer data for Windows Mobile Device Center and
ActiveSync deployments.

DmCommonInstaller.log - Records client transfer file installation for setting up mobile device
client transfer files on client computers.

DmInstaller.log - Records whether DMInstaller correctly calls DmClientSetup and whether

DmClientSetup exits with success or failure on mobile device clients.

DmInvExtension.log - Records Inventory Extension file installation for setting up Inventory

Extension files on client computers.

DmSvc.log - Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

CCMSetup.log - Provides information about client-based operating system actions.

CreateTSMedia.log - Provides information about task sequence media when it is created. This
log is generated on the computer running the Configuration Manager 2007 administrator
console.

DriverCatalog.log - Provides information about device drivers that have been imported into the
driver catalog.

MP_ClientIDManager.log - Provides information about the Configuration Manager 2007

management point when it responds to Configuration Manager 2007 client ID requests from
boot media or PXE. This log is generated on the Configuration Manager 2007 management
point.

MP_DriverManager.log - Provides information about the Configuration Manager 2007

management point when it responds to a request from the Auto Apply Driver task sequence
action. This log is generated on the Configuration Manager 2007 management point.

MP_Location.log - Provides information about the Configuration Manager 2007 management

point when it responds to request state store or release state store requests from the state
migration point. This log is generated on the Configuration Manager 2007 management point.

Pxecontrol.log - Provides information about the PXE Control Manager.

PXEMsi.log - Provides information about the PXE service point and is generated when the PXE
service point site server has been created.

PXESetup.log - Provides information about the PXE service point and is generated when the
PXE service point site server has been created.

Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup
logs.

SmpIsapi.log - Provides information about the state migration point Configuration Manager
2007 client request responses.

Smpmgr.log - Provides information about the results of state migration point health checks and
configuration changes.

SmpMSI.log - Provides information about the state migration point and is generated when the
state migration point site server has been created.

Smsprov.log - Provides information about the SMS provider.

Smspxe.log - Provides information about the Configuration Manager 2007 PXE service point.

SMSSMPSetup.log - Provides information about the state migration point and is generated
when the state migration point site server has been created.

Smsts.log - General location for all operating system deployment and task sequence log
events.

TaskSequenceProvider.log - Provides information about task sequences when they are

imported, exported, or edited.

USMT Log loadstate.log - Provides information about the User State Migration Tool (USMT)
regarding the restore of user state data.

USMT Log scanstate.log - Provides information about the USMT regarding the capture of user
state data.

Network Access Protection Log Files

Ccmcca.log - Logs the processing of compliance evaluation based on Configuration Manager

NAP policy processing and contains the processing of remediation for each software update
required for compliance.

CIAgent.log - Tracks the process of remediation and compliance. However, the software
updates log file, *Updateshandler.log - provides more informative details on installing the
software updates required for compliance.

locationservices.log - Used by other Configuration Manager features (for example, information

about the clients assigned site) but also contains information specific to Network Access
Protection when the client is in remediation. It records the names of the required remediation
servers (management point, software update point, and distribution points that host content
required for compliance), which are also sent in the client statement of health.

SDMAgent.log - Shared with the Configuration Manager feature desired configuration

management and contains the tracking process of remediation and compliance. However, the
software updates log file, Updateshandler.log, provides more informative details about
installing the software updates required for compliance.

SMSSha.log - The main log file for the Configuration Manager Network Access Protection client
and contains a merged statement of health information from the two Configuration Manager
components: location services (LS) and the configuration compliance agent (CCA). This log file

also contains information about the interactions between the Configuration Manager System
Health Agent and the operating system NAP agent, and also between the Configuration
Manager System Health Agent and both the configuration compliance agent and the location
services. It provides information about whether the NAP agent successfully initialized, the
statement of health data, and the statement of health response.

System Health Validator Point Log Files

Ccmperf.log -Contains information about the initialization of the System Health Validator point
performance counters.

SmsSHV.log - The main log file for the System Health Validator point; logs the basic operations
of the System Health Validator service, such as the initialization progress.

SmsSHVADCacheClient.log - Contains information about retrieving Configuration Manager

health state references from Active Directory Domain Services.

SmsSHVCacheStore.log - Contains information about the cache store used to hold the
Configuration Manager NAP health state references retrieved from Active Directory Domain
Services, such as reading from the store and purging entries from the local cache store file.
The cache store is not configurable.

SmsSHVRegistrySettings.log - Records any dynamic changes to the System Health Validator

component configuration while the service is running.

SmsSHVQuarValidator.log - Records client statement of health information and processing

operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the
following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Desired Configuration Management Log Files

ciagent.log - Provides information about downloading, storing, and accessing assigned

configuration baselines.

dcmagent.log - Provides high-level information about the evaluation of assigned configuration

baselines and desired configuration management processes.

discovery.log - Provides detailed information about the Service Modeling Language (SML)
processes.

sdmagent.log - Provides information about downloading, storing, and accessing configuration

item content.

sdmdiscagent.log - Provides high-level information about the evaluation process for the objects
and settings configured in the referenced configuration items.

Wake On LAN Log Files

Wolmgr.log - Contains information about wake-up procedures such as when to wake up

advertisements or deployments that are configured for Wake On LAN.

WolCmgr.log - Contains information about which clients need to be sent wake-up packets, the
number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files

ciamgr.log - Provides information about the addition, deletion, and modification of software
update configuration items.

distmgr.log - Provides information about the replication of software update deployment

packages.

objreplmgr.log - Provides information about the replication of software updates notification files
from a parent to child sites.

PatchDownloader.log - Provides information about the process for downloading software

updates from the update source specified in the software updates metadata to the download
destination on the site server.

replmgr.log - Provides information about the process for replicating files between sites.

smsdbmon.log - Provides information about when software update configuration items are
inserted, updated, or deleted from the site server database and creates notification files for
software updates components.

SUPSetup - Provides information about the software update point installation. When the
software update point installation completes, Installation was successful is written to this log
file.

WCM.log - Provides information about the software update point configuration and connecting
to the Windows Server Update Services (WSUS) server for subscribed update categories,
classifications, and languages.

WSUSCtrl.log - Provides information about the configuration, database connectivity, and health
of the WSUS server for the site.

wsyncmgr.log -Provides information about the software updates synchronization process.

WSUS Server Log Files

Change.log - Provides information about the WSUS server database information that has
changed.

SoftwareDistribution.log - Provides information about the software updates that are

synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

CAS.log - Provides information about the process of downloading software updates to the local
cache and cache management.

CIAgent.log - Provides information about processing configuration items, including software

updates.

LocationServices.log - Provides information about the location of the WSUS server when a scan
is initiated on the client.

PatchDownloader.log - Provides information about the process for downloading software

updates from the update source to the download destination on the site server. This log is only
on the client computer configured as the synchronization host for the Inventory Tool for
Microsoft Updates.

PolicyAgent.log - Provides information about the process for downloading, compiling, and
deleting policies on client computers.

PolicyEvaluator - Provides information about the process for evaluating policies on client
computers, including policies from software updates.

RebootCoordinator.log - Provides information about the process for coordinating system

restarts on client computers after software update installations.

ScanAgent.log - Provides information about the scan requests for software updates, what tool
is requested for the scan, the WSUS location, and so on.

ScanWrapper - Provides information about the prerequisite checks and the scan process
initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS)
2003 clients.

SdmAgent.log - Provides information about the process for verifying and decompressing
packages that contain configuration item information for software updates.

ServiceWindowManager.log - Provides information about the process for evaluating configured

maintenance windows.

smscliUI.log - Provides information about the Configuration Manager Control Panel user
interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager
Properties dialog box, opening the Program Download Monitor, and so on.

SmsWusHandler - Provides information about the scan process for the Inventory Tool for
Microsoft Updates on SMS 2003 client computers.

StateMessage.log - Provides information about when software updates state messages are
created and sent to the management point.

UpdatesDeployment.log - Provides information about the deployment on the client, including

software update activation, evaluation, and enforcement. Verbose logging shows additional
information about the interaction with the client user interface.

UpdatesHandler.log - Provides information about software update compliance scanning and

about the download and installation of software updates on the client.

UpdatesStore.log - Provides information about the compliance status for the software updates
that were assessed during the compliance scan cycle.

WUAHandler.log - Provides information about when the Windows Update Agent on the client
searches for software updates.

WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates
synchronization process. This log is only on the client computer configured as the
synchronization host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File

WindowsUpdate.log - Provides information about when the Windows Update Agent connects to
the WSUS server and retrieves the software updates for compliance assessment and whether
there are updates to the agent components.

What are the SCCM 2007 Site System roles?

SCCM 2007 supports the following 14 Site System roles, with those prefixed with [NEW]being new to
SCCM:

Site Server - The server on which you install the SCCM software.
Site Database Server - The server running SQL and hosting the SCCM Site Database (only
required for Primary Sites)
Configuration Manager Console - The interface for administering SCCM. Installed by
default on Primary Site Servers this role can also be installed on workstations to allow remote
administration.
SMS Provider - The intermediate Windows Management Instrumentation (WMI), layer that
sits between the Configuration Manager Console and the Site Database (the Configuration Manager
Console accesses the Site Database via the SMS Provider). Only required for Primary Sites.
Component Server - All SCCM Site System roles (except for the Distribution Point (DP)),
requires SCCM-specific software to be installed in order for the Site System role to function. When
such software is installed on a computer that computer becomes a Component Server.

Distribution Point (DP) - Stores SCCM Packages from where Clients can access them to
install them. Only required for the Software Distribution, Software Updates, and Advertised Task
Sequences functions of SCCM.
[NEW] Fallback Status Point - A catch all Site System for Clients that cannot be installed
because of various issues such as assignment, or their inability to communicate with their
Management Point (MP). Not required by default, but recommended to help with Client installation
issues.
Management Point (MP) - SCCM Clients do not communicate directly with the SCCM Site
Server and vice versa. Instead all communication is facilitated via the Management Point. A Default
Management Point needs to be defined in every Site that has Intranet Clients.
[NEW] Pre-boot Execution Environment (PXE) Service Point - The Site System that
responds to any computers requesting deployment of their Operating System (OS), via a PXE request.
Only required if Operating System Deployments (OSD), are going to take place using PXE boot
requests.
Reporting Point (RP) - Hosts the Report Viewer component that provides the web-based
reporting functionality of SCCM. Only required if Reports need to be run on a particular Primary Site.
Server Locator Point (SLP) - Responsible for informing SCCM Clients which MP they should
access in order to install the SCCM Client software. Only required in some Client Deployment
scenarios.
[NEW] Software Update Point (SUP) - Assigned to the computer running Windows Server
Update Services (WSUS). Only required if the Software Updates feature is going to be used.
[NEW] State Migration Point (SMP) - Stores the users state migration data when a
computers OS is migrated. Only required if the OSD feature is going to be used.
[NEW] System Health Validator Point (SHVP) - This role is assigned to the computer
running the Network Policy Service. Only required if the Network Access Protection (NAP) feature is
going to be used.

SCCM Logs and Troubleshooting

The client logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR
%\SysWOW64\CCM\Logs (for x64 OS).
The SCCM server log files are located in the <INSTALL_PATH>\Logs or SMS_CCM\Logs folder.
IIS logs can be found in %WINDIR%\System32\logfiles\W3SVC1 folder.

You can use Trace32.exe found in the Sccm2007 Toolkit, to interpret the logs easily (errors in Red,
warnings in Yellow).

Client Log Files

* CAS - Content Access Service. Maintains the local package cache.
* Ccmexec.log - Records activities of the client and the SMS Agent Host service.
* CertificateMaintenance.log - Maintains certificates for Active Directory directory service and
management points.
* ClientIDManagerStartup.log - Creates and maintains the client GUID.
* 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.
* DataTransferService.log - Records all BITS communication for policy or package access.
* Execmgr.log - Records advertisements that run.
* FileBITS.log - Records all SMB package access tasks.
* Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) - Windows
Management Instrumentation (WMI) provider for software inventory and file collection.
* InventoryAgent.log - Creates discovery data records (DDRs) and hardware and software inventory
records.
* LocationServices.log - Finds management points and distribution points.
* 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.
* PolicyAgentProvider.log - Records policy changes.
* PolicyEvaluator.log - Records new policy settings.
* Remctrl.log - Logs when the remote control component (WUSER32) starts.
* Scheduler.log - Records schedule tasks for all client operations.
* Smscliui.log - Records usage of the Systems Management tool in Control Panel.
* 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.)

Server Log Files

* Ccm.log - Client Configuration Manager tasks.
* Cidm.log - Records changes to the client settings by the Client Install Data Manager (CIDM).
* Colleval.log - Logs when collections are created, changed, and deleted by the Collection Evaluator.
* Compsumm.log - Records Component Status Summarizer tasks.
* Cscnfsvc.log - Records Courier Sender confirmation service tasks.

* Dataldr.log - Processes Management Information Format (MIF) files and hardware inventory in the
Configuration Manager 2007 database.
* Ddm.log - Saves DDR information to the Configuration Manager 2007 database by the Discovery
Data Manager.
* Despool.log - Records incoming site-to-site communication transfers.
* Distmgr.log - Records package creation, compression, delta replication, and information updates.
* Hman.log - Records site configuration changes, and publishes site information in Active Directory
Domain Services.
* Inboxast.log - Records files that are moved from the management point to the corresponding
SMS\INBOXES folder.
* Inboxmgr.log - Records file maintenance.
* Invproc.log - Records the processing of delta MIF files for the Dataloader component from client
inventory files.
* Mpcontrol.log - Records the registration of the management point with WINS. Records the
availability of the management point every 10 minutes.
* Mpfdm.log - Management point component that moves client files to the corresponding
SMS\INBOXES folder.
* MPMSI.log - Management point .msi installation log.
* MPSetup.log - Records the management point installation wrapper process.
* Ntsvrdis.log - Configuration Manager 2007 server discovery.
* Offermgr.log - Records advertisement updates.
* Offersum.log - Records summarization of advertisement status messages.
* Policypv.log - Records updates to the client policies to reflect changes to client settings or
advertisements.
* Replmgr.log - Records the replication of files between the site server components and the
Scheduler component.
* Rsetup.log - Reporting point setup log.
* Sched.log - Records site-to-site job and package replication.
* Sender.log - Records files that are sent to other child and parent sites.
* Sinvproc.log - Records client software inventory data processing to the site database in Microsoft
SQL Server.
* Sitecomp.log - Records maintenance of the installed site components.
* Sitectrl.log - Records site setting changes to the Sitectrl.ct0 file.
* Sitestat.log - Records the monitoring process of all site systems.
* Smsdbmon.log - Records database changes.
* Smsexec.log - Records processing of all site server component threads.
* Smsprov.log - Records WMI provider access to the site database.

* SMSReportingInstall.log - Records the Reporting Point installation. This component starts the
installation tasks and processes configuration changes.
* SMSSHVSetup.log - Records the success or failure (with failure reason) of installing the System
Health Validator point.
* Srvacct.log - Records the maintenance of accounts when the site uses standard security.
* Statmgr.log - Writes all status messages to the database.
* Swmproc.log - Processes metering files and maintains settings.

Admin Console Log Files

* RepairWizard.log - Records errors, warnings, and information about the process of running the
Repair Wizard.
* ResourceExplorer.log - Records errors, warnings, and information about running the Resource
Explorer.
* SMSAdminUI.log - Records the local Configuration Manager 2007 console tasks when you connect
to Configuration Manager 2007 sites.

Management Point Log Files

* MP_Ddr.log - Records the conversion of XML.ddr records from clients, and copies them to the site
server.
* MP_GetAuth.log - Records the status of the site management points.
* MP_GetPolicy.log - Records policy information.
* MP_Hinv.log - Converts XML hardware inventory records from clients and copies the files to the
site server.
* MP_Location.log - Records location manager tasks.
* MP_Policy.log - Records policy communication.
* MP_Relay.log - Copies files that are collected from the client.
* MP_Retry.log - Records the hardware inventory retry processes.
* MP_Sinv.log - Converts XML hardware inventory records from clients and copies them to the site
server.
* MP_Status.log - Converts XML.svf status message files from clients and copies them to the site
server.

Mobile Device Management Log Files

* DmClientHealth.log - Records the GUIDs of all the mobile device clients that are communicating
with the Device Management Point.
* DmClientRegistration.log - Records registration requests from and responses to the mobile device
client in Native mode.
* DmpDatastore.log - Records all the site database connections and queries made by the Device
Management Point.
* DmpDiscovery.log - Records all the discovery data from the mobile device clients on the Device
Management Point.
* DmpFileCollection.log - Records mobile device file collection data from mobile device clients on the
Device Management Point.
* DmpHardware.log - Records hardware inventory data from mobile device clients on the Device
Management Point.
* DmpIsapi.log - Records mobile device communication data from device clients on the Device
Management Point.
* dmpMSI.log - Records the MSI data for Device Management Point setup.
* DMPSetup.log - Records the mobile device management setup process.
* DmpSoftware.log - Records mobile device software distribution data from mobile device clients on
the Device Management Point.
* DmpStatus.log - Records mobile device status messages data from mobile device clients on the
Device Management Point.
* FspIsapi.log - Records Fallback Status Point communication data from mobile device clients and
client computers on the Fallback Status Point.

Mobile Device Client Log Files

* DmCertEnroll.log - Records certificate enrollment data on mobile device clients.
* DMCertResp.htm (in \temp) - Records HTML response from the certificate server when the mobile
device Enroller program requests a client authentication certificate on mobile device clients.
* DmClientSetup.log - Records client setup data on mobile device clients.
* DmClientXfer.log - Records client transfer data for Windows Mobile Device Center and ActiveSync
deployments.
* DmCommonInstaller.log - Records client transfer file installation for setting up mobile device client
transfer files on client computers.
* DmInstaller.log - Records whether DMInstaller correctly calls DmClientSetup and whether
DmClientSetup exits with success or failure on mobile device clients.
* DmInvExtension.log - Records Inventory Extension file installation for setting up Inventory
Extension files on client computers.

* DmSvc.log - Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

* CCMSetup.log - Provides information about client-based operating system actions.
* CreateTSMedia.log - Provides information about task sequence media when it is created. This log
is generated on the computer running the Configuration Manager 2007 administrator console.
* DriverCatalog.log - Provides information about device drivers that have been imported into the
driver catalog.
* MP_ClientIDManager.log - Provides information about the Configuration Manager 2007
management point when it responds to Configuration Manager 2007 client ID requests from boot
media or PXE. This log is generated on the Configuration Manager 2007 management point.
* MP_DriverManager.log - Provides information about the Configuration Manager 2007 management
point when it responds to a request from the Auto Apply Driver task sequence action. This log is
generated on the Configuration Manager 2007 management point.
* MP_Location.log - Provides information about the Configuration Manager 2007 management point
when it responds to request state store or release state store requests from the state migration point.
This log is generated on the Configuration Manager 2007 management point.
* Pxecontrol.log - Provides information about the PXE Control Manager.
* PXEMsi.log - Provides information about the PXE service point and is generated when the PXE
service point site server has been created.
* PXESetup.log - Provides information about the PXE service point and is generated when the PXE
service point site server has been created.
* Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup
logs.
* SmpIsapi.log - Provides information about the state migration point Configuration Manager 2007
client request responses.
* Smpmgr.log - Provides information about the results of state migration point health checks and
configuration changes.
* SmpMSI.log - Provides information about the state migration point and is generated when the state
migration point site server has been created.
* Smsprov.log - Provides information about the SMS provider.
* Smspxe.log - Provides information about the Configuration Manager 2007 PXE service point.
* SMSSMPSetup.log - Provides information about the state migration point and is generated when
the state migration point site server has been created.
* Smsts.log - General location for all operating system deployment and task sequence log events.
* TaskSequenceProvider.log - Provides information about task sequences when they are imported,

exported, or edited.
* USMT Log loadstate.log - Provides information about the User State Migration Tool (USMT)
regarding the restore of user state data.
* USMT Log scanstate.log - Provides information about the USMT regarding the capture of user
state data.

Network Access Protection Log Files

* Ccmcca.log - Logs the processing of compliance evaluation based on Configuration Manager NAP
policy processing and contains the processing of remediation for each software update required for
compliance.
* CIAgent.log - Tracks the process of remediation and compliance. However, the software updates
log file, *Updateshandler.log - provides more informative details on installing the software updates
required for compliance.
* locationservices.log - Used by other Configuration Manager features (for example, information
about the clients assigned site) but also contains information specific to Network Access Protection
when the client is in remediation. It records the names of the required remediation servers
(management point, software update point, and distribution points that host content required for
compliance), which are also sent in the client statement of health.
* SDMAgent.log - Shared with the Configuration Manager feature desired configuration management
and contains the tracking process of remediation and compliance. However, the software updates
log file, Updateshandler.log, provides more informative details about installing the software updates
required for compliance.
* SMSSha.log - The main log file for the Configuration Manager Network Access Protection client
and contains a merged statement of health information from the two Configuration Manager
components: location services (LS) and the configuration compliance agent (CCA). This log file also
contains information about the interactions between the Configuration Manager System Health Agent
and the operating system NAP agent, and also between the Configuration Manager System Health
Agent and both the configuration compliance agent and the location services. It provides information
about whether the NAP agent successfully initialized, the statement of health data, and the
statement of health response.

System Health Validator Point Log Files

* Ccmperf.log -Contains information about the initialization of the System Health Validator point
performance counters.
* SmsSHV.log - The main log file for the System Health Validator point; logs the basic operations of

the System Health Validator service, such as the initialization progress.

* SmsSHVADCacheClient.log - Contains information about retrieving Configuration Manager health
state references from Active Directory Domain Services.
* SmsSHVCacheStore.log - Contains information about the cache store used to hold the
Configuration Manager NAP health state references retrieved from Active Directory Domain
Services, such as reading from the store and purging entries from the local cache store file. The
cache store is not configurable.
* SmsSHVRegistrySettings.log - Records any dynamic changes to the System Health Validator
component configuration while the service is running.
* SmsSHVQuarValidator.log - Records client statement of health information and processing
operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following
location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Desired Configuration Management Log Files

* ciagent.log - Provides information about downloading, storing, and accessing assigned
configuration baselines.
* dcmagent.log - Provides high-level information about the evaluation of assigned configuration
baselines and desired configuration management processes.
* discovery.log - Provides detailed information about the Service Modeling Language (SML)
processes.
* sdmagent.log - Provides information about downloading, storing, and accessing configuration item
content.
* sdmdiscagent.log - Provides high-level information about the evaluation process for the objects and
settings configured in the referenced configuration items.

Wake On LAN Log Files

* Wolmgr.log - Contains information about wake-up procedures such as when to wake up
advertisements or deployments that are configured for Wake On LAN.
* WolCmgr.log - Contains information about which clients need to be sent wake-up packets, the
number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files

* ciamgr.log - Provides information about the addition, deletion, and modification of software update
configuration items.
* distmgr.log - Provides information about the replication of software update deployment packages.
* objreplmgr.log - Provides information about the replication of software updates notification files from
a parent to child sites.
* PatchDownloader.log - Provides information about the process for downloading software updates
from the update source specified in the software updates metadata to the download destination on
the site server.
* replmgr.log - Provides information about the process for replicating files between sites.
* smsdbmon.log - Provides information about when software update configuration items are inserted,
updated, or deleted from the site server database and creates notification files for software updates
components.
* SUPSetup - Provides information about the software update point installation. When the software
update point installation completes, Installation was successful is written to this log file.
* WCM.log - Provides information about the software update point configuration and connecting to
the Windows Server Update Services (WSUS) server for subscribed update categories,
classifications, and languages.
* WSUSCtrl.log - Provides information about the configuration, database connectivity, and health of
the WSUS server for the site.
* wsyncmgr.log -Provides information about the software updates synchronization process.

WSUS Server Log Files

* Change.log - Provides information about the WSUS server database information that has changed.
* SoftwareDistribution.log - Provides information about the software updates that are synchronized
from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

* CAS.log - Provides information about the process of downloading software updates to the local
cache and cache management.
* CIAgent.log - Provides information about processing configuration items, including software
updates.
* LocationServices.log - Provides information about the location of the WSUS server when a scan is
initiated on the client.
* PatchDownloader.log - Provides information about the process for downloading software updates
from the update source to the download destination on the site server. This log is only on the client

computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
* PolicyAgent.log - Provides information about the process for downloading, compiling, and deleting
policies on client computers.
* PolicyEvaluator - Provides information about the process for evaluating policies on client
computers, including policies from software updates.
* RebootCoordinator.log - Provides information about the process for coordinating system restarts on
client computers after software update installations.
* ScanAgent.log - Provides information about the scan requests for software updates, what tool is
requested for the scan, the WSUS location, and so on.
* ScanWrapper - Provides information about the prerequisite checks and the scan process
initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS)
2003 clients.
* SdmAgent.log - Provides information about the process for verifying and decompressing packages
that contain configuration item information for software updates.
* ServiceWindowManager.log - Provides information about the process for evaluating configured
maintenance windows.
* smscliUI.log - Provides information about the Configuration Manager Control Panel user
interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager
Properties dialog box, opening the Program Download Monitor, and so on.
* SmsWusHandler - Provides information about the scan process for the Inventory Tool for Microsoft
Updates on SMS 2003 client computers.
* StateMessage.log - Provides information about when software updates state messages are created
and sent to the management point.
* UpdatesDeployment.log - Provides information about the deployment on the client, including
software update activation, evaluation, and enforcement. Verbose logging shows additional
information about the interaction with the client user interface.
* UpdatesHandler.log - Provides information about software update compliance scanning and about
the download and installation of software updates on the client.
* UpdatesStore.log - Provides information about the compliance status for the software updates that
were assessed during the compliance scan cycle.
* WUAHandler.log - Provides information about when the Windows Update Agent on the client
searches for software updates.
* WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates
synchronization process. This log is only on the client computer configured as the synchronization
host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File

* WindowsUpdate.log - Provides information about when the Windows Update Agent connects to the
WSUS server and retrieves the software updates for compliance assessment and whether there are
updates to the agent components.

Software Distribution Troubleshooting Flowcharts

The following flowchart shows the process for Microsoft System Center Configuration
Manager 2007 package creation and distribution.

SCCM troubleshooting log files

Site Server logs:
ciamgr.log: Provides information about the addition, deletion, and modification of software update
configuration items.
distmgr.log : Provides information about the replication of software update deployment packages.
objreplmgr.log : Provides information about the replication of software updates notification files from
a parent to child sites.
PatchDownloader.log : Provides information about the process for downloading software updates
from the update source specified in the software updates metadata to the download destination on the
site server.
replmgr.log : Provides information about the process for replicating files between sites.
smsdbmon.log : Provides information about when software update configuration items are inserted,
updated, or deleted from the site server database and creates notification files for software updates
components.
SUPSetup : Provides information about the software update point installation. When the software
update point installation completes, Installation was successful is written to this log file.
WCM.log : Provides information about the software update point configuration and connecting to the
WSUS server for subscribed update categories, classifications, and languages.
WSUSCtrl.log : Provides information about the configuration, database connectivity, and health of the
WSUS server for the site.
wsyncmgr.log : Provides information about the software updates synchronization process.

WSUS Server Log Files

Change.log: Provides information about the WSUS server database information that has changed.
SoftwareDistribution.log : Provides information about the software updates that are synchronized

Client Computer Log Files

CAS.log: Provides information about the process of downloading software updates to the local cache
and cache management.
CIAgent.log:Provides information about processing configuration items, including software updates.
LocationServices.log: Provides information about the location of the WSUS server when a scan is
initiated on the client.
PatchDownloader.log:Provides information about the process for downloading software updates from

the update source to the download destination on the site server. This log is only on the client
computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
PolicyAgent.log: Provides information about the process for downloading, compiling, and deleting
policies on client computers.
PolicyEvaluator:Provides information about the process for evaluating policies on client computers,
including policies from software updates.
RebootCoordinator.log:Provides information about the process for coordinating system restarts on
client computers after software update installations.
ScanAgent.log: Provides information about the scan requests for software updates, what tool is
requested for the scan, the WSUS location, and so on.
ScanWrapper.log:Provides information about the prerequisite checks and the scan process
initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003
clients.