Monthly Archives: September 2013

System Center Service Manager SP1 UR4

Microsoft just announced that UR4 will arrive in a couple of weeks. And it will have some bugfixes in the patch.

Here is the list

SCSM 2012:SP1: Regression- Simple lists do not function correctly in SSP after upgrading to SP1 UR 4
Review Activity add reviewer workflow fail to run in SCSM2012 sp1 running in windows Server 2012 UR 4
Subsequent activities start to run even though the current activity has not finished yet. UR 4
After SP1 upgrade, new “Service Dependents” entries created for “Business Services” cannot be seen in the console anymore UR 4
RunbookMonitorWorkflow cannot handle failed status of runbook UR 4
SCSM2012SP1:File attachments are not getting properly saved UR 4
Service Requests – incorrectly evaluated as completed UR 4
SCOM2012 the SQL broker conversations can lead to very large OperationsManager DB size and TempDB size UR 4
The status of SR becomes “completed” though it’s canceled manually UR 4



Protect a workgroup and not a domain server with DPM2012 SP1

DPM have the possibility to protect some workload from computers that are outside a domain. This is file/sql/hyper-v hosts for example. In order to do this you have to do some manual stuff with the DPM-agent before we can protect the workload.

Step 1 – Install the DPM-agent and configure it

Install the DPM-agent on the server you want to protect. You need to make sure that the server can resolved the netbios (hostname) that the DPM-server has. If it has the name make sure you can resolve it FQDN. After you verify that you can resolve and no firewall is blocking the traffic we can now configure the agent.

The -username flag will create a local account that DPM will use to do the backup. Notice that the flag -dpmservername is only the NETBIOS name and not the FQDN to the DPM-server.

Step 2 – Attach the DPM-klient to DPM-server

First before we can attach the client verify that you can reach the DPM-agent host by netbios name. If the computer has the netbios name client01 we have to be able to lookup the name client01 from the DPM-server. This MUST match if it does not match the process of attaching the client will fail. Go to management and agents. Select install agent and see the picture below.



After this is done you can now create your protection group as usual.

Remove orphaned connector from Service manager 2012 SP1

Some time ago i had a problem with an connector and i decided to remove it. But i was unable to remove the connector from the console. It just gave me an error. To fix this i had to use powershell to remove the connector.

Step 1 – Identify the connector

Step 2 – Remove the connector

As you can se abow i have identifed an Exchange connector that i want to remove. So now i can run following powershell command to remove the connector.


Using Orchestrator to send email to service owner in service manager 2012

There might be a few ways to get a notification to a service owner when an incident in the owners service has a high priority. I used System Center Orchestrator SP1 to achieve this.



In my case i have a Runbook that watches Incident with the flag new and a filter to priority eq 1, when a match is found i save it into a database and later parse that database and trigger the runbook abow. So lets not talk about the way i trigger the runbook. You can just replace Initialize Data with a monitor object instead.

Step 1

The first step we do after the monitor is fetch the incident that have a priority 1.

Step 2

We now need to map the incident relationship to services relationship.

Step 3

Mapping between user account and services.

Now we can fetch the service owner and proceed to send the email to the user.

This is one way to do it but it works fine, hope this might help someone some day.