Managing Incidents Overview

 

Updated: May 13, 2016

Applies To: System Center 2012 SP1 - Service Manager, System Center 2012 R2 Service Manager, System Center 2012 - Service Manager

In System Center 2012 – Service Manager, help desk analysts use incident management to restore regular operations as quickly and as cost-effectively as possible.

Using the E-mail Incident template to populate a new email-related incident, you can quickly create an incident and ensure that the correct Impact, Urgency, Assigned Analyst, and Support Tier fields are configured.

If you configure connectors so that Service Manager imports configuration items and alerts from Operations Manager, some new incidents are automatically created. An analyst reviews the automatically created incidents for accuracy.

In Service Manager, incidents are automatically created from email requests by users. If the user is recognized as a Service Manager end user, the request that is sent to the help desk email address automatically creates a new incident.

Note


Service Manager can automatically generate new incidents from email requests only after a Service Manager administrator enables inbound email processing. By default, the impact and urgency of every incident created by email submission is set to medium, and no category is assigned.

Normally, you create incidents only for user accounts in your organization that have Active Directory Domain Services (AD DS) accounts that are synchronized with Service Manager. However, you might occasionally need to manually create incidents for users. For example, you might need to create an incident for a new user whose account is not yet in AD DS or if an Active Directory account is not yet synchronized with Service Manager. You can also manually create incidents to support external vendors who do not have Active Directory accounts. In another example, you might need to open an incident for an on-site technician who does not have an Active Directory account but who needs to report an incident. Or, you might need to open an incident for an externally-supported customer who does not have an Active Directory account. In all these examples, you must manually create a user in Service Manager. For more information, see “How to Add a Member to a User Role” in the Administrator's Guide for System Center 2012 - Service Manager in the topic.

Depending on the needs of your organization, you might want to have a clear distinction between an incident’s Assigned To user and the primary owner. Within Service Manager, neither use has any implied value. For example, although you can choose both of these two users in an incident form, you might want customers to deal with a single person who is your customer focal point. In this case, that person might be the primary owner who also owns other incidents. An Assigned To user might be one of many analysts who might work on an incident temporarily before the incident is assigned to another analyst before it is ultimately resolved and closed.

IDs that are assigned to change requests and incidents are not created in sequence. However, newer change requests and incidents are assigned IDs with a higher number than the IDs created previously.

See Also

Managing Incidents