Here’s a new Knowledge Base article we published this morning. This one discusses an issue where you might find duplicate Activities in a SCSM Change or Incident Request.
Scenario 1: A new Change Request (CR) is created in System Center Service Manager. When you open the new Change Request, you see that there are duplicate Activities on the activities tab and the second of each activity will not have the prefix applied, only a number. Scenario 2: A new Incident Request (IR) is created from a template which has activities defined. When the new Incident Request is opened there are duplicate Activities on the activities tab and the second of each activity will not have the prefix applied, only a number.
When these requests are created, a template is selected to create the Request. When there are activities defined in the template, an instance of these activities are created at the time the request is created. Then the workflow runs, and because the option to apply a template is selected, another template is applied on top of the original template selected, which will then create the additional activities.
Both scenarios above are resolved in the same way. In the Service Manager console, Under Administration -> Workflows -> Configuration, highlight the Change Request/Incident Request event workflow Configuration and click Configure Workflow Rules in the task pane on the right. In the configure workflows screen, there will be any number of workflows which have been defined. Find and highlight the one that matches the criteria of the Change Request or Incident Request submitted in one of the scenarios above and click Edit. In the Configuration wizard for this workflow, there is a section called Apply Template which has a checkbox next to "Apply the Selected Template". Uncheck this box and click OK.
For the most current version of this article please see the following:
2703549 - Additional Activities are created when creating a Change Request or Incident Request in System Center Service Manager
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
This is useful, I wonder if this fix will resolve the issue I'm experiencing here: social.technet.microsoft.com/.../5d80098d-9b0e-4632-b757-1f6006f9b99f
I'll run through and feed back.