SCCM Interview Q & A

8/16/2019 SCCM Interview Q & A

http://slidepdf.com/reader/full/sccm-interview-q-a 1/46

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, rou!leshooting, "S#, #CM, S$% 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.

'hat is Secondary Site(

Four Main characteristics

• A !econdary !ite does not have access to a Microsoft !"# $atabase

• !econdary !ites are A#%A&! a 'hild !ite of a (rimary !ite and can only be

administered via a (rimary !ite

• !econdary !ites cannot have 'hild !ites of their own

• 'lients cannot be assigned directly to the !ite

'hat is C)*RA+ SI)(

A 'entral !ite is a 'onfiguration Manager (rimary !ite that resides at the top of the'onfiguration Manager hierarchy. All $atabase information rolls from the child to the parent and

is collected by the 'entral !ite)s 'onfiguration Manager $atabase. The 'entral !ite can

administer any site below it in the hierarchy and can send data down to those sites as well.

'hat is %RIMAR SI)(

Four main characteristics

•

The !ite has access to a Microsoft !"# !erver $atabase

• 'an administer or be administered via the 'onfiguration Manager 'onsole

• It can be a child of other (rimary !ites and can have 'hild !ites of its own

• 'lients can be assigned directly to the !ite



-ow do you install and configure Secondary site server

http**e+changeserverinfo.com*--*-/*-*installation0and0configuration0of0secondary0site0

server.asp+

-ow do you create a pac.age for Ado!e(

the command line msie+ec.e+e *1 A##2!34!5 *m M!I6(!74 *i 8Acro4ead.msi9

T4AN!F:4M!5mytransform.mst

6ow do you distribute a package;

• create a package in !''M, pointing it to the installation sources, and in the package

create an install program <you may have already done this;=

• assign $istribution (oints to your package so the contents get synched.

• create a 'ollection containing the ob>ects <users*computers= that are allowed to receivethe 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 84un Advertised (rograms9 dialog in %indows and select toinstall the program=

-ow SCCM download the patches(

&ou need to add the !oftware 2pdate (oint site role to the site, configure the software update

point as active, configure the products, classifications, sync settings, etc. in the !oftware 2pdate(oint properties. T63N, you can go to the 2pdate 4epository node and run the 4un

!ynchroni?ation action from the central primary site. :nce synchroni?ation completes, you will

see the metadata in the 'onfiguration Manager console.

-ow do you configure the S$%(

In the 'onfiguration Manager console, navigate to System CenterConfiguration

Manager * Site #ata!ase *Site Management * lt0 site code1 2 3 site name1 * Site

Settings * Site Systems

4ight0click the site system server name, and then click *ew Roles.!elect Software update point, and then click *e4t.

!pecify whether the site server will use a pro+y server when connecting to the software update point, and then click *e4t.!elect $se this server as the active software update point, and then specify the port settings

configured for the %!2! %eb site on this site system.

!pecify the synchroni?ation source for the active software update point using one of thefollowing settings like Synchroni5e from Microsoft $pdate or Synchroni5e from an

upstream update server

@eep the default setting #o not create 'S$S reporting events, and then click *e4t



!pecify whether to synchroni?e software updates on a schedule by selecting )na!le

synchroni5ation on a schedule

!pecify the update classifications for which the software updates will be synchroni?ed, and thenclick *e4t.

!pecify the products for which the software updates will be synchroni?ed, and then click *e4t.

:pen S$%Setup&log in InstallationPathBC#ogs to monitor the installation progress for thesoftware update point. %hen the installation completes, Installation was successful is

written to the log file.

:pen 'CM&log in InstallationPathBC#ogs to verify that the connection to the %!2! serverwas successful.

6ow do you Dackup !''M !erver;

To create a scheduled backup task, e+pand the !ite !ettings node and e+pand the !ite

Maintenance node, click on Tasks.

For Manual backup E !tart !M!!IT3DA'@2( service

'hat are the client deployments methods(

'lient (ush Installion, !oftware update point based installation, Group (olicy Installation, #ogon

!cript Installation, Manual Installation, 2pgrade Installation<software $istribution=

Can you discover clients those are in different A# forest(

yes.Internet0based client management, which supports the following site systems installed in a

separate forest to the site server

Management point

$istribution point!oftware update point

Fallback status point

'hat are the prere6uisite for Software $pdate %oint(

%indows !erver 2pdate !ervices <%!2!= H.-, %!2! H.- Administration 'onsole, %indows

2pdate Agent <%2A= H.-,!ite server communication to the active software update

point,Network #oad Dalancing <N#D=,Dackground Intelligent Transfer !erver <DIT!=./,%indows Installer

%hat is !M! (rovider;

The !M! (rovider is a %MI provider that allows both read and write access to the 'onfigurationManager -- site database. The !M! (rovider is used by the 'onfiguration Manager consoleThe !M! (rovider can be installed on the site database server computer, site server computer or

another server class third computer during 'onfiguration Manager -- !etup. After setup has

completed, the current installed location of the !M! (rovider is displayed on the site propertiesgeneral tab

'hat is IM$(



!M! --H Inventory Tool for Microsoft 2pdates

%hat is the use of %!2! <%indows !erver 2pdate !ervice=;

It enables administrators to deploy the latest Microsoft product updates to computers that arerunning the %indows operating system.

#ifference !etween SMS 7889 and SCCM 788:

%hat is %MI <indows Management Instrumentation=;

&ou can write %MI scripts or applications to automate administrative tasks on remote computers

'hat is S$% ; Software $pdate %oint<(

This is re1uired component of software updates, and after it is installed, the !2( is displayed as a

site system role in the 'onfiguration Manager console. The software update point site system

role must be created on a site system server that has %indows !erver 2pdate !ervices <%!2!=H.- installed.

his is how %eople come here Searching=

• sccm administrator interview 1uestions

• what is the difference between sms and sccm

• sms sccm interview 1uestions

ou want specific users>groups to run specific custom reports& 'hat should you do(

Navigate to 8!ystem 'enter 'onfiguration Manager E !ite $atabase E !ecurity 4ights E 2sers94ight click on 82sers9 and select 8Manage 'onfigMgr 2sers9

Navigate to the 8!''M !upport9 group you created earlier

J. For 8'ollection9 E 8<All Instances=9 add the following

0 8$elete resource90 8Modify resource9

0 84ead9

0 84ead resource90 82se remote tools9

. For 84eport9 E 8<All Instances=9 add the following

0 84ead9

H. For 8'omputer association9 E 8<All Instances=9 add the following

0 8'reate90 8$elete9

0 84ead9

0 84ecover user state9

K. 'lick 8Ne+t9



/. 'lick 8Ne+t9

L. 'lick 8'lose9

You have been provided with permissions on the SCCM console to create, distribute, modify and

delete packages? owever, when distributing a package there is no !istribution points listed inthe !istribution Point "i#ard$ "hat should you do?

%o designate a distribution point on a new server or server share

J. In the 'onfiguration Manager console, navigate to System CenterConfiguration

Manager * Site #ata!ase * Site Management * site nameB * Site Settings.

. 4ight0click Site Systems, point to New, and then click !erver or !erver !hare, depending

on which you want to create.

H. If you are creating a new server, use the *ew Site System Server 'i5ard to create the

site system server, and select the #istri!ution %oint check bo+ from the Availa!leRoles on the System Role Selection page to designate this server as a distribution point.

'hat are the re6uired ports used !y Configuration Manager(

http**technet.microsoft.com*en0us*library*bbLHLJ.asp+

&ou 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 serverside; 6ow !''M clients come to know that they have to use !''M %!2!;

6ow certificates created in !''M and what they called;

6ow !''M 'ommunicate securely between sites; And where do you define that setting; what

you will keep in mind before configuring !''M server to manage clients.%hat are the causes for a slow 'onfiguration Manager 'onsole connection and what would you

do to make your 'onfiguration Manager 'onsole users) e+perience better;

SCCM Interview Questions 2013

• What is the purpose of extended AD schema?

• What are MP, SLP and DP?

• Why we are using BIS?

• If c!ient is not reporting data"info then which point is fa!!s under?

• If we want to ad#ertisement a pac$age in a sing!e c!ient then how do to that?

• %ow to create co!!ections?

http://technet.microsoft.com/en-us/library/bb632618.aspx

http://kallol-sccm.blogspot.com/2012/12/sccm-interview-questions-2013.html

http://kallol-sccm.blogspot.com/2012/12/sccm-interview-questions-2013.html

http://technet.microsoft.com/en-us/library/bb632618.aspx



• What is feature of S&&M '$(? ) Internet *ased c!ient, +SD and Wa$e on LA-

• Where the SMS ser#er and c!ient !og fi!e wi!! *e store?

• What is the direct co!!ection mem*ership?

• What is the wa$e on LA?

• What is the pre.re/uisites of S&&M '$(?

• What is Wa$e on LA and how it0s wor$s?

• What is +SD? And what are the options a#ai!a*!e?

• What is diff- *etween WS1S 2 IM1?

• If p$g is not reaching the secondary ser#er then what cou!d *e a issue?

• What is AP?

• What are the issue faced whi!e distri*ute the pac$age from primary ser#er to

secondary ser#er?

• Which too! are you using to monitor SMS ser#er?

• What $ind of ma3or issues face on the c!ient side?

• What is the different *etween p$g refresh and update, where the changes wi!! *e

happen, how the p$g #ersion wi!! *e change?

• What is the SMS #ersion are you using, IM1 #ersion?

• %ow MP and DP identified c!ient? Is it possi*!e c!ient can send in#entory report to

ser#er if AD not extended?

• When AD extended in the SMS ser#er there are entry wi!! *e added in the AD, what

is that?

• What are the pre.re/uisites for SMS '$4 insta!!ation?

• If DP doesn0t wor$ then where we need to !oo$ and which are the !og fi!es wi!! you

refer?'56 %ow the c!ients send the info to MP? If it is WMI then which fi!e send the info to

WMI?'(6 What is the procedure to dep!oy p$g to c!ient and how it wor$s?

• Which !og fi!e wi!! indicate if SMS c!ient insta!! successfu!!y?



• What is the sender address? &!assification of sender, if you use Standard sender then

why we are using it?

• What are the ro!e wi!! you ena*!e in the &entra! Site?

• Different *etween Primary and Secondary site?

• What is the reason we are ena*!ing reporting point in &entra! Site?

• What is the f!ow of p$g distri*ution?

• Some of the c!ients are not getting patch insta!!ed? What cou!d *e a reason and how

to find out those c!ients and trou*!eshoot?

• What are the !ogs need to !oo$ c!ient and ser#er side?

• %ow to c!ient communicate with ser#er?

• hrough which port c!ient getting down!oad fi!e from ser#er?

• %ow did you $now that the particu!ar patch reached c!ient or not?

• %ow many MP and DP can we ena*!e a sing!e site?

• When the defau!t profi!e wi!! *e !oading in AD user 2 computers whi!e insta!! SMS?

What are the profi!e names?

• Why are we using S7L'889 enterprise edition? What is the ad#antage of that and

there are ma3or changes" &onfiguration need to *e done during the S7L '889 insta!!ation,

what is that?

• Scenario: we ha#e a one ;orest and two Domain0s, how the SMS communicate with

them if so, how to configure in *oundaries?

• here are < methods to #iew the !ogs and to do trou*!eshoot a!so-

• What are the disco#ery methods a#ai!a*!e?

• What is the defau!t schedu!e time for AD system disco#ery method?

• Which -exe fi!e wi!! use for SMS c!ient insta!!ation?

• After SMS c!ient insta!!ation, there is a one exe wi!! *e running continuous!y, what is

that?



• If the c!ient machine not in the domain then how the SMS ser#er communicate and

insta!! SMS c!ient?

• Scenario: ota! hosts: '888=988 c!ients assigned status is >es0 and 988 c!ient status

is >o0 e#en a!! the c!ient got insta!!ed SMS c!ient- What are the trou*!eshoot steps to *e

fo!!owed for reso!#ing the issue?

• %ow to $now that the particu!ar app!ication is running on c!ient machine?

• What are the defau!t co!!ections a#ai!a*!e in SMS?

• &an you te!! two resource ids? @esource id, @esource a!ue, @esource type and

system resource-

• %ow to ad#ertisement goes to c!ient?

• Which !ogs shou!d !oo$ when communication happen from primary to secondary?

%man-!og and hierarchy manager

• Site to site communication? Sitecomp-!og, hman-!og

• %ow wi!! you chec$ c!ient hea!th status?

• What are the steps needs to *e fo!!owing if a p$g needs to distri*ute production

en#ironment?

•

here is a one site and it has =88 c!ients, needs to *e dep!oyed one p$g to =8c!ients? %ow wi!! you create a co!!ection?

• here is a p$g and it wi!! *e re*ooting after insta!! the app!ication- eeds to *e

suppressing the re*oot function in the program?

• What $ind of c!ient insta!!ation method are you using?

• We ha#e a =888 c!ient and 88 c!ients are insta!!ed SMS c!ient, '88 c!ient not

insta!!ed- What cou!d *e a reason? 5=6 Why we need to extend AD? What is the name of

fi!e?

• What is SLP, BIS, Difference *"w primary and secondary ser#er, nati#e mode and

mixed mode , what is ad#antage using this

• Does internet *ased c!ient support mixed mode? o5<6 What is DP and BDP, hw wi!!

*ac$up S&&M, difference *"w SMS and S&&M 596 %ow to configure software metering for

particu!ar pac$age?



• Dep!oyed one pac$age to =8$ c!ient, howe#er =988 machines got fai!ed, how wi!!

trou*!eshoot?

• What are the sites ro!es configured?

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

• What are the features a#ai! in S&&M

• +SD. how wi!! create a +S

• What are the reports wi!! pu!!out from S&&M

• What are the components a#ai! in S&&M

• Diff *"w nati#e mode and mixed mode

• %ow wi!! setup new S&&M en#ironment

• What is BDP, what are the ro!es a#ai! in S&&M 2their function

• What is %"W in#entory !og fi!e and ser#er !og fi!es

• Diff *"w IM1 2 WS1S

• What are the ser#ice are running on S&&M ser#er and c!ient )

• What is SMS execute

• What is SMSCsiteCcomponentCmanager

• SMSCsiteCS7LC*ac$up, SMSC@eporting point, SMSCser#erC!ocatorCpoint,

SMSCtas$Cse/uencerCagent, SMSCagentChost

• What are the pac$age can distri*ute through IM1 or WS1S ) a!! Microsoft pac$age,

hot fixes, patch, Ser#ice pac$

• &onfigMgr does not a!!ow for incrementa! or differentia! *ac$ups and it a!ways adoptsa fu!! *ac$upE approach i-e- it *ac$s up e#erything that is needed to reinsta!! a site

comp!ete!y

SCCM 2007 Basics IF#e *een !oo$ing for short notes that faci!itate /uic$ understanding $now!edge on S&&M

'88(- I fina!!y put my efforts to *ring a short notes on S&&M '88( to he!p those who are

http://kallol-sccm.blogspot.com/2012/12/sccm-2007-basics.html

http://kallol-sccm.blogspot.com/2012/12/sccm-2007-basics.html



a!ready fami!iar with Systems Management Ser#er GSMS6 '884 and who wish to /uic$!y

de#e!op understanding $now!edge on FMicrosoft System &enter &onfiguration Manager

'88(F-

Microsoft S&&M .'88( G&onfigMgr6 pro#ides a comprehensi#e so!ution for change andconfiguration management for the Microsoft p!atform, ena*!ing organiHations to pro#ide

re!e#ant software and updates to users /uic$!y and cost.effecti#e!y, A!!ows I staff to

monitor and manage the hardware 2 software in a modern distri*uted en#ironment-

SCCM 2007 Features

• %W"SW In#entory

• Software Distri*ution

• Software 1pdate

• Software Metering

• +perating System Dep!oyment GImage capture"dep!oyment, 1ser State Migration,

as$ se/uence6

• Manage site accounts too! GMSA&6

• Asset Inte!!igence @emote too!s

AP Wor$s with Windows Ser#er '88 operating system etwor$ Po!icy Ser#er to restrict

computers from accessing the networ$ if they do not meet specified re/uirements he

System &enter ;ami!y, he products inc!uded under the System &enter um*re!!a address the

cha!!enges of managing information techno!ogy in organiHations of different siHes-

What's New

• Branch distri*ution point

• Desired configuration management

• Wa$e +n LA

• etwor$ Access Protection GAP6



In addition to S&&M '88(, the System &enter products inc!ude: System &enter +perations

Manager '88( .A!!ows I staff to monitor and manage the hardware and software in a

modern software distri*uted en#ironment- System &enter code name Ser#ice Des$E When

it re!eased, Ser#ice Des$E is expected to pro#ide imp!ementations of fundamenta! ISer#ice Management processes, inc!uding incident management, pro*!em management, and

change management-

System &enter Data Protection Manager '885 Pro#ides data *ac$up and restore for

Windows fi!e ser#ers- System &enter ssentia!s '88( Pro#ides too!s for !ess.specia!iHed I

staff in sma!!er organiHations to manage their en#ironments more effecti#e!y with the three

most important management functions: monitoring distri*uted systems, automating

software updates and insta!!ing app!ications- System &enter irtua! Machine Manager %e!ps

management staff with the process of conso!idating app!ications onto #irtua!iHed ser#ers-

System &enter &apacity P!anner '885 &apacity P!anner is a too! for determining what

hardware resources wi!! *e re/uired to run an app!ication, such as xchange Ser#er '884, to

meet specific performance and a#ai!a*i!ity goa!s-

;or more information a*out Microsoft System &enter,

SCCM Sites

A site consists of a site ser#er, site system ro!es, c!ients, and resources- A site a!ways

re/uires access to a Microsoft S7L Ser#er data*ase- here are se#era! types of S&&M '88(

sites- A S&&M '88( site uses *oundaries to determine the c!ients *e!onging to the site-

Mu!tip!e sites can *e configured into site hierarchies and connected such that you can

manage *andwidth uti!iHation *etween sites- A S&&M '88( site is identified *y the three.

character code and the friend!y site name configured during Setup and types of sites as

fo!!ows-

Primary Sites.A primary site stores S&&M '88( data for itse!f and a!! the sites *eneath it in

a S7L Ser#er data*ase-

Secondary Site.A secondary site has no S&&M '88( site data*ase- It is attached to and

reports to a primary site- he secondary site is managed *y a S&&M '88( administrator

running a &onfiguration Manager '88( conso!e that is connected to the primary site- he

secondary site forwards the information it gathers from &onfiguration Manager '88( c!ients,

such as computer in#entory data and &onfiguration Manager '88( system status



information, to its parent site- he primary site then stores the data of *oth the primary and

secondary sites in the S&&M '88( site data*ase- he ad#antages of using secondary sites

are that they re/uire no additiona! S&&M '88( ser#er !icense and do not re/uire the

o#erhead of maintaining an additiona! data*ase- Secondary sites are managed from the

primary site it is connected to, so they are fre/uent!y used in sites with no !oca!

administrator present- he disad#antage of secondary sites is that they must *e attached toa primary site and cannot *e mo#ed to a different primary site without de!eting and

recreating the site- A!so, secondary sites cannot ha#e sites *eneath 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- +n!y a primary site can ha#e chi!d sites- A secondary site is a!ways a chi!d site- A

parent site contains pertinent information a*out its !ower !e#e! sites, such as computer

in#entory data and S&&M '88( system status information, and can contro! many operations

at the chi!d sites-

Child Sites.A chi!d site is a site that is attached to a site a*o#e it in the hierarchy- he site

it reports to is its parent site- A chi!d site can ha#e on!y one parent site- S&&M '88( copies

a!! the data that is co!!ected at a chi!d site to its parent site- A chi!d site is either a primary

site or a secondary site-

Central Site .A centra! site has no parent site- ypica!!y, a centra! site has chi!d and

grandchi!d sites and aggregates a!! of their c!ient information to pro#ide centra!iHed

management and reporting- A site with no parent and no chi!d site is sti!! ca!!ed a centra!

site a!though it is a!so referred to as a standa!one site- A centra! site to co!!ect a!! of the site

information for centra!iHed management-

Site Systems

ach site contains one site ser#er and one or more site systems- he site ser#er is the

computer where you insta!! S&&M '88( and it hosts ser#ices re/uired for S&&M '88(- A site

system is any computer running a supported #ersion of WindowsJ or a shared fo!der that

hosts one or more site system ro!es- A site system ro!e is a function re/uired to use S&&M

'88( or to use a feature of S&&M '88(- Mu!tip!e site ro!es can *e com*ined on a sing!e site

system, inc!uding running a!! site ro!es on the site ser#er, *ut this is usua!!y appropriate on!y

for #ery sma!! and simp!e en#ironments-

Site System Roles

• Management Point. he site system ro!e that ser#es as the primary point of

contact *etween S&&M '88( c!ients and the &onfiguration Manager '88( site ser#er-



• Server locator Point .A site system ro!e that !ocates management points for S&&M

'88( c!ients-

• istri!ution Point.A site system ro!e that stores pac$ages for c!ients to insta!!-

Software 1pdate Point.A site system ro!e assigned to a computer running Microsoft

Windows Ser#er 1pdate Ser#ices GWS1S6-

• Re"orting Point.A site system ro!e hosts the @eport iewer component for We*.

*ased reporting functiona!ity-

• Fall!ac# Status Point . A site system ro!e that gathers state messages from c!ients

that cannot insta!! proper!y, cannot assign to a &onfiguration Manager '88( site, or cannot

communicate secure!y with their assigned management point-

• P$% Service Point.A site system ro!e that has *een configured to respond to and

initiate operating system dep!oyments from computers whose networ$ interface card is

configured to a!!ow PK *oot re/uests- 1ser

• State Migration Point.A site system ro!e that stores user state data whi!e a

computer is *eing migrated to a new operating system-

&ow Site communicates

&!ients communicate with site systems hosting site system ro!es- Site systems communicate

with the site ser#er and with the site data*ase- If there are mu!tip!e sites connected in ahierarchy, the sites communicate with their parent, chi!d, or sometimes grandchi!d sites-

Site Boundaries, S&&M '88( uses *oundaries to determine when c!ients and site systems

are in the site and outside of the site- Boundaries can *e IP su*nets, IP address ranges,

IP#5 prefixes, and Acti#e Directory sites- wo sites shou!d ne#er share the same *oundaries-

Assigning the same IP su*net, IP address range, IP#5 prefix or Acti#e Directory site to two

different sites ma$es it difficu!t to determine which c!ients shou!d *e managed in the site-

Inter.Site &ommunication When you ha#e a separate sites, S&&M '88( uses senders to

connect the two sites- Senders ha#e sender addresses that he!p them !ocate the other site-

When sending data *etween sites, senders pro#ide fau!t to!erance and *andwidth

management-

Intra.site &ommunications hey use either ser#er message *!oc$ GSMB6, %P, or %PS,

depending on #arious site configuration choices you ma$e- Because a!! of these

communications are unmanaged, that is, they happen at any time with no consideration for



*andwidth consumption, it is *eneficia! to ma$e sure these site e!ements ha#e fast

communication channe!s-

iscovery Methods

•

(ctive irectory System iscovery .Disco#ers detai!s a*out the computer

• (ctive irectory System )rou" iscovery . Disco#ers detai!s such as

organiHationa! unit, g!o*a! groups, uni#ersa! groups, and nested groups-

• (ctive irectory *ser iscovery+Retrieves Acti#e Directory 1ser Disco#ery

• (ctive irectory Security )rou" iscovery.Disco#ers security groups created in

Acti#e Directory-

• &eart!eat iscovery.@efresh &onfiguration Manager c!ient computer disco#ery

data in the site data*ase-

• Networ# iscovery.Searches the networ$ for resources that meet a specific profi!e,

;rom routerFs A@P cache, SMP agent and D%&P ach disco#ery method creates data

disco#ery records GDD@s6 for resources and sends them to the site data*ase, e#en if the

disco#ered resource is not capa*!e of *eing a S&&M '88( c!ient-

Acti#e Directory 1ser Disco#ery and Acti#e Directory Security roup Disco#ery a!!ow you to

target software distri*ution pac$ages to users and groups instead of computers-

Client ,nstallation

S&&M '88( pro#ides se#era! options for insta!!ing the c!ient software-

he fo!!owing ta*!e !ists the c!ient computer insta!!ation methods-



• So-tware u"date "oint installation .1ses the Automatic 1pdate configuration of a

c!ient to direct the c!ient computer to a WS1S computer configured as a S&&M '88(

software update point-

• Client "ush installation .1ses an account with administrati#e rights to access the

c!ient computers and insta!! the S&&M '88( c!ient software-

• Manual client installation .A user with administrati#e rights can insta!! the c!ient

software *y running &&MSetup on the c!ient computer- A #ariety of switches modify the

insta!!ation options-

• )rou" Policy installation .1ses roup Po!icy software insta!!ation to insta!!

&&MSetup-msi-

• ,maging .he c!ient software can *e added to an image, inc!uding images created

and dep!oyed with S&&M '88( operating system dep!oyment-

• Software Distri*ution .xisting c!ients can *e upgraded or redep!oyed using S&&M

'88( software distri*ution-

Mo*i!e de#ices use different insta!!ation methods &!ient Assignment &!ients must *e

assigned to a site *efore they can *e managed *y that site- &!ients can *e assigned to a site

during insta!!ation or after insta!!ation- Assigning a c!ient in#o!#es either te!!ing it a specific

site code to use, or configuring the c!ient to automatica!!y assign to a site *ased on

*oundaries- If the c!ient is not assigned to any site during the c!ient insta!!ation phase, the

c!ient insta!!ation phase comp!etes, *ut the c!ient cannot *e managed *y S&&M '88(-

&!ients cannot *e assigned to secondary sites they are a!ways assigned to the parent

primary site, *ut can reside in the *oundaries of the secondary site, ta$ing ad#antage of

any proxy management points and distri*ution points at the secondary site- his is *ecause

c!ients communicate with management points and management points must communicate

with a site data*ase- Secondary sites do not ha#e their own site data*ase, hey use the site

data*ase at their parent primary site- Authenticating &!ients Before S&&M '88( trusts a



c!ient, it re/uires some manner of authentication- In mixed mode, c!ients must *e appro#ed,

either *y manua!!y appro#ing each c!ient or *y automatica!!y appro#ing a!! c!ients or a!!

c!ients in a trusted Windows domain- In nati#e mode, c!ients must *e issued c!ient

authentication certificates prior to insta!!ing the S&&M '88( c!ient software-

.loc#ing Clients. If a c!ient computer is no !onger trusted, the &onfiguration Manager

administrator can *!oc$ the c!ient in the S&&M '88( conso!e-

Client (gents

&!ient agents are S&&M '88( components that run on top of the *ase c!ient components-

Com"uter Client (gent Pro"erties.&onfigures how often c!ient computers retrie#e the

po!icy that gi#es them the rest of their configuration settings-

evice Client (gent Pro"erties.&onfigures a!! of the properties specific to mo*i!e de#ice

c!ients- %ardware In#entory &!ient Agent.na*!es and configures the agent that co!!ects a

wide #ariety of information a*out the c!ient computer-

So-tware ,nventory Client (gent.na*!es and configures which fi!es &onfiguration

Manager in#entories and co!!ects-

(dvertised Programs Client (gent.na*!es and configures the software distri*ution

feature-

esired Con-iguration Management Client (gent.na*!es the c!ient agent that

e#a!uates whether computers are in comp!iance with configuration *ase!ines that are

assigned to them

Remote /ools Client (gent.na*!es &onfiguration Manager remote contro!

Networ# (ccess Protection Client (gent.na*!es &onfiguration Manager etwor$ Access

Protection

So-tware *"dates Client (gent.na*!es the agent that scans for and insta!!s softwareupdates on c!ient computers-

(dministrator Console



ou can run the conso!e from the site ser#er or insta!! additiona! conso!es on your des$top or

he!p des$ computers to faci!itate management- +ne conso!e can manage many sites or

many conso!es can manage a sing!e site- he S&&M '88( conso!e runs as a Microsoft

Management &onso!e GMM&6 snap.in, a!though you must run S&&M '88( Setup on the

computer so that the snap.in is a#ai!a*!e-

Collections

&o!!ections represent groups of resources and can consist not on!y of computers, *ut a!so of

Microsoft Windows users and user groups as we!! as other disco#ered resources- &o!!ections

pro#ide you with the means to organiHe resources into easi!y managea*!e units, ena*!ing

you to create an organiHed structure that !ogica!!y represents the $inds of tas$s that you

want to perform-

,nventory

%ardware in#entory gi#es you system information Software in#entoried fi!e types and

#ersions present on c!ient computers 7ueries It uses WBM /uery !anguage GW7L6 to /uery

the site data*ase- 7uery resu!ts are returned in the S&&M '88( conso!e, where they can *e

exported using the MM& export !ist feature-

Re"orting

@eporting is a supporting feature to many other S&&M '88( features- @eports are returned

in We* pages in the *rowser- With reporting you can create reports that show the in#entory

you ha#e co!!ected or the software updates successfu!!y dep!oyed- ou can a!so create

dash*oards, which com*ine se#era! different #iews of information- Se#era! pre.created

reports are a#ai!a*!e to support common reporting scenarios- ;or more information a*out

the reports pro#ided for each feature, see the feature documentation-

So-tware istri!ution

Software distri*ution a!!ows you to push 3ust a*out anything to a c!ient computer- Pac$agesin software distri*ution can contain source fi!es to dep!oy software app!ications and

commands ca!!ed programs that te!! the c!ient what executa*!e fi!e to run- A sing!e pac$age

can contain mu!tip!e programs, each configured to run different!y- Pac$ages can a!so contain

command !ines to run fi!es a!ready present on the c!ient, without actua!!y containing

additiona! source fi!es-



So-tware u"dates

he software updates feature pro#ides a set of too!s and resources that can he!p manage

the comp!ex tas$ of trac$ing and app!ying software updates to c!ient computers in the

enterprise- Software updates in S&&M '88( re/uires a Windows Ser#er 1pdate Ser#ices

GWS1S6 ser#er to *e insta!!ed and uses that to scan the c!ient computers for app!ica*!esoftware updates- he administrator #iews which updates are needed in the en#ironment

and creates pac$ages and dep!oyments containing the source fi!es for the software updates-

&!ients then insta!! the software updates from distri*ution points and report their status

*ac$ to the site data*ase-

So-tware Metering

Software metering ena*!es you to co!!ect and report software program usage data- he data

pro#ided *y these reports can *e used *y many groups within the organiHation such as I

and corporate purchasing- Software metering in S&&M '88( supports the fo!!owingscenarios: Identify which software app!ications are *eing used, and who is using them-

Identify the num*er of concurrent usages of a specified software app!ication- Identify actua!

software !icense re/uirements- Identify redundant software app!ication insta!!ations- Identify

unused software app!ications which cou!d *e re!ocated-

"erating System e"loyment

+perating system dep!oyment ena*!es you to insta!! new operating systems and software

onto a computer- ou can use operating system dep!oyment to insta!! operating system

images to new or existing computers as we!! as to computers with no connection your S&&M'88( site- By using tas$ se/uences and the dri#er cata!og operating system dep!oyment

stream!ines new computer insta!!ations *y a!!owing you to insta!! software using one

dynamic image that can *e insta!!ed on different types of computers and configurations-

+perating system dep!oyment pro#ides the fo!!owing so!utions for dep!oying operating

system images to computers: Pro#ide a secure operating system dep!oyment en#ironment-

Assist with managing the cost of dep!oying images *y a!!owing one image to wor$ with

different computer hardware configurations- Assist with unifying dep!oyment strategies to

he!p pro#ide a so!id dep!oyment foundation for future operating system dep!oyment

methods-

esired Con-iguration Management

Desired configuration management ena*!es you to define configuration standards and

po!icies, and audit comp!iance throughout the enterprise against those defined

configurations- Best practices configurations can *e used from Microsoft and #endors in the

form of Microsoft System &enter S&&M '88( &onfiguration Pac$s- hese &onfiguration Pac$s

can then *e refined to meet customiHed *usiness re/uirements- Additiona!!y, desired



configuration management supports an authoring en#ironment for customiHed

configurations- his feature is designed to pro#ide data for use *y many groups within the

organiHation, inc!uding I and corporate security-

Mo!ile evice Management

Mo*i!e de#ices are supported as S&&M '88( c!ients- ;or documentation purposes, mo*i!e

c!ients are treated as a separate feature- Mo*i!e c!ients can run a su*set of S&&M '88(

features such as in#entory and software distri*ution, *ut cannot *e managed *y remote

contro! and cannot recei#e operating system dep!oyments !i$e des$top c!ients-

Remote /ools

@emote too!s in S&&M '88( inc!udes the remote contro! feature which a!!ows an operator

with sufficient access rights the a*i!ity to remote!y administer c!ient computers in the S&&M

'88( site hierarchy-

Networ# (ccess Protection

etwor$ Access Protection GAP6 is a po!icy enforcement p!atform *ui!t into the Windows

ista and Windows Ser#erJ '88 operating systems that he!ps you to *etter protect

networ$ assets *y enforcing comp!iance with system hea!th re/uirements- ou can configure

D%&P nforcement, P nforcement, 8'-=K nforcement, IPSec nforcement, or a!! four,

depending on your networ$ needs-

(sset ,ntelligence

rac$ing I asset 2 reporting .Is an in#entory monitoring capa*i!ity of S&&M '88(

Wa#e n 1(N



he Wa$e +n LA feature he!ps to achie#e a higher success rate for schedu!ed S&&M '88(

acti#ities, reducing associated networ$ traffic during *usiness hours, and he!ps organiHations

to conser#e power *y not re/uiring computers to *e !eft on for maintenance outside

*usiness hours- Wa$e +n LA in S&&M '88( supports the fo!!owing scenarios:

Sending a wa$e.up transmission prior to the configured dead!ine for a software update

dep!oyment- Sending a wa$e.up transmission prior to the configured schedu!e of a

mandatory ad#ertisement, which can *e for software distri*ution or a tas$ se/uence-

Security Modes

here are two security modes in S&&M '88(-ati#e mode is the recommended site

configuration for new S&&M '88( sites *ecause it offers a higher !e#e! of security *y

integrating with a pu*!ic $ey infrastructure GPNI6 to he!p protect c!ient.to.ser#ercommunication- PNIs can he!p companies meet their security and *usiness re/uirements,

*ut they must *e carefu!!y designed and imp!emented to meet the current and future needs-

Insta!!ing a PNI so!e!y to support S&&M '88( operations cou!d fu!fi!! certain short term goa!s

*ut cou!d hamper a more extensi#e PNI ro!!out to support other app!ications at a !ater time-

If your organiHation a!ready has a we!!.designed, industry.standard PNI, S&&M '88( shou!d

*e a*!e to use certificates from the existing PNI-

.ac#u" and Recovery

Li$e any enterprise software, your site shou!d *e *ac$ed up to pro#ide reco#era*i!ity in case

of unexpected e#ents- Bac$ing up a S&&M '88( site in#o!#es *ac$ing up the data*ase, the

fi!e system, and the registry a!! at the same point in time . *ac$ing up 3ust one of these

e!ements is not sufficient to restore a wor$ing site- S&&M '88( uses the o!ume Shadow

&opy Ser#ice GSS6 to ta$e sma!!, fre/uent snapshots of the necessary components, ma$ing

it easier to restore a fai!ed site- he Site @epair WiHard wa!$s you through the necessary

steps to comp!ete the site reco#ery-

SCCM Logs

The client logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR

%\SysWW!"\CCM\Logs #for $!" S&

The SCCM ser'er log (les are located in the )INST*LL+,*T-.\Logs or SMS+CCM\Logs folder& IIS logs

can /e fo0nd in %WINDIR%\System32\log(les\W3S1C folder&

http://kallol-sccm.blogspot.com/2012/12/sccm-logs.html

http://kallol-sccm.blogspot.com/2012/12/sccm-logs.html



Client Log iles

• C*S 4 Content *ccess Ser'ice& Maintains the local 5ac6age cache&

• Ccme$ec&log 4 Records acti'ities of the client and the SMS *gent -ost ser'ice&

• Certi(cateMaintenance&log 4 Maintains certi(cates for *cti'e Directory directory ser'ice and

management 5oints&

• ClientIDManagerStart05&log 4 Creates and maintains the client 78ID&

• ClientLocation&log 4 Site assignment tas6s&

• ContentTransferManager&log 4 Sched0les the 9ac6gro0nd Intelligent Transfer Ser'ice #9ITS or

the Ser'er Message 9loc6 #SM9 to do:nload or to access SMS 5ac6ages&

• DataTransferSer'ice&log 4 Records all 9ITS comm0nication for 5olicy or 5ac6age access&

• ;$ecmgr&log 4 Records ad'ertisements that r0n&

• ile9ITS&log 4 Records all SM9 5ac6age access tas6s&

• sin'5ro'ider&log #renamed to ileSystemile&log in all SMS 2<<3 Ser'ice ,ac6s 4 Windo:s

Management Instr0mentation #WMI 5ro'ider for soft:are in'entory and (le collection&

• In'entory*gent&log 4 Creates disco'ery data records #DDRs and hard:are and soft:are

in'entory records&

• LocationSer'ices&log 4 inds management 5oints and distri/0tion 5oints&

• Mif5ro'ider&log 4 The WMI 5ro'ider for &MI (les&

• Mtrmgr&log 4 Monitors all soft:are metering 5rocesses&

• ,olicy*gent&log 4 Re=0ests 5olicies /y 0sing the Data Transfer ser'ice&

• ,olicy*gent,ro'ider&log 4 Records 5olicy changes&

•

,olicy;'al0ator&log 4 Records ne: 5olicy settings&

• Remctrl&log 4 Logs :hen the remote control com5onent #W8S;R32 starts&

• Sched0ler&log 4 Records sched0le tas6s for all client o5erations&

• Smscli0i&log 4 Records 0sage of the Systems Management tool in Control ,anel&



• Stat0s*gent&log 4 Logs stat0s messages that are created /y the client com5onents&

• SWMTRRe5ort7en&log 4 7enerates a 0sage data re5ort that is collected /y the metering agent&

#This data is logged in Mtrmgr&log&

Ser'er Log iles

• Ccm&log 4 Client Con(g0ration Manager tas6s&

• Cidm&log 4 Records changes to the client settings /y the Client Install Data Manager #CIDM&

• Colle'al&log 4 Logs :hen collections are created> changed> and deleted /y the Collection

;'al0ator&

• Com5s0mm&log 4 Records Com5onent Stat0s S0mmari?er tas6s&

• Cscnfs'c&log 4 Records Co0rier Sender con(rmation ser'ice tas6s&

• Dataldr&log 4 ,rocesses Management Information ormat #MI (les and hard:are in'entory in

the Con(g0ration Manager 2<<@ data/ase&

• Ddm&log 4 Sa'es DDR information to the Con(g0ration Manager 2<<@ data/ase /y the

Disco'ery Data Manager&

• Des5ool&log 4 Records incoming site4to4site comm0nication transfers&

• Distmgr&log 4 Records 5ac6age creation> com5ression> delta re5lication> and information

05dates&

• -man&log 4 Records site con(g0ration changes> and 50/lishes site information in *cti'e

Directory Domain Ser'ices&

• In/o$ast&log 4 Records (les that are mo'ed from the management 5oint to the corres5onding

SMS\IN9A;S folder&

• In/o$mgr&log 4 Records (le maintenance&

• In'5roc&log 4 Records the 5rocessing of delta MI (les for the Dataloader com5onent from client

in'entory (les&

• M5control&log 4 Records the registration of the management 5oint :ith WINS& Records the

a'aila/ility of the management 5oint e'ery < min0tes&

• M5fdm&log 4 Management 5oint com5onent that mo'es client (les to the corres5onding

SMS\IN9A;S folder&



• M,MSI&log 4 Management 5oint &msi installation log&

• M,Set05&log 4 Records the management 5oint installation :ra55er 5rocess&

• Nts'rdis&log 4 Con(g0ration Manager 2<<@ ser'er disco'ery&

• Bermgr&log 4 Records ad'ertisement 05dates&

• Bers0m&log 4 Records s0mmari?ation of ad'ertisement stat0s messages&

• ,olicy5'&log 4 Records 05dates to the client 5olicies to reect changes to client settings or

ad'ertisements&

• Re5lmgr&log 4 Records the re5lication of (les /et:een the site ser'er com5onents and the

Sched0ler com5onent&

• Rset05&log 4 Re5orting 5oint set05 log&

• Sched&log 4 Records site4to4site o/ and 5ac6age re5lication&

• Sender&log 4 Records (les that are sent to other child and 5arent sites&

• Sin'5roc&log 4 Records client soft:are in'entory data 5rocessing to the site data/ase in

Microsoft SEL Ser'er&

• Sitecom5&log 4 Records maintenance of the installed site com5onents&

• Sitectrl&log 4 Records site setting changes to the Sitectrl&ct< (le&

• Sitestat&log 4 Records the monitoring 5rocess of all site systems&

• Smsd/mon&log 4 Records data/ase changes&

• Smse$ec&log 4 Records 5rocessing of all site ser'er com5onent threads&

• Sms5ro'&log 4 Records WMI 5ro'ider access to the site data/ase&

• SMSRe5ortingInstall&log 4 Records the Re5orting ,oint installation& This com5onent starts the

installation tas6s and 5rocesses con(g0ration changes&

• SMSS-1Set05&log 4 Records the s0ccess or fail0re #:ith fail0re reason of installing the System

-ealth 1alidator 5oint&

• Sr'acct&log 4 Records the maintenance of acco0nts :hen the site 0ses standard sec0rity&

• Statmgr&log 4 Writes all stat0s messages to the data/ase&



• S:m5roc&log 4 ,rocesses metering (les and maintains settings&

*dmin Console Log iles

• Re5airWi?ard&log 4 Records errors> :arnings> and information a/o0t the 5rocess of r0nning the

Re5air Wi?ard&

• Reso0rce;$5lorer&log 4 Records errors> :arnings> and information a/o0t r0nning the Reso0rce

;$5lorer&

• SMS*dmin8I&log 4 Records the local Con(g0ration Manager 2<<@ console tas6s :hen yo0

connect to Con(g0ration Manager 2<<@ sites&

Management ,oint Log iles

• M,+Ddr&log 4 Records the con'ersion of AML&ddr records from clients> and co5ies them to the

site ser'er&

• M,+7et*0th&log 4 Records the stat0s of the site management 5oints&

• M,+7et,olicy&log 4 Records 5olicy information&

• M,+-in'&log 4 Con'erts AML hard:are in'entory records from clients and co5ies the (les to the

site ser'er&

• M,+Location&log 4 Records location manager tas6s&

• M,+,olicy&log 4 Records 5olicy comm0nication&

• M,+Relay&log 4 Co5ies (les that are collected from the client&

• M,+Retry&log 4 Records the hard:are in'entory retry 5rocesses&

• M,+Sin'&log 4 Con'erts AML hard:are in'entory records from clients and co5ies them to the

site ser'er&

• M,+Stat0s&log 4 Con'erts AML&s'f stat0s message (les from clients and co5ies them to the site

ser'er&

Mo/ile De'ice Management Log iles

• DmClient-ealth&log 4 Records the 78IDs of all the mo/ile de'ice clients that are

comm0nicating :ith the De'ice Management ,oint&

• DmClientRegistration&log 4 Records registration re=0ests from and res5onses to the mo/ile

de'ice client in Nati'e mode&



• Dm5Datastore&log 4 Records all the site data/ase connections and =0eries made /y the De'ice

Management ,oint&

• Dm5Disco'ery&log 4 Records all the disco'ery data from the mo/ile de'ice clients on the De'ice

Management ,oint&

• Dm5ileCollection&log 4 Records mo/ile de'ice (le collection data from mo/ile de'ice clients on

the De'ice Management ,oint&

• Dm5-ard:are&log 4 Records hard:are in'entory data from mo/ile de'ice clients on the De'ice

Management ,oint&

• Dm5Isa5i&log 4 Records mo/ile de'ice comm0nication data from de'ice clients on the De'ice

Management ,oint&

• dm5MSI&log 4 Records the MSI data for De'ice Management ,oint set05&

• DM,Set05&log 4 Records the mo/ile de'ice management set05 5rocess&

• Dm5Soft:are&log 4 Records mo/ile de'ice soft:are distri/0tion data from mo/ile de'ice clients

on the De'ice Management ,oint&

• Dm5Stat0s&log 4 Records mo/ile de'ice stat0s messages data from mo/ile de'ice clients on

the De'ice Management ,oint&

• s5Isa5i&log 4 Records all/ac6 Stat0s ,oint comm0nication data from mo/ile de'ice clients and

client com50ters on the all/ac6 Stat0s ,oint&

Mo/ile De'ice Client Log iles

• DmCert;nroll&log 4 Records certi(cate enrollment data on mo/ile de'ice clients&

• DMCertRes5&htm #in \tem5 4 Records -TML res5onse from the certi(cate ser'er :hen the

mo/ile de'ice ;nroller 5rogram re=0ests a client a0thentication certi(cate on mo/ile de'ice

clients&

• DmClientSet05&log 4 Records client set05 data on mo/ile de'ice clients&

•

DmClientAfer&log 4 Records client transfer data for Windo:s Mo/ile De'ice Center and*cti'eSync de5loyments&

• DmCommonInstaller&log 4 Records client transfer (le installation for setting 05 mo/ile de'ice

client transfer (les on client com50ters&

• DmInstaller&log 4 Records :hether DMInstaller correctly calls DmClientSet05 and :hether

DmClientSet05 e$its :ith s0ccess or fail0re on mo/ile de'ice clients&



• DmIn';$tension&log 4 Records In'entory ;$tension (le installation for setting 05 In'entory

;$tension (les on client com50ters&

• DmS'c&log 4 Records mo/ile de'ice management ser'ice data on mo/ile de'ice clients&

5erating System De5loyment Log iles

• CCMSet05&log 4 ,ro'ides information a/o0t client4/ased o5erating system actions&

• CreateTSMedia&log 4 ,ro'ides information a/o0t tas6 se=0ence media :hen it is created& This

log is generated on the com50ter r0nning the Con(g0ration Manager 2<<@ administrator

console&

• Dri'erCatalog&log 4 ,ro'ides information a/o0t de'ice dri'ers that ha'e /een im5orted into the

dri'er catalog&

• M,+ClientIDManager&log 4 ,ro'ides information a/o0t the Con(g0ration Manager 2<<@management 5oint :hen it res5onds to Con(g0ration Manager 2<<@ client ID re=0ests from

/oot media or ,A;& This log is generated on the Con(g0ration Manager 2<<@ management

5oint&

• M,+Dri'erManager&log 4 ,ro'ides information a/o0t the Con(g0ration Manager 2<<@

management 5oint :hen it res5onds to a re=0est from the *0to *55ly Dri'er tas6 se=0ence

action& This log is generated on the Con(g0ration Manager 2<<@ management 5oint&

• M,+Location&log 4 ,ro'ides information a/o0t the Con(g0ration Manager 2<<@ management

5oint :hen it res5onds to re=0est state store or release state store re=0ests from the state

migration 5oint& This log is generated on the Con(g0ration Manager 2<<@ management 5oint&

• ,$econtrol&log 4 ,ro'ides information a/o0t the ,A; Control Manager&

• ,A;Msi&log 4 ,ro'ides information a/o0t the ,A; ser'ice 5oint and is generated :hen the ,A;

ser'ice 5oint site ser'er has /een created&

• ,A;Set05&log 4 ,ro'ides information a/o0t the ,A; ser'ice 5oint and is generated :hen the

,A; ser'ice 5oint site ser'er has /een created&

• Set05act&log Set05a5i&log Set05err&log ,ro'ide information a/o0t Windo:s Sys5re5 and set05

logs&

• Sm5Isa5i&log 4 ,ro'ides information a/o0t the state migration 5oint Con(g0ration Manager

2<<@ client re=0est res5onses&

• Sm5mgr&log 4 ,ro'ides information a/o0t the res0lts of state migration 5oint health chec6s and

con(g0ration changes&



• Sm5MSI&log 4 ,ro'ides information a/o0t the state migration 5oint and is generated :hen the

state migration 5oint site ser'er has /een created&

• Sms5ro'&log 4 ,ro'ides information a/o0t the SMS 5ro'ider&

•

Sms5$e&log 4 ,ro'ides information a/o0t the Con(g0ration Manager 2<<@ ,A; ser'ice 5oint&

• SMSSM,Set05&log 4 ,ro'ides information a/o0t the state migration 5oint and is generated

:hen the state migration 5oint site ser'er has /een created&

• Smsts&log 4 7eneral location for all o5erating system de5loyment and tas6 se=0ence log

e'ents&

• Tas6Se=0ence,ro'ider&log 4 ,ro'ides information a/o0t tas6 se=0ences :hen they are

im5orted> e$5orted> or edited&

• 8SMT Log loadstate&log 4 ,ro'ides information a/o0t the 8ser State Migration Tool #8SMT

regarding the restore of 0ser state data&

• 8SMT Log scanstate&log 4 ,ro'ides information a/o0t the 8SMT regarding the ca5t0re of 0ser

state data&

Net:or6 *ccess ,rotection Log iles

• Ccmcca&log 4 Logs the 5rocessing of com5liance e'al0ation /ased on Con(g0ration Manager

N*, 5olicy 5rocessing and contains the 5rocessing of remediation for each soft:are 05date

re=0ired for com5liance&

• CI*gent&log 4 Trac6s the 5rocess of remediation and com5liance& -o:e'er> the soft:are

05dates log (le> F85dateshandler&log 4 5ro'ides more informati'e details on installing the

soft:are 05dates re=0ired for com5liance&

• locationser'ices&log 4 8sed /y other Con(g0ration Manager feat0res #for e$am5le> information

a/o0t the clientGs assigned site /0t also contains information s5eci(c to Net:or6 *ccess

,rotection :hen the client is in remediation& It records the names of the re=0ired remediation

ser'ers #management 5oint> soft:are 05date 5oint> and distri/0tion 5oints that host content

re=0ired for com5liance> :hich are also sent in the client statement of health&

• SDM*gent&log 4 Shared :ith the Con(g0ration Manager feat0re desired con(g0ration

management and contains the trac6ing 5rocess of remediation and com5liance& -o:e'er> the

soft:are 05dates log (le> 85dateshandler&log> 5ro'ides more informati'e details a/o0t

installing the soft:are 05dates re=0ired for com5liance&

• SMSSha&log 4 The main log (le for the Con(g0ration Manager Net:or6 *ccess ,rotection client

and contains a merged statement of health information from the t:o Con(g0ration Manager

com5onentsH location ser'ices #LS and the con(g0ration com5liance agent #CC*& This log (le



also contains information a/o0t the interactions /et:een the Con(g0ration Manager System

-ealth *gent and the o5erating system N*, agent> and also /et:een the Con(g0ration

Manager System -ealth *gent and /oth the con(g0ration com5liance agent and the location

ser'ices& It 5ro'ides information a/o0t :hether the N*, agent s0ccessf0lly initiali?ed> the

statement of health data> and the statement of health res5onse&

System -ealth 1alidator ,oint Log iles

• Ccm5erf&log 4Contains information a/o0t the initiali?ation of the System -ealth 1alidator 5oint

5erformance co0nters&

• SmsS-1&log 4 The main log (le for the System -ealth 1alidator 5oint logs the /asic o5erations

of the System -ealth 1alidator ser'ice> s0ch as the initiali?ation 5rogress&

• SmsS-1*DCacheClient&log 4 Contains information a/o0t retrie'ing Con(g0ration Manager

health state references from *cti'e Directory Domain Ser'ices&

• SmsS-1CacheStore&log 4 Contains information a/o0t the cache store 0sed to hold the

Con(g0ration Manager N*, health state references retrie'ed from *cti'e Directory Domain

Ser'ices> s0ch as reading from the store and 50rging entries from the local cache store (le&

The cache store is not con(g0ra/le&

• SmsS-1RegistrySettings&log 4 Records any dynamic changes to the System -ealth 1alidator

com5onent con(g0ration :hile the ser'ice is r0nning&

• SmsS-1E0ar1alidator&log 4 Records client statement of health information and 5rocessing

o5erations& To o/tain f0ll information> change the registry 6ey LogLe'el from to < in the

follo:ing locationH-JLM\STW*R;\Microsoft\SMSS-1\Logging\K7L9*L

Desired Con(g0ration Management Log iles

• ciagent&log 4 ,ro'ides information a/o0t do:nloading> storing> and accessing assigned

con(g0ration /aselines&

• dcmagent&log 4 ,ro'ides high4le'el information a/o0t the e'al0ation of assigned con(g0ration

/aselines and desired con(g0ration management 5rocesses&

• disco'ery&log 4 ,ro'ides detailed information a/o0t the Ser'ice Modeling Lang0age #SML

5rocesses&

• sdmagent&log 4 ,ro'ides information a/o0t do:nloading> storing> and accessing con(g0ration

item content&

• sdmdiscagent&log 4 ,ro'ides high4le'el information a/o0t the e'al0ation 5rocess for the o/ects

and settings con(g0red in the referenced con(g0ration items&



Wa6e n L*N Log iles

• Wolmgr&log 4 Contains information a/o0t :a6e405 5roced0res s0ch as :hen to :a6e 05

ad'ertisements or de5loyments that are con(g0red for Wa6e n L*N&

• WolCmgr&log 4 Contains information a/o0t :hich clients need to /e sent :a6e405 5ac6ets> then0m/er of :a6e405 5ac6ets sent> and the n0m/er of :a6e405 5ac6ets retried&

Soft:are 85dates Site Ser'er Log iles

• ciamgr&log 4 ,ro'ides information a/o0t the addition> deletion> and modi(cation of soft:are

05date con(g0ration items&

• distmgr&log 4 ,ro'ides information a/o0t the re5lication of soft:are 05date de5loyment

5ac6ages&

• o/re5lmgr&log 4 ,ro'ides information a/o0t the re5lication of soft:are 05dates noti(cation (les

from a 5arent to child sites&

• ,atchDo:nloader&log 4 ,ro'ides information a/o0t the 5rocess for do:nloading soft:are

05dates from the 05date so0rce s5eci(ed in the soft:are 05dates metadata to the do:nload

destination on the site ser'er&

• re5lmgr&log 4 ,ro'ides information a/o0t the 5rocess for re5licating (les /et:een sites&

• smsd/mon&log 4 ,ro'ides information a/o0t :hen soft:are 05date con(g0ration items are

inserted> 05dated> or deleted from the site ser'er data/ase and creates noti(cation (les for

soft:are 05dates com5onents&

• S8,Set05 4 ,ro'ides information a/o0t the soft:are 05date 5oint installation& When the

soft:are 05date 5oint installation com5letes> Installation :as s0ccessf0l is :ritten to this log

(le&

• WCM&log 4 ,ro'ides information a/o0t the soft:are 05date 5oint con(g0ration and connecting

to the Windo:s Ser'er 85date Ser'ices #WS8S ser'er for s0/scri/ed 05date categories>

classi(cations> and lang0ages&

• WS8SCtrl&log 4 ,ro'ides information a/o0t the con(g0ration> data/ase connecti'ity> and health

of the WS8S ser'er for the site&

• :syncmgr&log 4,ro'ides information a/o0t the soft:are 05dates synchroni?ation 5rocess&

WS8S Ser'er Log iles

• Change&log 4 ,ro'ides information a/o0t the WS8S ser'er data/ase information that has

changed&



• Soft:areDistri/0tion&log 4 ,ro'ides information a/o0t the soft:are 05dates that are

synchroni?ed from the con(g0red 05date so0rce to the WS8S ser'er data/ase&

Soft:are 85dates Client Com50ter Log iles

• C*S&log 4 ,ro'ides information a/o0t the 5rocess of do:nloading soft:are 05dates to the localcache and cache management&

• CI*gent&log 4 ,ro'ides information a/o0t 5rocessing con(g0ration items> incl0ding soft:are

05dates&

• LocationSer'ices&log 4 ,ro'ides information a/o0t the location of the WS8S ser'er :hen a scan

is initiated on the client&

• ,atchDo:nloader&log 4 ,ro'ides information a/o0t the 5rocess for do:nloading soft:are

05dates from the 05date so0rce to the do:nload destination on the site ser'er& This log is only

on the client com50ter con(g0red as the synchroni?ation host for the In'entory Tool forMicrosoft 85dates&

• ,olicy*gent&log 4 ,ro'ides information a/o0t the 5rocess for do:nloading> com5iling> and

deleting 5olicies on client com50ters&

• ,olicy;'al0ator 4 ,ro'ides information a/o0t the 5rocess for e'al0ating 5olicies on client

com50ters> incl0ding 5olicies from soft:are 05dates&

• Re/ootCoordinator&log 4 ,ro'ides information a/o0t the 5rocess for coordinating system

restarts on client com50ters after soft:are 05date installations&

• Scan*gent&log 4 ,ro'ides information a/o0t the scan re=0ests for soft:are 05dates> :hat tool

is re=0ested for the scan> the WS8S location> and so on&

• ScanWra55er 4 ,ro'ides information a/o0t the 5rere=0isite chec6s and the scan 5rocess

initiali?ation for the In'entory Tool for Microsoft 85dates on Systems Management Ser'er #SMS

2<<3 clients&

• Sdm*gent&log 4 ,ro'ides information a/o0t the 5rocess for 'erifying and decom5ressing

5ac6ages that contain con(g0ration item information for soft:are 05dates&

• Ser'iceWindo:Manager&log 4 ,ro'ides information a/o0t the 5rocess for e'al0ating con(g0red

maintenance :indo:s&

• smscli8I&log 4 ,ro'ides information a/o0t the Con(g0ration Manager Control ,anel 0ser

interactions> s0ch as initiating a Soft:are 85dates Scan Cycle from the Con(g0ration Manager

,ro5erties dialog /o$> o5ening the ,rogram Do:nload Monitor> and so on&



• SmsW0s-andler 4 ,ro'ides information a/o0t the scan 5rocess for the In'entory Tool for

Microsoft 85dates on SMS 2<<3 client com50ters&

• StateMessage&log 4 ,ro'ides information a/o0t :hen soft:are 05dates state messages are

created and sent to the management 5oint&

• 85datesDe5loyment&log 4 ,ro'ides information a/o0t the de5loyment on the client> incl0ding

soft:are 05date acti'ation> e'al0ation> and enforcement& 1er/ose logging sho:s additional

information a/o0t the interaction :ith the client 0ser interface&

• 85dates-andler&log 4 ,ro'ides information a/o0t soft:are 05date com5liance scanning and

a/o0t the do:nload and installation of soft:are 05dates on the client&

• 85datesStore&log 4 ,ro'ides information a/o0t the com5liance stat0s for the soft:are 05dates

that :ere assessed d0ring the com5liance scan cycle&

• W8*-andler&log 4 ,ro'ides information a/o0t :hen the Windo:s 85date *gent on the client

searches for soft:are 05dates&

• W8SSyncAML&log 4 ,ro'ides information a/o0t the In'entory Tool for the Microsoft 85dates

synchroni?ation 5rocess& This log is only on the client com50ter con(g0red as the

synchroni?ation host for the In'entory Tool for Microsoft 85dates&

Windo:s 85date *gent Log ile

• Windo:s85date&log 4 ,ro'ides information a/o0t :hen the Windo:s 85date *gent connects to

the WS8S ser'er and retrie'es the soft:are 05dates for com5liance assessment and :hether

there are 05dates to the agent com5onents&

What are the SCCM 2007 Site System roles

S&&M '88( supports the fo!!owing =< Site System ro!es, with those prefixed with N%W3*eing new to

S&&M:

• Site Server + he ser#er on which you insta!! the S&&M software-

• Site ata!ase Server + he ser#er running S7L and hosting the S&&M Site Data*ase Gon!y

re/uired for Primary Sites6

•

Con-iguration Manager Console + he interface for administering S&&M- Insta!!ed *ydefau!t on Primary Site Ser#ers this ro!e can a!so *e insta!!ed on wor$stations to a!!ow remote

administration-

• SMS Provider + he intermediate Windows Management Instrumentation GWMI6, !ayer that

sits *etween the &onfiguration Manager &onso!e and the Site Data*ase Gthe &onfiguration Manager

&onso!e accesses the Site Data*ase #ia the SMS Pro#ider6- +n!y re/uired for Primary Sites-

• Com"onent Server + A!! S&&M Site System ro!es Gexcept for the Distri*ution Point GDP66,

re/uires S&&M.specific software to *e insta!!ed in order for the Site System ro!e to function- When

such software is insta!!ed on a computer that computer *ecomes a &omponent Ser#er-

http://kallol-sccm.blogspot.com/2012/12/what-are-sccm-2007-site-system-roles.html

http://kallol-sccm.blogspot.com/2012/12/what-are-sccm-2007-site-system-roles.html



• istri!ution Point 4P5 + Stores S&&M Pac$ages from where &!ients can access them to

insta!! them- +n!y re/uired for the Software Distri*ution, Software 1pdates, and Ad#ertised as$

Se/uences functions of S&&M-

• N%W3 Fall!ac# Status Point + A catch a!!E Site System for &!ients that cannot *e insta!!ed

*ecause of #arious issues such as assignment, or their ina*i!ity to communicate with their

Management Point GMP6- ot re/uired *y defau!t, *ut recommended to he!p with &!ient insta!!ation

issues-

• Management Point 4MP5 + S&&M &!ients do not communicate direct!y with the S&&M Site

Ser#er and #ice #ersa- Instead a!! communication is faci!itated #ia the Management Point- A Defau!t

Management Point needs to *e defined in e#ery Site that has Intranet &!ients-

• N%W3 Pre+!oot %6ecution %nvironment 4P$%5 Service Point + he Site System that

responds to any computers re/uesting dep!oyment of their +perating System G+S6, #ia a PK re/uest-

+n!y re/uired if +perating System Dep!oyments G+SD6, are going to ta$e p!ace using PK *oot

re/uests-

• Re"orting Point 4RP5 + %osts the @eport iewer component that pro#ides the we*.*ased

reporting functiona!ity of S&&M- +n!y re/uired if @eports need to *e run on a particu!ar Primary Site-

• Server 1ocator Point 4S1P5 + @esponsi*!e for informing S&&M &!ients which MP they shou!d

access in order to insta!! the S&&M &!ient software- +n!y re/uired in some &!ient Dep!oyment

scenarios-

• N%W3 So-tware *"date Point 4S*P5 + Assigned to the computer running Windows Ser#er

1pdate Ser#ices GWS1S6- +n!y re/uired if the Software 1pdates feature is going to *e used-

• N%W3 State Migration Point 4SMP5 + Stores the user0s state migration data when a

computer0s +S is migrated- +n!y re/uired if the +SD feature is going to *e used-

• N%W3 System &ealth alidator Point 4S&P5 + his ro!e is assigned to the computer

running the etwor$ Po!icy Ser#ice- +n!y re/uired if the etwor$ Access Protection GAP6 feature is

going to *e used-

SCCM Logs an! "rou#leshooting

Theclient logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR

%\SysWOW64\CCM\Logs (for x64 OS).

TheSCCM 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 useTrace32.exe found in theSccm2007 Toolkit, to interpret the logs easily (errors in Red,

warnings in Yellow).

http://kallol-sccm.blogspot.com/2012/12/sccm-logs-and-troubleshooting.html

http://www.windows-noob.com/forums/index.php?showtopic=505

http://kallol-sccm.blogspot.com/2012/12/sccm-logs-and-troubleshooting.html

http://www.windows-noob.com/forums/index.php?showtopic=505



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 DeviceManagement 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 client’s 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 DomainServices, 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, thenumber 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.

So$tware %istri#ution "rou#leshooting &lowcharts

The follo:ing o:chart sho:s the 5rocess for Microsoft System Center Con(g0ration

Manager 2<<@ 5ac6age creation and distri/0tion&

http://kallol-sccm.blogspot.com/2012/12/software-distribution-troubleshooting.html

http://kallol-sccm.blogspot.com/2012/12/software-distribution-troubleshooting.html



SCCM trou#leshooting log 'les

Site Server logs8O

ciamgr(log) ,ro'ides information a/o0t the addition> deletion> and modi(cation of soft:are 05datecon(g0ration items&

!istmgr(log ) ,ro'ides information a/o0t the re5lication of soft:are 05date de5loyment 5ac6ages&

o#*re+lmgr(log ) ,ro'ides information a/o0t the re5lication of soft:are 05dates noti(cation (les from

a 5arent to child sites&

,atch%ownloa!er(log ) ,ro'ides information a/o0t the 5rocess for do:nloading soft:are 05dates

from the 05date so0rce s5eci(ed in the soft:are 05dates metadata to the do:nload destination on the

site ser'er&

re+lmgr(log ) ,ro'ides information a/o0t the 5rocess for re5licating (les /et:een sites&

sms!#mon(log ) ,ro'ides information a/o0t :hen soft:are 05date con(g0ration items are inserted>

05dated> or deleted from the site ser'er data/ase and creates noti(cation (les for soft:are 05dates

com5onents&

S-,Setu+ ) ,ro'ides information a/o0t the soft:are 05date 5oint installation& When the soft:are

05date 5oint installation com5letes> Installation :as s0ccessf0l is :ritten to this log (le&

WCM(log ) ,ro'ides information a/o0t the soft:are 05date 5oint con(g0ration and connecting to the

WS8S ser'er for s0/scri/ed 05date categories> classi(cations> and lang0ages&

WS-SCtrl(log ) ,ro'ides information a/o0t the con(g0ration> data/ase connecti'ity> and health of the

WS8S ser'er for the site&

wsyncmgr(log ) ,ro'ides information a/o0t the soft:are 05dates synchroni?ation 5rocess&

WS*S Server 1og FilesO

Change(log) ,ro'ides information a/o0t the WS8S ser'er data/ase information that has changed&

So$tware%istri#ution(log ) ,ro'ides information a/o0t the soft:are 05dates that are synchroni?ed

Client Com"uter 1og FilesO

C.S(log) ,ro'ides information a/o0t the 5rocess of do:nloading soft:are 05dates to the local cache

and cache management&

CI.gent(log),ro'ides information a/o0t 5rocessing con(g0ration items> incl0ding soft:are 05dates&

LocationServices(log) ,ro'ides information a/o0t the location of the WS8S ser'er :hen a scan is

initiated on the client&

,atch%ownloa!er(log),ro'ides information a/o0t the 5rocess for do:nloading soft:are 05dates from

http://kallol-sccm.blogspot.com/2012/12/sccm-troubleshooting-log-files.html

http://www.myitforum.com/myITWiki/SCCM%20troubleshooting%20Logs%20file.ashx#_Site_Server_logs:__0

http://www.myitforum.com/myITWiki/SCCM%20troubleshooting%20Logs%20file.ashx#_WSUS_Server_Log_Files__1

http://www.myitforum.com/myITWiki/SCCM%20troubleshooting%20Logs%20file.ashx#_Client_Computer_Log_Files__2

http://kallol-sccm.blogspot.com/2012/12/sccm-troubleshooting-log-files.html

http://www.myitforum.com/myITWiki/SCCM%20troubleshooting%20Logs%20file.ashx#_Site_Server_logs:__0

http://www.myitforum.com/myITWiki/SCCM%20troubleshooting%20Logs%20file.ashx#_WSUS_Server_Log_Files__1

http://www.myitforum.com/myITWiki/SCCM%20troubleshooting%20Logs%20file.ashx#_Client_Computer_Log_Files__2



the 05date so0rce to the do:nload destination on the site ser'er& This log is only on the client

com50ter con(g0red as the synchroni?ation host for the In'entory Tool for Microsoft 85dates&

,olicy.gent(log) ,ro'ides information a/o0t the 5rocess for do:nloading> com5iling> and deleting

5olicies on client com50ters&

,olicy/valuator),ro'ides information a/o0t the 5rocess for e'al0ating 5olicies on client com50ters>incl0ding 5olicies from soft:are 05dates&

e#ootCoor!inator(log),ro'ides information a/o0t the 5rocess for coordinating system restarts on

client com50ters after soft:are 05date installations&

Scan.gent(log) ,ro'ides information a/o0t the scan re=0ests for soft:are 05dates> :hat tool is

re=0ested for the scan> the WS8S location> and so on&

ScanWra++er(log),ro'ides information a/o0t the 5rere=0isite chec6s and the scan 5rocess

initiali?ation for the In'entory Tool for Microsoft 85dates on Systems Management Ser'er #SMS 2<<3

clients&

SCCM Interview Q & A

Documents

Transcript of SCCM Interview Q & A