From Orchestrator to Service Management Automation: Migration Scenarios

Service Management Automation (SMA) is the next gen IT Automation tool. SMA has some certain advantage over Orchestrator but also some limitations and vise versa. Nevertheless I am taking in consideration that you are aware of these advantages and limitations and you’ve decided to move fully or partially from SCO to SMA. Continue reading “From Orchestrator to Service Management Automation: Migration Scenarios”

Installing System Center Service Management Automation Worker Role Fails with MSI Error 1603

I was deploying SMA recently and bumped in into the following error while installing the Worker Role: Continue reading “Installing System Center Service Management Automation Worker Role Fails with MSI Error 1603”

Important Links for the R2 Wave

Remote Tools:

Release notes for System Center 2012 R2:

WAP:

What is new in System Center 2012 R2:

System Center 2012 R2 Documents Download:

How to Upgrade:

System Center 2012 R2 Evaluation VHDs:

Windows Server 2012 R2 Updates:

Automatic Deployment of System Center 2012 R2:

Management Packs:

System Center 2012 R2 addons:

Development:

Visio Stencils:

Microsoft Deployment Toolkit (MDT) 2013

Windows Server 2012 R2 and Windows Server 2012 TechNet Library Documentation

Windows Server 2012 R2 Test Lab Guide

Linux Integration Services Version 3.5 for Hyper-V – NEW

More links to come

Orchestrator Web Service Does Not Work After Adding The Server to Infrastructure Servers in VMM 2012 R2

I have a couple of Orchestrator servers with Web Features role installed on them. I’ve recently added those servers as Infrastructure Servers in VMM 2012 R2 in order to update them from there. After adding them the Orchestrator Web Service on those server stopped working. Continue reading “Orchestrator Web Service Does Not Work After Adding The Server to Infrastructure Servers in VMM 2012 R2”

Quick Look at System Center Service Provider Foundation Management Pack

Last week the SPF MP for SCOM was released so let’s look on how to install it and configure it.

First we need to install it:

image

image

image

image

image

Then we need to import in SCOM

image

image

After it is imported we need to create account/s. According to the guide you need to create two accounts in SCOM:

  • One account that have access to the SPF database and with access to your VMM;
  • Second account with access to the VMM endpoint in SPF.

As I see it you need only read access for both accounts but in my case I will use one account that have admin rights in SPF database, admin rights in VMM and member of the group that gives permissions to the VMM endpoint.

image

image

Set it to more secure

image

Next open the properties of the account in the Distribution tab add all your SPF server(s), VMM server(s) and SQL server(s) where SPF database is:

image

In the SCOM console in Profiles section you will see two profiles:

  • Service Provider Foundation Database Account
  • Service Provider Foundation VMM Web Endpoint Account

image

To both accounts you need to add the account you’ve just added in SCOM. Of course if you want to go more secure and have two accounts you will add them to the corresponding profile. Also remember to distribute the accounts to the right servers. In my case I am adding to both profiles the same account:

image

image

After that in your Service Provider Foundation State view you should see your SPF servers:

image

If you have any alerts for wrong credentials you can reset the monitors and close the alerts. During the import, the creation of the accounts and setting them some alerts might be generated for wrong credentials.

image