Update Rollup 4 for System Center 2012 Service Pack 1

UR 4 for System Center 2012 SP1 is out. There are a lot of fixes for SCVMM, SCOM and SCSM so check it out here.

System Center Service Manager Connector 3.0 for Exchange Re-released

The Exchange connector for SCSM is re-released offering some unknown bug fixes. If you have some bugs with your Exchange connector you might try to update and see if your issues are fixed if they are not you are not among the lucky ones.

First Look at OpsLogix’s VMware Management Pack (beta)–Part II

After taking a first look at OpsLogix’s VMware Management Pack I’ve released I’ve missed something that I usually test with such core MPs like this one. That test is to bring the discovered objects from SCOM to SCSM as Configuration Items. It is not something hard to do and I’ve described the process before here but nevertheless I think it will good to see it visually in this blog post.

First you need to import OpsLogix IMP –Base Library MP and OpsLogix IMP – VMWare MP in Service Manager.

image

But before actually importing these two you need to import also their dependencies:

image

image

In my case I’ve needed to import Operations Manager Internal Library, System Center Visualization Library and System Center Image Library. All management packs can be found in the SCOM installation in the Management Packs folder. Keep in mind that for the System Center Visualization Library the MPB file have to be imported:

image 

After successful import you need to configure your Operations Manager CI connector in SCOM to sync the VMWare MP:

image

Next we need to put some classes in the SCSM allow list in order to sync the instances for that classes. The classes we will find in SCOM Discovered Inventory View:

image

Now that we know the display names of the classes we can easily find their internal names with PowerShell.

image

You need to start Operations Manager cmdlet and execute the following commands:

  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Cluster"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Datacenter"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Datastore"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware ESX Server"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Network"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Resource Pool"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware vCenter"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Virtual Machine"}

Basically we need the following classes:

  • OpsLogix.IMP.VMWare.Cluster
  • OpsLogix.IMP.VMWare.Datacenter
  • OpsLogix.IMP.VMWare.Datastore
  • OpsLogix.IMP.VMWare.ESXServer
  • OpsLogix.IMP.VMWare.Network
  • OpsLogix.IMP.VMWare.ResourcePool
  • OpsLogix.IMP.VMWare.vCenter
  • OpsLogix.IMP.VMWare.VirtualMachine

Now that we have the internal names of the classes we can easily put them in SCSM allow list again with PowerShell:

image

I am using the built-in SCSM PowerShell cmdlets and executing these commands:

  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Cluster
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Datacenter
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Datastore
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.ESXServer
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Network
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.ResourcePool
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.vCenter
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.VirtualMachine

To verify that the classes are added to the allowed sync list you can use: Get-SCSMAllowList

Next you need to force sync on your Operations Manager CI connector. After the connector syncs successful you can create several views to check if the instances of these classes are synced:

image

image

image

image

image

image

image

The beta of the MP does not discover a lot of properties for the objects but I am hoping this will be changed in the final version or some of the next ones as proper and rich CMDB is important.

Some Tips on Upgrading System Center 2012 SP1 to R2 Preview

After covering the installation of the R2 wave for System Center 2012 I will now cover the upgrade from SC 2012 SP1 by providing some tips.

Note: Do not upgrade your production environment to R2 Preview. Only try to upgrade in lab environment.

So let’s start. With System Center we need upgrade sequence for upgrading the different components. Currently there is not such publically available but we can use the upgrade sequence for SC 2012 SP1:

1. Orchestrator

2. Service Manager

3. Data Protection Manager (DPM)

4. Operations Manager

5. Configuration Manager

6. Virtual Machine Manager (VMM)

7. App Controller

I will not be able to cover Configuration Manager, Data Protection Manager and App Controller as I do not have them in my lab. Also Service Provider Foundation is not listed in the upgrade sequence list but as it is part of Orchestrator I am putting it also on first position.

Upgrading to Orchestrator 2012 R2

In order to Upgrade to R2 you have to remove all Orchestrator 2012 SP1 roles. By removing them, retaining the database and starting the R2 installation you will be able to upgrade without data loss. Unfortunately after upgrading I’ve stumbled upon on the bug with the not working web service. Besides that bug runbook designer was working OK and all my runbooks were intact. After upgrading Orchestrator you have to upgrade your Integration Packs also to R2. You can download them from here. As my web service was not working and I couldn’t fix it even with my own workaround in the end I’ve end up on creating a new Orchestrator 2012 R2 and migrating all my data.

Upgrading to Service Provider Foundation 2012 R2

SPF 2012 R2 requires to be installed on Windows Server 2012 R2. So I’ve created a new WS 2012 R2 server hoping that I will start the installation pointing to my old database so SPF can upgrade it. Again unfortunately when I’ve done that the installation stuck on Updating Database for more than 40 minutes at which time I’ve decided to cancel the installation. Installation wasn’t responding to cancel command so I’ve ended up killing it. In the end I had to install completely new SPF server with a new database. I’ve couldn’t migrate my old data.

Upgrading to Service Manager 2012 R2

With Service Manager in most cases you will have at least one Service Manager Management Server and one Service Manager Data Warehouse. To upgrade to R2 you have to start with the Data Warehouse server first. Before upgrading it is best to stop all data warehouse jobs. I haven’t met any issues with upgrading the Data Warehouse server. After DW you can continue with the Management Server. Before upgrading it is good idea to disable all connectors. Again I was having no troubles with this upgrade also. Keep in mind that in a new installation of SCSM 2012 R2 System Center Management Service is renamed to Microsoft Monitoring Agent. This is not the case with upgrade that service stays named System Center Management. After upgrade start the DW jobs and enable the connectors. Make sure all are finished successful.

Upgrading to Operations Manager 2012 R2

Operations Manager upgrade also went flawless. The one thing I’ve done before upgrading is to brake the SCOM-SCVMM integration and remove the VMM MPs.  I’ve upgraded Management Server and Reporting server without issues. After the upgrade you need to upgrade the SCOM agents on all servers you are monitoring. If you have somewhere Service Manager Console installed (like terminal server) you will need to uninstall the console and than upgrade the agent. You may also need to update some of your MPs to the preview versions. VMM 2012 R MPs are located in a folder of the VMM 2012 R2 installation. Do not import only the Dashboard MP from there but rather download it from here. If you have data that is synchronized between SCOM and SCSM and you’ve updated some MPs in SCOM that are also imported in SCSM you will need to update them there also.

Upgrading to Virtual Machine Manager 2012 R2

VMM also does not support in-place upgrade. You have to uninstall VMM and retain the database. Before uninstalling VMM first uninstall any Update Rollup if you have such. After uninstalling VMM, ADK (Windows Assessment and Deployment Toolkit) 8.0 also have to be uninstalled. Before starting the VMM 2012 R2 installation you have to install ADK 8.1. After VMM 2012 R2 installation is easy. You have to point a few settings, the installation will detect that you want to make upgrade to existing database and after a few minutes you will be upgrade to R2. After successful upgrade you need to start the console and update your VMM agents also.

Overall the upgrading experience to R2 is good but there are few serous bugs that needs to be fixed or at least upgrade documentation to be available to help you when RTM arrives which today was announced that it will be 18th of October. Mark you calendars.

Where is my System Center Management Service in SC 2012 R2?

If you’ve already installed SCOM 2012 R2 you’ve probably noticed that System Center Management Service is gone. Now we have Microsoft Monitoring Agent:

image

But that is not all folder location is also changed:

image

You will notice the change also in the Control Panel:

image

We already know that changes are not only in the name now but the service can actually can be leveraged by other products. Could we see in the future this agent be leverage by other products as well? May be something like Windows Azure Monitoring (WAM) or Windows Azure Operations Manager (WAOM)? We can only speculate for now and wait to see what will happen.

Note 1: This is not the first time the name of the service is changes in 2005 it was MOM, in 2007 RTM/SP1 it was OpsMgr Health Service and in 2007 R2, 2012 and 2012 SP1 it was System Center Management Service.

Note 2: The built-in agent in Service Manager 2012 R2 is also renamed to Microsoft Monitoring Agent in services.msc and Control Panel so if you need to restart Service Manager 2012 R2 health service you have to restart Microsoft Monitoring Agent. The installation folder of the agent is where Service Manager is installed.