Your network contains a System Center 2012 Configuration Manager environment. You
need to use the Configuration Manager console to identify service level agreement (SLA)
issues among non-compliant clients.
What should you do?
A.
Configure an in-console alert.
B.
Create a ConfigMgr query.
C.
Create an alert subscription.
D.
Configure a Microsoft SQL Server Reporting Services (SSRS) report.
Explanation:
Configure an in-console alert.
http://myitforum.com/myitforumwp/2012/06/26/client-health-check-in-configmgr-
2012inactionpart-2/
Client
Health Check in ConfigMgr 2012–In Action–Part 2
Over here, we can clearly see that it failed to verify if the SMS Agent Host Service exists and
it failed with error code 5 (Access Denied). Other than this, we can also see that few other
evaluation tasks did not run because the tasks they were dependent on failed. Once this
evaluation was complete, I checked the ConfigMgr Console to see what all is shown over
there. So we go to ConfigMgr Console > Monitoring > Client Status > Client
Check. Over here we get graphical view which gives summary of Client Checks.So now, I can see that there is 1 machine which failed the Client Check. if we click on the
Red/Green Area of the graph, it takes us to a Temporary Monitoring Collection. I clicked on
the Red Area and it took me to a collection named “Clients that failed client check from “All
Desktop and Server Clients”So we can see that there is one machine which failed the Client Check. At the bottom on the
screen, I clicked on Client Check Detail TabSo now, I can see that “Verify SMS Agent Host service exists” task failed with the error
“Access is Denied” and this caused 3 other evaluation tasks to fail because they were
dependent on the first task. Pretty Nice Thing!! We can even configure alerts based on Client
Checks. For this, I opened the properties of the collection my client is a part of and went
Alerts Tab.I selected the option “Client check pass or no results for active clients falls below threshold
(%)”. After clicking OK it took me back to the Properties of the Collection.Now, we get an option to select the Severity of the Alert and SLA. I selected “Warning” as he
Severity and 90 as the SLA. So whenever the Client Check Fail Percentage falls below 90%,
I’ll get an alert in the console.
Now, if we go to Monitor > Alerts. We can see that an alert has been created.Further information:
http://technet.microsoft.com/en-us/library/hh427334.aspx
Configuring Alerts in Configuration Manager
Alerts in System Center 2012 Configuration Manager are generated by some operations
when a specific condition occurs. Typically, alerts are generated when an error occurs that
you must resolve. Additionally, an alert might be generated to warn you that a condition
exists so that you can continue to monitor the situation.
You can configure alerts for some Configuration Manager operations, such as Endpoint
Protection and client status, whereas some alerts are configured automatically.
Additionally, you can configure subscriptions to alerts for client status and Endpoint
Protection that will be emailed to you.
Personal comment:
“Create an alert subscription.” is not a correct answer because it only reffers to e-mailing alerts.