System Center SCSM und SCO Session from CDCGermany

Hi, as you may noticed, i  have been at CDC Germany in Hanau a few weeks ago, talking about Service Management and Automation.

The Session has been recorded an is available now (German)

If the Preview is not working, you can click on that URL: https://vimeo.com/341831252/ff1f56351e

Upcoming Speaker Engagements, Meetups or other Appointments

Hi, some exciting weeks and month are coming up, some Speaker Engagements, Meetups or Sponsor Slots are around. So if you like to meet, feel free to visit and talk to me.

Speaker

System Center User Group Munich – 17. April 2019 – Microsoft München – Phönix aus der Asche – Service Management und Automatisierung mit System Center

Signup: https://www.meetup.com/System-Center-Usergroup-Munich-SCUGDE/events/258897775/


CDC-Germany – 21, 22. May 2019 – Congress Park Hanau – Service Management und Automatisierung mit System Center aus der Praxis

Tickets: https://www.cdc-germany.de/#tickets

Sponsor

Experts Live Norway – 29. May 2019 – Felix Conference Center, Oslo – Silver Sponsor with au2mator Self Service Portal

Tickets: https://expertslive.no/tickets/


Experts Live Switzerland – 20. June 2019 – Welle 7, Bern – Silver Sponsor with au2mator Self Service Portal

Tickets: https://www.expertslive.ch/anmeldung


Looking forward to see and meet a lot of People.

Michael Seidl aka Techguy

Upgrade to System Center Orchestrator 2019

Since a few days, System Center 2019 is GA, so lets upgrade our environment to the latest bits. I will start with System Center 2019 Orchestrator.

Very important note here, System C

So lets start with a quick overview on what’s new.

What’s new with SCO 2019

  • Support for PowerShell 4.0+
  • Support for SQL 2017
  • Support for TLS 1.2
  • Enhancement on SSH
  • SM/SCOM Integration Enhancements.
  • Support for PowerShell 4+
  • SCO will be a 64bit Application (will come with UR 1 for 2019)

Prepare the Upgrade

You can upgrade to System Center Orchestrator 2019 from the following Version

  • Orchestrator 2016 UR6
  • Orchestrator 1801
  • Orchestrator 1807

Make sure to backup the Orchestrator DB, you never know.

Make a note of all you Integration Packs.

Upgrade

  • Stop all Runbook
  • Now, uninstall all Orchestrator components on all Server
    • Important, keep the Database, if asked
  • Run the 2019 Setup Files
  • Enter all the Information’s

After some minutes, Orchestrator 2019 is installed

image

Michael Seidl aka Techguy

System Center Service Manager–SQL Query to get a full List of your Incidents

In the most cases, the Reporting has to be done through the Data warehouse DB for SCSM, but in some cases you have to get all the Data from the ServiceManager DB. For Example if you don’t have a Data warehouse DB for SCSM or you need some more Details.

In this Case you have to query the Service Manager DB, and unfortunately, this DB is not as simple as the Data warehouse DB. So to get a complete list of your Incidents, including all your Status, Classifications, Affected Users, Assigned Users and everything else, it will cost some time to build this Query.

Also to get the correct Values for Status, Classification and so on, you have to make some joins, but see yourself.

Take this Query as a basis and changed it to fit your needs. Below is a Link to Download

(Read more…)

System Center Orchestrator–SQL Query detailed Logs and behind the Scene

In some cases it can happen that the Log Purge is not working anymore, or not working correctly. In a real bad situation it can happen, that the daily Log Purge will make more troubles, maybe stops your Runbooks from working.

Than you will see a lot of orphaned Runbooks, and in the most cases this can happen when the extended Logging is activated at to many Runbooks. I always see customer, which are using the extended Logging at each Runbook and for ever.

Extended Logging should be used with care and only for testing and Dev Phase, not in production and not persistent.

Get Runbooks with active extended Logging

To get a List of Runbook with active, extended logging, run he following Query.

use Orchestrator 

select Name, LastModified, Enabled  from POLICIES where LogSpecificData = 1 or LogCommonData = 1


(Read more…)

Check and remove orphaned Runbooks

To keep System Center Orchestrator up and running, and of course healthy, you need to take care of orphaned Runbooks. Sometime, or maybe more often, Orchestrator produces orphaned Runbooks. As you maybe know, Orchestrator acts very special with his Database, so always make sure the Database is attached as best as possible.

What are orphaned Runbooks

Orphaned Runbooks are instances of Runbooks, which Orchestrator, or the Database, thinks that they are running, but they are not. This does not sound very bad, but it can be, trust me. If Problems exists, which are causing orphaned Runbooks, there will be a lot of orphaned Runbooks in a short period of time.

(Read more…)

System Center Orchestrator Health Checker

It is very important to take care of your System Center Orchestrator Environment. I have introduced multiple ways to do this, bit one very important one is the Free Tool called, Orchestrator Health Checker.

This Tool is providing you a lot of options to control and monitor your Orchestrator Environment.

First, you have to Download and configure the Orchestrator Health Checker, Install and Configure Instructions are also included at the Download Page here: https://gallery.technet.microsoft.com/scriptcenter/Orchestrator-Health-Checker-5ef5510f

Overview

After starting the Tool, you should see something like this

image

At the Front, you will see a overview of your runbook, which are running, also the Count of running and queued Runbooks.

Don’t forget to check the “Auto-Update” Checkbox.

(Read more…)

System Center Orchestrator SQL Query–Query failed Runbooks

For your routine Orchestrator Checks, it can be vefy useful to see all failed Runbooks in a period. Of course you can go to each Runbook, and check the Logs, but to be honest, this is not fun.

So, there is a SQL Query to help on this. At the end of the the Query, there is a number, which will control the Timespan of the Query, in our example we want all failed Runbooks from the last 300 Hours, change this to your needs.

SQL Query get failed Runbooks

use Orchestrator

Select Name, TimeStarted, TimeEnded, POLICYINSTANCES.Status
From [Microsoft.SystemCenter.Orchestrator.Runtime].Jobs AS Jobs
 INNER JOIN POLICIES ON Jobs.RunbookId = POLICIES.UniqueID
 inner join POLICYINSTANCES on jobs.Id = POLICYINSTANCES.JobId 
 where POLICYINSTANCES.Status != 'success' 
 and  TimeEnded > dateadd(HOUR, -300, getdate()) 
 order by Name

(Read more…)

System Center Orchestrator SQL Query–Get Parent Caller Runbook

In huge System Center Orchestrator Environments, it is usual to make a lot of Sub Runbooks, that will be called by more than one Parent Runbook.

For Example, you build a Runbook to add a User in a Group. This Runbook will definitely be used by different Parent Runbooks. And in this case, it can sometimes be useful to query all Runbooks, which are calling our “Add User to Group” Runbook.

So, without any longer explanation, here is the SQL Query, which need to be run against the Orchestrator DB.

Don’t forget to change the Name of the Runbook, you want to query, at the End of the Script, in our example the name is “1.1-AddUserToGroup”

(Read more…)

System Center Orchestrator SQL Query–Runbook Run Count

This will be a short Post, sometimes it can be helpful to get a List of Runbooks and the Count, on how many times the Runbook has been executed.

Maybe if you are looking for most executed Runbook in case of an Performance Issue or you just want to track your environment.

Get Runbook Execution Count from the last Month

use Orchestrator

select	Name, count(policies.UniqueID) as Count from Policies 
inner join POLICYINSTANCES on policies.UniqueID=POLICYINSTANCES.PolicyID 
where POLICYINSTANCES.TimeEnded > DATEADD(mm,-1,GETDATE()) 
group by name 
order by Count Desc


 

(Read more…)