You are browsing the archive for Orchestrator.

Avatar of alkin

by alkin

part 2: Getting facebook status updates when something happens to my servers.

7:46 am in Azure, Powershell, SytemCenter by alkin

In my previous blogpost I explained how to install the powershell Facebook Module.

Today I’m going to show you how you can get Facebook status updates when something happens to your server. To simulate this I will create a new runbook that will shut down all the virtual machines in a certain cloud in Azure and then post a facebook status update with the name of the servers that have been shut downed.

To be able to do this I created the following Orchestrator runbook:


This workflow will get a list of the Cloud services running in Azure and then stop all the Virtual Machines in that Cloud. After that a status update will be posted on facebook saying which server has been turned off.

The first activity is the get Azure cloud service properties to retrieve cloud service properties


We can then use the output of the cloud service activity in the Virtual machine activity to stop all the VM’s in the discovered cloud.


The last activity is a .Net activity that will import the facebook module and post a new status update on facebook with the new-FBfeed command


The result will be something like this



Alexandre Verinderen

Avatar of alkin

by alkin

Cloud Service pack failed: Current user is not a valid Orchestrator user

9:46 am in SytemCenter by alkin

Microsoft released beginning of March the updated Cloud Service Process pack that is now fully compatible with System Center 2012 SP1. You can download the new process pack here:   CSPP is an extension pack built on top of System Center. This release is compatible only with System Center 2012 and 2012 SP1. This release does not contain a new feature set from prior releases.

When I tried to install CSPP I got the following error:


I opened the log files of the CSSP setup that are located at the following location:


When I search through the log file I discovered the following error:


03:12:25:Checking if current user is valid Orchestrator user or not
03:12:27:System.Runtime.InteropServices.COMException (0x800708AC): The group name could not be found.

My account is a local admin and I could perfectly connect to Orchestator and create and launch runbooks so I was quite suprised to see this error.

So I looked locally in computer managed and you need two groups: the first one is the OrchestratorSystemGroup and the second one is the OrchestratorUserGroup which apparently didn’t exist on my orchestrator server! This means the Orchestator pre-requisites checker is checking for a group which doesn’t exist locally!


So I created manually a new group and added my account to the group



After that I closed and re-opened the setup wizard and everything went through without any issues!

Hope this helps,


Visit Us On TwitterVisit Us On Linkedin