After having done several SCSM upgrades over the past weeks, I noticed the following issue showing up from time to time.

http://www.jvm-net.com/2017/06/26/SCSM-2016-Console-Crash-RunAs/

Looking for the best way to upgrade to SCSM 2016. You can read my experiences here.

In this post, I describe how to troubleshoot slow SCSM portal performance regarding CMDB pickers:

Slow loading of CMDB picker controls in the SCSM portal

In this post, I explain how we can use the existing techniques of adding controls to an existing form to also modify exiting ones.

http://www.jvm-net.com/2017/03/19/scsm-multitenant-3/

In the previous post I talked about the basic idea of setting up SCSM as a multi-tenant platform in your organization.

This post will show you how to make any CI/WI multi-tenant aware by adding custom list-fields.

This is the first post in a series about how to setup and extend SCSM to make it shine in an environment where multi-tenancy is required.

Full article here

During a SCSM migration, I encountered some issues when moving data with the smlets module.

All information here: http://www.jvm-net.com/2017/02/23/beware-of-the-scsm-smlets-smdefaultcomputer-feature/

I found a workaround to the scenario where AAD-joined devices without InstantGo do not store their Bitlocker info in AAD. Read about it here: http://www.jvm-net.com/2016/12/20/store-bitlocker-recovery-keys-in-aad/

I build a webhook activity for Service Manager that allows you to connect your service request process to the cloud!

Read all about it here: http://www.jvm-net.com/2016/11/28/the-service-manager-webhook-activity/

It is common to have multiple SCOM management groups in an organization. For example a test MG to stage changes and a production one for day-to-day operations. If your monitoring processes rely heavily on SCOM subscriptions (for automation with command channels, or just mail for example), it might be tedious to keep them in sync across all the different management groups. Creating or copying subscriptions by GUI is click-intensive and prone to error. By automating this part of the monitoring process, it can greatly speed-up and simplify things.

A customer of mine relies on subscriptions for integration with other systems. Per monitored service, a subscription exists that passes all relevant service alerts through an executable that performed a part of the integration. Just like the service monitoring itself, the subscription is created in a test environment, validated and then copied to production. The script I am showcasing has limited (only single-channel mail- or command channel based subscriptions are supported) but worry-free capabilities for quickly copying a subscription. This is done by passing the to-copy subscription’s displayname, a management server for the source management group and one for the target management group. For now, you need to run the script with an account that has administrator rights in both locations. A nice feature is that if the source subscription already exists in the target MG, it will only sync the configuration without fully deleting or recreating it!

Check it out on GitHub

I hope it can be of use!

Jan out