Which log files should you review?

Your network contains a System Center 2012 Configuration Manager environment.
In Default Client Agent Settings, you enable Hardware Inventory and Software Inventory.
You discover that a group of client computers fails to report software inventory data. The
client computers report hardware inventory data.
You confirm that Configuration Manager can deploy Applications to the group of client
computers.
You need to identify what is causing the reporting issue.
Which log files should you review? (Choose all that Apply.)

A.
Filesystemfile.log
See 11. below.
C: See 20. below.
D: see 4. below.
Note:
1. Client SideThe scheduler will send a message to the inventory agent to start the
software inventory process.
2. Scheduler.log:
Sending message for schedule ‘Machine/{00000000-0000-0000-0000-000000000002}’
(Target: ‘direct:InventoryAgent’, Name: ”)Scheduler4/10/2005 9:39:06 AM3904 (0x0F40)
The agent will determine the type of inventory it has to process (Full, Delta, Resync).The
Scan Properties are stored in WMI at the Root\CCM\Policy\Machine namespace.
1. If you don’t see this, the issue can be the client unable to download the policies or the
server has not been configured for Software Inventory.
2. Once the Software Inventory Client Agent has determined its Scan type, it must now
determine precisely what it needs to inventory. This is accomplished by again pulling
configuration data from WMI. WMI (Root\CCM\Policy\Machine) Each rule is stored in an
instance of this class.
3. The inventory agent will scan the machine according to the software inventory rules and
will send an XML file to the software inventory endpoint.
4. Inventoryagent.log
5. Inventory: Opening store for action {00000000-0000-0000-0000-000000000002}
…InventoryAgent4/22/2010 12:07:37 AM2924 (0x0B6C)
6. Inventory: Action=Software ReportType=DeltaInventoryAgent4/22/2010 12:07:56 AM2924
(0x0B6C)
7. Inventory: Initialization completed in 19.849 secondsInventoryAgent4/22/2010 12:07:56
AM2924 (0x0B6C)
8. Collection: Input context, scan rate in milliseconds = 2InventoryAgent4/22/2010 12:09:57
AM3972 (0x0F84)
9. Collection: Input context, skip file name = skpswi.datInventoryAgent4/22/2010 12:09:57
AM3972 (0x0F84)
10. Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT Name, Path,
LastWriteDate, Size, CompanyName, ProductName, ProductVersion, ProductLanguage,
FileVersion, FileDescription FROM FileSystemFile WHERE Name = ‘*.exe’ AND Path =
‘*\\*’ AND IsCompressed = FALSE AND IsEncrypted = FALSE; Timeout = 14400
secs.InventoryAgent4/22/2010 12:09:57 AM3972 (0x0F84)
11. FileSystemFile.log
12. ************* Start of File System Query. *************FileSystemFile4/22/2010 12:09:57
AM2384 (0x0950)
13. Query = SELECT __class, __path, __relpath, name, path, lastwritedate, size,
companyname, productname, productversion, productlanguage, fileversion,
filedescriptionFROM FileSystemFile WHERE name = ‘*.exe’ and path = ‘*\\*’ and
iscompressed = false and isencrypted = false; Timeout = 14400 secs; ScanInterval = 2
msecs; SkipFile = skpswi.datFileSystemFile4/22/2010 12:09:57 AM2384 (0x0950)
14. Query parsed successfully… ready to scan for files.FileSystemFile4/22/2010 12:09:57
AM2384 (0x0950)
15. Folders to skip: c:\system volume information.FileSystemFile4/22/2010 12:09:57
AM2384 (0x0950)
16. Scanning all local drives using input path *\FileSystemFile4/22/2010 12:09:57 AM2384
(0x0950)
17. Skipping A:\;GetDriveType indicates it is not a fixed drive pathFileSystemFile4/22/2010
12:09:57 AM2384 (0x0950)
Server Side
18. The Management Point receives the message from the Advanced Client via a
CCM_POST request. This allows the client to upload the message to the
C:\SMS_CCM\ServiceData\Messaging\EndpointQueues\MP_SinvEndpoint directory on the
Management Point.
19. Once there, CCMExec on the Management Point processes the message to recreate the
XML file. This file is then stored in the <SEREVERDIR>[1]\MP\Outboxes\Sinv.box folder.
Once the Management Point has properly received the message and converted it into an
XML file for processing, the XML file is then parsed and used to create a .SIC or .SID file( If
the inventory data in the XML file is a Delta)
20. Mp_sinv.log:
20..1. Mp Message Handler: copying attachment to C:\Program Files\Microsoft
Configuration
Manager\inboxes\auth\sinv.box\SinvAttachment8920FQG5.xmlMP_SinvEndpoint1/31/2010
9:49:55 AM3548 (0x0DDC)
20..2. Inv-Sinv Task: processing xml file “C:\Program Files\Microsoft Configuration
Manager\inboxes\auth\sinv.box\SinvAttachment8920FQG5.xml”MP_SinvEndpoint1/31/201
0 9:49:55 AM3280 (0x0CD0)
20..3. Sinv Sax: loading C:\Program Files\Microsoft Configuration
Manager\inboxes\auth\sinv.box\SinvAttachment8920FQG5.xmlMP_SinvEndpoint1/31/2010
9:49:55 AM3280 (0x0CD0)
20..4. Full report from client SQL, action description = SoftwareMP_SinvEndpoint1/31/2010
9:49:55 AM3280 (0x0CD0)
20..5. Sinv Task: Translate report attachment to file “C:\Program Files\Microsoft
Configuration Manager\inboxes\auth\sinv.box\9GY0JSG8.SIC” returned
0MP_SinvEndpoint1/31/2010 9:49:55 AM3280 (0x0CD0)
20..6. Mp Message Handler: copying attachment to C:\Program Files\Microsoft
Configuration
Manager\inboxes\auth\sinv.box\SinvAttachment4L7OW9WF.xmlMP_SinvEndpoint2/19/2010
7:37:16 PM5980 (0x175C)
20..7. Inv-Sinv Task: processing xml file “C:\Program Files\Microsoft Configuration
Manager\inboxes\auth\sinv.box\SinvAttachment4L7OW9WF.xml”
MP_SinvEndpoint2/19/2010 7:37:16 PM272 (0x0110)
20..8. Sinv Sax: loading C:\Program Files\Microsoft Configuration
Manager\inboxes\auth\sinv.box\SinvAttachment4L7OW9WF.xmlMP_SinvEndpoint2/19/2010
7:37:16 PM272 (0x0110)
21. The management point file dispatch manager copies the file to the site server. There the
software inventory processor inserts the data into the database.
22. Sinvproc.log:
22..1. Process Inventory Files…SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010
9:27:13 AM5208 (0x1458)
22..2. Processing file: C:\Program Files\Microsoft Configuration
Manager\inboxes\auth\sinv.box\W06N50OM.SICSMS_SOFTWARE_INVENTORY_PROC
ESSOR1/31/2010 9:27:13 AM4668 (0x123C)
22..3. Processing Inventory for Machine: SCCMResId: 3 [OpCode=17 Sinv=1 FC=0
Resync=1] Generated: 01/31/2010
09:27:02SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:37 AM4668
(0x123C)
22..4. Transactions: Exist=0, Add=1196, Upd=0, Del=0,
Total=1196SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:37 AM4668
(0x123C)
22..5. Report for Machine SCCM took 27 secs. for 2290 recs, FP=109, P=985, F=1196,
FC=0SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:40 AM4668 (0x123C)
22..6. Successfully Processed file C:\Program Files\Microsoft Configuration
Manager\inboxes\auth\sinv.box\W06N50OM.SIC
!!!SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:40 AM4668 (0x123C)
23. If the files are not getting processed then we need to make sure that the component
SMS_SOFTWARE_INVENTORY_PROCESSOR. In certain circumstances a site reset can
also fix
QUESTION 21
Your network contains a System Center 2012 Configuration Manager environment.
The network contains 10 database servers that run Microsoft SQL Server 2008.
You have a configuration baseline that is used to monitor the database servers.
You add new configuration items to the configuration baseline.
Two days later, you discover that only eight of the database servers report any information
about the new configuration items.
You need to identify whether the new configuration items downloaded to the database
servers.
Which log file should you review?
Hman.log

B.
Dataldr.log
Sitestat.log

C.
Mp_sinv.log
Dcmagent.log

D.
Inventoryagent.log
Wsyncmgr.log

E.
Hman.log
Ccm.log

A.
Filesystemfile.log
See 11. below.
C: See 20. below.
D: see 4. below.
Note:
1. Client SideThe scheduler will send a message to the inventory agent to start the
software inventory process.
2. Scheduler.log:
Sending message for schedule ‘Machine/{00000000-0000-0000-0000-000000000002}’
(Target: ‘direct:InventoryAgent’, Name: ”)Scheduler4/10/2005 9:39:06 AM3904 (0x0F40)
The agent will determine the type of inventory it has to process (Full, Delta, Resync).The
Scan Properties are stored in WMI at the Root\\CCM\\Policy\\Machine namespace.
1. If you don’t see this, the issue can be the client unable to download the policies or the
server has not been configured for Software Inventory.
2. Once the Software Inventory Client Agent has determined its Scan type, it must now
determine precisely what it needs to inventory. This is accomplished by again pulling
configuration data from WMI. WMI (Root\\CCM\\Policy\\Machine) Each rule is stored in an
instance of this class.
3. The inventory agent will scan the machine according to the software inventory rules and
will send an XML file to the software inventory endpoint.
4. Inventoryagent.log
5. Inventory: Opening store for action {00000000-0000-0000-0000-000000000002}
…InventoryAgent4/22/2010 12:07:37 AM2924 (0x0B6C)
6. Inventory: Action=Software ReportType=DeltaInventoryAgent4/22/2010 12:07:56 AM2924
(0x0B6C)
7. Inventory: Initialization completed in 19.849 secondsInventoryAgent4/22/2010 12:07:56
AM2924 (0x0B6C)
8. Collection: Input context, scan rate in milliseconds = 2InventoryAgent4/22/2010 12:09:57
AM3972 (0x0F84)
9. Collection: Input context, skip file name = skpswi.datInventoryAgent4/22/2010 12:09:57
AM3972 (0x0F84)
10. Collection: Namespace = \\\\.\\root\\ccm\\invagt; Query = SELECT Name, Path,
LastWriteDate, Size, CompanyName, ProductName, ProductVersion, ProductLanguage,
FileVersion, FileDescription FROM FileSystemFile WHERE Name = ‘*.exe’ AND Path =
‘*\\\\*’ AND IsCompressed = FALSE AND IsEncrypted = FALSE; Timeout = 14400
secs.InventoryAgent4/22/2010 12:09:57 AM3972 (0x0F84)
11. FileSystemFile.log
12. ************* Start of File System Query. *************FileSystemFile4/22/2010 12:09:57
AM2384 (0x0950)
13. Query = SELECT __class, __path, __relpath, name, path, lastwritedate, size,
companyname, productname, productversion, productlanguage, fileversion,
filedescriptionFROM FileSystemFile WHERE name = ‘*.exe’ and path = ‘*\\\\*’ and
iscompressed = false and isencrypted = false; Timeout = 14400 secs; ScanInterval = 2
msecs; SkipFile = skpswi.datFileSystemFile4/22/2010 12:09:57 AM2384 (0x0950)
14. Query parsed successfully… ready to scan for files.FileSystemFile4/22/2010 12:09:57
AM2384 (0x0950)
15. Folders to skip: c:\\system volume information.FileSystemFile4/22/2010 12:09:57
AM2384 (0x0950)
16. Scanning all local drives using input path *\\FileSystemFile4/22/2010 12:09:57 AM2384
(0x0950)
17. Skipping A:\\;GetDriveType indicates it is not a fixed drive pathFileSystemFile4/22/2010
12:09:57 AM2384 (0x0950)
Server Side
18. The Management Point receives the message from the Advanced Client via a
CCM_POST request. This allows the client to upload the message to the
C:\\SMS_CCM\\ServiceData\\Messaging\\EndpointQueues\\MP_SinvEndpoint directory on the
Management Point.
19. Once there, CCMExec on the Management Point processes the message to recreate the
XML file. This file is then stored in the <SEREVERDIR>[1]\\MP\\Outboxes\\Sinv.box folder.
Once the Management Point has properly received the message and converted it into an
XML file for processing, the XML file is then parsed and used to create a .SIC or .SID file( If
the inventory data in the XML file is a Delta)
20. Mp_sinv.log:
20..1. Mp Message Handler: copying attachment to C:\\Program Files\\Microsoft
Configuration
Manager\\inboxes\\auth\\sinv.box\\SinvAttachment8920FQG5.xmlMP_SinvEndpoint1/31/2010
9:49:55 AM3548 (0x0DDC)
20..2. Inv-Sinv Task: processing xml file “C:\\Program Files\\Microsoft Configuration
Manager\\inboxes\\auth\\sinv.box\\SinvAttachment8920FQG5.xml”MP_SinvEndpoint1/31/201
0 9:49:55 AM3280 (0x0CD0)
20..3. Sinv Sax: loading C:\\Program Files\\Microsoft Configuration
Manager\\inboxes\\auth\\sinv.box\\SinvAttachment8920FQG5.xmlMP_SinvEndpoint1/31/2010
9:49:55 AM3280 (0x0CD0)
20..4. Full report from client SQL, action description = SoftwareMP_SinvEndpoint1/31/2010
9:49:55 AM3280 (0x0CD0)
20..5. Sinv Task: Translate report attachment to file “C:\\Program Files\\Microsoft
Configuration Manager\\inboxes\\auth\\sinv.box\\9GY0JSG8.SIC” returned
0MP_SinvEndpoint1/31/2010 9:49:55 AM3280 (0x0CD0)
20..6. Mp Message Handler: copying attachment to C:\\Program Files\\Microsoft
Configuration
Manager\\inboxes\\auth\\sinv.box\\SinvAttachment4L7OW9WF.xmlMP_SinvEndpoint2/19/2010
7:37:16 PM5980 (0x175C)
20..7. Inv-Sinv Task: processing xml file “C:\\Program Files\\Microsoft Configuration
Manager\\inboxes\\auth\\sinv.box\\SinvAttachment4L7OW9WF.xml”
MP_SinvEndpoint2/19/2010 7:37:16 PM272 (0x0110)
20..8. Sinv Sax: loading C:\\Program Files\\Microsoft Configuration
Manager\\inboxes\\auth\\sinv.box\\SinvAttachment4L7OW9WF.xmlMP_SinvEndpoint2/19/2010
7:37:16 PM272 (0x0110)
21. The management point file dispatch manager copies the file to the site server. There the
software inventory processor inserts the data into the database.
22. Sinvproc.log:
22..1. Process Inventory Files…SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010
9:27:13 AM5208 (0x1458)
22..2. Processing file: C:\\Program Files\\Microsoft Configuration
Manager\\inboxes\\auth\\sinv.box\\W06N50OM.SICSMS_SOFTWARE_INVENTORY_PROC
ESSOR1/31/2010 9:27:13 AM4668 (0x123C)
22..3. Processing Inventory for Machine: SCCMResId: 3 [OpCode=17 Sinv=1 FC=0
Resync=1] Generated: 01/31/2010
09:27:02SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:37 AM4668
(0x123C)
22..4. Transactions: Exist=0, Add=1196, Upd=0, Del=0,
Total=1196SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:37 AM4668
(0x123C)
22..5. Report for Machine SCCM took 27 secs. for 2290 recs, FP=109, P=985, F=1196,
FC=0SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:40 AM4668 (0x123C)
22..6. Successfully Processed file C:\\Program Files\\Microsoft Configuration
Manager\\inboxes\\auth\\sinv.box\\W06N50OM.SIC
!!!SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:40 AM4668 (0x123C)
23. If the files are not getting processed then we need to make sure that the component
SMS_SOFTWARE_INVENTORY_PROCESSOR. In certain circumstances a site reset can
also fix
QUESTION 21
Your network contains a System Center 2012 Configuration Manager environment.
The network contains 10 database servers that run Microsoft SQL Server 2008.
You have a configuration baseline that is used to monitor the database servers.
You add new configuration items to the configuration baseline.
Two days later, you discover that only eight of the database servers report any information
about the new configuration items.
You need to identify whether the new configuration items downloaded to the database
servers.
Which log file should you review?
Hman.log

A.
Filesystemfile.log
See 11. below.
C: See 20. below.
D: see 4. below.
Note:
1. Client SideThe scheduler will send a message to the inventory agent to start the
software inventory process.
2. Scheduler.log:
Sending message for schedule ‘Machine/{00000000-0000-0000-0000-000000000002}’
(Target: ‘direct:InventoryAgent’, Name: ”)Scheduler4/10/2005 9:39:06 AM3904 (0x0F40)
The agent will determine the type of inventory it has to process (Full, Delta, Resync).The
Scan Properties are stored in WMI at the Root\\\\CCM\\\\Policy\\\\Machine namespace.
1. If you don’t see this, the issue can be the client unable to download the policies or the
server has not been configured for Software Inventory.
2. Once the Software Inventory Client Agent has determined its Scan type, it must now
determine precisely what it needs to inventory. This is accomplished by again pulling
configuration data from WMI. WMI (Root\\\\CCM\\\\Policy\\\\Machine) Each rule is stored in an
instance of this class.
3. The inventory agent will scan the machine according to the software inventory rules and
will send an XML file to the software inventory endpoint.
4. Inventoryagent.log
5. Inventory: Opening store for action {00000000-0000-0000-0000-000000000002}
…InventoryAgent4/22/2010 12:07:37 AM2924 (0x0B6C)
6. Inventory: Action=Software ReportType=DeltaInventoryAgent4/22/2010 12:07:56 AM2924
(0x0B6C)
7. Inventory: Initialization completed in 19.849 secondsInventoryAgent4/22/2010 12:07:56
AM2924 (0x0B6C)
8. Collection: Input context, scan rate in milliseconds = 2InventoryAgent4/22/2010 12:09:57
AM3972 (0x0F84)
9. Collection: Input context, skip file name = skpswi.datInventoryAgent4/22/2010 12:09:57
AM3972 (0x0F84)
10. Collection: Namespace = \\\\\\\\.\\\\root\\\\ccm\\\\invagt; Query = SELECT Name, Path,
LastWriteDate, Size, CompanyName, ProductName, ProductVersion, ProductLanguage,
FileVersion, FileDescription FROM FileSystemFile WHERE Name = ‘*.exe’ AND Path =
‘*\\\\\\\\*’ AND IsCompressed = FALSE AND IsEncrypted = FALSE; Timeout = 14400
secs.InventoryAgent4/22/2010 12:09:57 AM3972 (0x0F84)
11. FileSystemFile.log
12. ************* Start of File System Query. *************FileSystemFile4/22/2010 12:09:57
AM2384 (0x0950)
13. Query = SELECT __class, __path, __relpath, name, path, lastwritedate, size,
companyname, productname, productversion, productlanguage, fileversion,
filedescriptionFROM FileSystemFile WHERE name = ‘*.exe’ and path = ‘*\\\\\\\\*’ and
iscompressed = false and isencrypted = false; Timeout = 14400 secs; ScanInterval = 2
msecs; SkipFile = skpswi.datFileSystemFile4/22/2010 12:09:57 AM2384 (0x0950)
14. Query parsed successfully… ready to scan for files.FileSystemFile4/22/2010 12:09:57
AM2384 (0x0950)
15. Folders to skip: c:\\\\system volume information.FileSystemFile4/22/2010 12:09:57
AM2384 (0x0950)
16. Scanning all local drives using input path *\\\\FileSystemFile4/22/2010 12:09:57 AM2384
(0x0950)
17. Skipping A:\\\\;GetDriveType indicates it is not a fixed drive pathFileSystemFile4/22/2010
12:09:57 AM2384 (0x0950)
Server Side
18. The Management Point receives the message from the Advanced Client via a
CCM_POST request. This allows the client to upload the message to the
C:\\\\SMS_CCM\\\\ServiceData\\\\Messaging\\\\EndpointQueues\\\\MP_SinvEndpoint directory on the
Management Point.
19. Once there, CCMExec on the Management Point processes the message to recreate the
XML file. This file is then stored in the <SEREVERDIR>[1]\\\\MP\\\\Outboxes\\\\Sinv.box folder.
Once the Management Point has properly received the message and converted it into an
XML file for processing, the XML file is then parsed and used to create a .SIC or .SID file( If
the inventory data in the XML file is a Delta)
20. Mp_sinv.log:
20..1. Mp Message Handler: copying attachment to C:\\\\Program Files\\\\Microsoft
Configuration
Manager\\\\inboxes\\\\auth\\\\sinv.box\\\\SinvAttachment8920FQG5.xmlMP_SinvEndpoint1/31/2010
9:49:55 AM3548 (0x0DDC)
20..2. Inv-Sinv Task: processing xml file “C:\\\\Program Files\\\\Microsoft Configuration
Manager\\\\inboxes\\\\auth\\\\sinv.box\\\\SinvAttachment8920FQG5.xml”MP_SinvEndpoint1/31/201
0 9:49:55 AM3280 (0x0CD0)
20..3. Sinv Sax: loading C:\\\\Program Files\\\\Microsoft Configuration
Manager\\\\inboxes\\\\auth\\\\sinv.box\\\\SinvAttachment8920FQG5.xmlMP_SinvEndpoint1/31/2010
9:49:55 AM3280 (0x0CD0)
20..4. Full report from client SQL, action description = SoftwareMP_SinvEndpoint1/31/2010
9:49:55 AM3280 (0x0CD0)
20..5. Sinv Task: Translate report attachment to file “C:\\\\Program Files\\\\Microsoft
Configuration Manager\\\\inboxes\\\\auth\\\\sinv.box\\\\9GY0JSG8.SIC” returned
0MP_SinvEndpoint1/31/2010 9:49:55 AM3280 (0x0CD0)
20..6. Mp Message Handler: copying attachment to C:\\\\Program Files\\\\Microsoft
Configuration
Manager\\\\inboxes\\\\auth\\\\sinv.box\\\\SinvAttachment4L7OW9WF.xmlMP_SinvEndpoint2/19/2010
7:37:16 PM5980 (0x175C)
20..7. Inv-Sinv Task: processing xml file “C:\\\\Program Files\\\\Microsoft Configuration
Manager\\\\inboxes\\\\auth\\\\sinv.box\\\\SinvAttachment4L7OW9WF.xml”
MP_SinvEndpoint2/19/2010 7:37:16 PM272 (0x0110)
20..8. Sinv Sax: loading C:\\\\Program Files\\\\Microsoft Configuration
Manager\\\\inboxes\\\\auth\\\\sinv.box\\\\SinvAttachment4L7OW9WF.xmlMP_SinvEndpoint2/19/2010
7:37:16 PM272 (0x0110)
21. The management point file dispatch manager copies the file to the site server. There the
software inventory processor inserts the data into the database.
22. Sinvproc.log:
22..1. Process Inventory Files…SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010
9:27:13 AM5208 (0x1458)
22..2. Processing file: C:\\\\Program Files\\\\Microsoft Configuration
Manager\\\\inboxes\\\\auth\\\\sinv.box\\\\W06N50OM.SICSMS_SOFTWARE_INVENTORY_PROC
ESSOR1/31/2010 9:27:13 AM4668 (0x123C)
22..3. Processing Inventory for Machine: SCCMResId: 3 [OpCode=17 Sinv=1 FC=0
Resync=1] Generated: 01/31/2010
09:27:02SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:37 AM4668
(0x123C)
22..4. Transactions: Exist=0, Add=1196, Upd=0, Del=0,
Total=1196SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:37 AM4668
(0x123C)
22..5. Report for Machine SCCM took 27 secs. for 2290 recs, FP=109, P=985, F=1196,
FC=0SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:40 AM4668 (0x123C)
22..6. Successfully Processed file C:\\\\Program Files\\\\Microsoft Configuration
Manager\\\\inboxes\\\\auth\\\\sinv.box\\\\W06N50OM.SIC
!!!SMS_SOFTWARE_INVENTORY_PROCESSOR1/31/2010 9:27:40 AM4668 (0x123C)
23. If the files are not getting processed then we need to make sure that the component
SMS_SOFTWARE_INVENTORY_PROCESSOR. In certain circumstances a site reset can
also fix
QUESTION 21
Your network contains a System Center 2012 Configuration Manager environment.
The network contains 10 database servers that run Microsoft SQL Server 2008.
You have a configuration baseline that is used to monitor the database servers.
You add new configuration items to the configuration baseline.
Two days later, you discover that only eight of the database servers report any information
about the new configuration items.
You need to identify whether the new configuration items downloaded to the database
servers.
Which log file should you review?
Hman.log

B.
Dataldr.log
Sitestat.log

C.
Mp_sinv.log
Dcmagent.log

D.
Inventoryagent.log
Wsyncmgr.log

E.
Hman.log
Ccm.log

F.
Contenttransfermanager.log

G.
Sdmagent.log

H.
Rcmctri.log

I.
Ciagent.log

J.
Smsexec.log
K.
Locationservices.log

Explanation:
Ciagent.log
Not related to US foreign security policy but provides information about processing
configuration items, including software updates.
Incorrect:
Not B: Sitestat.log: Records the monitoring process of all site systems.