70-243 · Question #95
You have a System Center 2012 Configuration Manager environment. When users attempt to install a program by using the Run Advertise program, they receive a message that the desired software is not…
The correct answer is A. Connect to the client computers, and view the LocationServices.log file. LocationServices.log on the client records content location requests and responses, making it the correct log to diagnose why a client reports software as unavailable.
Question
You have a System Center 2012 Configuration Manager environment. When users attempt to install a program by using the Run Advertise program, they receive a message that the desired software is not available. You need to view the status to find out why software is not available. What should you do?
Options
- AConnect to the client computers, and view the LocationServices.log file.
- BConnect to the client computers, and view the DataTransferService.log file.
- CConnect to the distribution point, and view the LocationServices.log file.
- DConnect to the distribution point, and view the PatchDownloader.log file.
How the community answered
(16 responses)- A81% (13)
- B6% (1)
- C13% (2)
Why each option
LocationServices.log on the client records content location requests and responses, making it the correct log to diagnose why a client reports software as unavailable.
LocationServices.log is a client-side log that records all attempts by the ConfigMgr client to discover content sources such as distribution points. When software is reported as unavailable, this log reveals whether the client received no valid content location or received an error response, pinpointing the root cause of the unavailability message.
DataTransferService.log records BITS transfer activity and is only relevant after a content location has already been found, not when the software cannot be located at all.
LocationServices.log is a client-side log and does not exist on distribution points, so connecting to the distribution point would yield no such file.
PatchDownloader.log is specific to software update content downloads and is unrelated to general software distribution package availability.
Concept tested: Client log troubleshooting for content location failures
Source: https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/log-files
Topics
Community Discussion
No community discussion yet for this question.