In this post, I describe how to troubleshoot slow SCSM portal performance regarding CMDB pickers:
In this post, I explain how we can use the existing techniques of adding controls to an existing form to also modify exiting ones.
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!
I hope it can be of use!
Although it rarely occurs it is sometimes necessary to work with a runas-credential that contains a space in the username (eg a web-service authentication). In pre 2012 R2 environments, spaces are apparently not allowed in the username when entering it through the SCOM console GUI.
Lukcily, the PowerShell interface does not contains such restrictions, and if upgrading to R2 is not an option, you can use the following set of commands to create and distribute a runas-account that contains spaces:
# setup variables
# create a PS credential from the user/password variables
# Connect to the SCOM environment
# Retrieve the agents, management servers or pools to distribute the account to (can be an array of a combination of these object types, use Get-SCOMAgent, Get-SCOMManagementServer or Get-SCOMResourcePool to populate)
# create a simple (or basic) runas-account using the PS credential
# distribute the account
After running these commands, you can verify (but not modify!) the changes in the GUI:
Assigning this account to a profile afterwards is perfectly doable with the GUI however!
Although this post revolves around bypassing a GUI restriction, you can use the same commands of course to administer any runas-account in the context of automation or general nerdyness
Let me know if you have further question on this topic! Jan out!