System Center & Automation

Latest Posts

In-place OS Upgrade of Service Manager Data Warehouse Server

In this post, I will show the steps for in-place upgrade of Service Manager Data Warehouse management server (1801) OS from Microsoft Server 2012 R2 to 2016. The OS upgrade is straight forward and may take up to 60 minutes depending on your environment. Stop all Service Manager services. Microsoft Monitoring Agent System Center Data Access Service System Center Management Configuration Disable...

In-place OS Upgrade of Service Manager

In this post, I will show the steps for in-place upgrade of Service Manager management server (1801) OS from Microsoft Server 2012 R2 to 2016. The OS upgrade is straight forward and may take up to 90 minutes depending on your environment. Stop all Service Manager services. Microsoft Monitoring Agent System Center Data Access Service System Center Management Configuration Insert the Windows Server...

Moving Orchestrator Database

In this post, I will demonstrate the steps for moving the remote Orchestrator database to the local management server. Since SQL 2016 is out there, we can also use as our new SQL server. My Orchestrator version is 1807 and SQL is on remote server with version 2012 SP1. It is recommended to upgrade the Orchestrator server OS to the latest before your upgrade the SQL. Install SQL Server 2016 on the...

In-place OS Upgrade of Orchestrator

Since the EOL of Windows Server 2012 R2 has been announced, it is time to upgrade the OS of the System Center products to Server 2016. In this post, I will show the steps for in-place upgrade of SCO management server (1807) which has all the Orchestrator services. The OS upgrade is straight forward and may take up to 90 minutes depending on your environment. Stop all Orchestrator services...

In-place OS Upgrade of Configuration Manager

In this post, I will show the steps of upgrading SCCM OS from Windows Server 2012 R2 to 2016. First, remove the WSUS role and System Center Endpoint Protection (SCEP) client from the server if they are installed. Locate the Windows Server 2016 installation media and start the upgrade process. Make sure your Antivirus software is compatible with 2016 otherwise you will be prompted to uninstall it...

How to use SQL Server 2017 with SCOM 1807?

With the release of SCOM 1807, you can now use SQL Server 2017. In order to do that, you should first upgrade to SCOM 1807 and then upgrade your SQL 2016 to 2017. This looks a bit frustrating but the upgrade process is painless and straight forward. You can read my previous post on how to upgrade SCOM 1801 to 1807. After upgrading SCOM, use the SQL Server 2017 media and upgrade your SQL 2016...

Upgrading SCOM 1801 to 1807 using WSUS and SCCM

In this post, I will show you how to upgrade SCOM 1801 to 1807 using WSUS and SCCM. Unfortunately there is no baseline media for SCOM 1807 that’s why you need to upgrade your environment using the patch files. There is also a way to download the updates manually from the Microsoft Update Catalog, using SCCM and WSUS is a better and faster solution. Requirements: SCCM with WSUS integration...

Get AC Unit Temperature with Orchestrator

The other day I was requested to develop an interface that displays the temperature of the Air Condition (AC) units. You may ask that how is this possible and what is the relationship with IT? Well, I asked the same questions but after digging a bit more, I found out that our AC unit has web interface based on XML. Here is how the XML looks like. In order to build an interface, I need the...

SCSM 2012 Activity Prefix Sorunu

Servive Manager 2012 sürümlerindeki bir bug dolayısıyla mevcut Incident ya da Service Request üzerine Manual ya da Review Activity içeren bir şablon uygularsanız aktivitelerin MA ya da RA prefixleri olmadan açıldığını görürsünüz. Bunu gidermenin yolu şablonun kayıtlı olduğu XML Management Pack‘i bilgisayarınıza indirip aşağıdaki kodları ilgili yerlere eklemekten geçmektedir. Review Activity...

Service Manager Convert Incident To Service Request Console Task

Service Manager konsolda açılmış herhangi bir Incident kaydını Service Request’e dönüştürme özelliği bulunmaktadır. Bu özellik Incident‘a ait Affected User, Title ve Description parametrelerini kopyalayarak Service Request kaydına aktarmaktadır ancak Incident kaydı açık kaldığından elle kapatılması gerekmektedir. Çağrı yoğunluğunun çok olduğu sistemler düşünüldüğünde Incident‘ın...

System Center & Automation

Categories