As many of you know, in Service Manager 2012 it is not easy to find out who exactly marked a Manual Activity as Completed. This information can be found in the history of the Manual Activity where the user is mentioned in the form of so-called 'Down-Level Logon Name' or DOMAIN\UserName. Needless to say that sometimes it is hard to realize that Contoso\josmi is actually John Smith.
In this post, I will show how to add information about an existing class to the SCSM Data Warehouse and quickly generate a report without developing skills. In the same way, you can add the information about your own custom class.
Many SCSM customizers who use Service Manager with non-US regional settings and try to set DateTime value using SMLets cmdlets in PowerShell scripts meet ‘String was not recognized as a valid DateTime’ error.
Last week one of our customers asked how to get a person who actually completed a manual activity. After some investigation, I’ve realized that the only source of that information is a history log of the manual activity.
Recently I was asked how to make a service request change its status from ‘Completed’ to ‘In Progress’ when a new activity was added as a last one in Microsoft System Center 2012 Service Manager. This customer said that it was required in some scenarios and told that it worked for change requests. The idea was to create a custom workflow to realize the required logics.
In this post I described how to create a custom report based on the standard one to present a list of incidents with additional columns Rate and Comment defined in SCUtils SurveyLite. Many of our customers also ask us to do the same for SLA instance durations calculated by SCUtils SLAInstanceDuration solution. I also met the similar requests on the SCSM forums and finally decided to create the report with the information about SLA’s status, name and duration.
In this post I’d like to share one solution for Microsoft System Center 2012 Service Manager that we were recently asked. One company has a practice to notify not only the assigned analyst about a new assignment to the service desk’s ticket but also the analyst who has been withdrawn from that ticket. It asked us for help in doing that for its Service Manager setup.
In this post I wrote how to manage GUID type of the script parameters. Now I want to present an example of such a scripts. Some of SCSM 2012 customers have noticed that ‘Actual End Time’ field of Change Requests is not being populated in the last version of Microsoft System Center 2012 Service Manager. I don’t know why the vendor has removed this workflow but sometimes this field is required in reports to assess the average (max, min) durations of different types of the change requests.
In my previous post I’ve described in detail what type of the parameter SCSM2012 Authoring Tool automatically assigns for the Powershell script’s parameter if this parameter is GUID (in that post it was ID of Service Request). And I mentioned that we needed to control the script’s text in XML file. That is definitely awkward and one of my colleagues has prompted me how to avoid that.
Our product, SCUtils SurveyLite for System Center 2012 Service Manager, provides the functionality to gather user opinions about IT support team’s work. And some of our visitors have been asking about how to make this information available in SCSM reports. For SCSM super-pros this is an easy task but for others it isn’t so obvious. That’s why we’ve decided to make a sample report to present the approach how to achieve the goal. In our scenario we will create the report that lists SCSM incidents with user rate and comment if any.
This issue occurs because the system cannot retrieve trusted and untrusted certificate trust lists (CTLs). If the system does not have access to Windows Update, either because the system is not connected to the Internet or because Windows Update is blocked by firewall rules, the network retrieval times out before the service can continue its startup procedure. In some cases, this network retrieval time-out may exceed the service startup time-out of 30 seconds. If a service cannot report that startup completed after 30 seconds, the service control manager (SCM) stops the service.
Assume that you apply the update that is described in Microsoft Knowledge Base (KB) article 2677070 on a computer that is running Microsoft SQL Server Reporting Services (SSRS). When you try to start SSRS, you receive a time-out error, and event ID 7000 and event ID 7009 are logged in the Application log.