System Center Service Manager (SCSM) Authoring Management Pack tips and best practices

When using the SCSM Authoring Management Pack, follow these tips and best practices for best results. These are not always presented in order, so please read through this post before setting up your MP. Disable the MPSSyncJob Schedule before importing custom Management Packs until you determine you like the results of your custom changes on… Read more

System Center 2016 now supports TLS1.2 security protocols

TLS 1.2 is the secure way of communication suggested by Microsoft with best-in class encryption. SSL and early TLS are not considered strong cryptography and cannot be used as a security control. Microsoft has added official support for TLS1.2 security protocols in System Center 2016. This protocol is now supported in the following products: System… Read more

KB: Configuration Manager 2007 client operations fail after you install a May 2017 security update for Windows Server 2008 R2

We have released a new KB article Configuration Manager 2007 client operations fail after you install a May 2017 security update for Windows Server 2008 R2 which contains a solution to the following issue: Client-related operations fail in an installation of Microsoft System Center Configuration Manager 2007 that has the server locator point (SLP) role… Read more

Troubleshooting Service Manager work item (Incident, Change Request, Service Request) status stuck on “New”

Any time we see newly created work items stuck with a “New” status, it generally means that the Service Manager workflows are not processing or are processing slowly. Monitoring the “Minutes behind” of each workflow can be a useful method of troubleshooting. The following web page has good troubleshooting tips and a SQL query that… Read more

Extending the support of platforms for SCSM 2016

Hi everyone! Thanks for sharing your feedback and experiences with the Service Manager 2016 deployment. We heard you, and to make your deployment and upgrade experience better, we are now extending the support of following platforms for Service Manager 2016 – Support of SQL server 2014 SP2 for both SM 2016 & 2012 R2 As… Read more

Service Manager now available in System Center 2016

Hi everyone! We are delighted to announce the availability of System Center 2016 Service Manager. This new release of Service Manager contains a wide array of additions & improvements- its faster, provides better usability, and comes with many new features. When we talk about performance, this release of Service Manager  is a big leap from… Read more

Monitoring Service Manager with Microsoft System Center Operations Manager

Microsoft System Center Operations Manager, along with the Service Manager management packs, provides an excellent monitoring platform for Service Manager. Many important pieces that are vital to Service Manager health can be monitored, including: Checking SQL Server to be sure the Broker Service is enabled Checking the Service Manager Grooming History to be sure cleanup… Read more

Removing a Service Manager WorkItem using native PowerShell cmdlets and confirming what happens to the user relationship

Hi everyone, this is Austin Mack from the Microsoft Service Manager support team. Recently I was asked how to remove a Service Manager WorkItem (Incident, Service Request, Change Request, Release Record, Problem). I was also asked to verify that the relationships associated with the WorkItem did not get orphaned. Service manager relationships have two end points, and if… Read more

Service Manager #LyncUp calls

We are currently heads down working towards the System Center 2016 launch. As such, on June 24th, we sent out a cancellation notice for the Service Manager #LyncUp calls, with the plan to resume it post System Center 2016 GA (General Availability). Meanwhile, it has been brought to our attention that on August 16th, a few… Read more

SCSM 2016 – Upgrade steps for custom development

With the SCSM 2016 release, the product has moved to support .Net 4.5.1. The tool set to support this move to .Net 4.5.1, required to break few dependencies and has led to the movement of classes across the assemblies. This may break the custom solutions made by 3rd party (non-Microsoft) after upgrade to SCSM 2016…. Read more