Showing posts with label System Center Service Manager 2012. Show all posts
Showing posts with label System Center Service Manager 2012. Show all posts

Tuesday, October 23, 2012

SCSM 2012 : Work Item Running Number

One counter for all types of work items:
For instance:

  • New Incident = IR1
  • New Change Request = CR2
  • Change Request contains 2 activities = RA3 and MA4
  • New Incident = IR5

and so on

All work items are sharing the same counter for ID. Only the prefix is added to this ID based on the work item class (IR, CR, PR, SR, MA, RA).
For this reason the ID is not increment uniformly for each type of work item.
This behavior can't be changed. 

However, you can set the starting number by changing a value in the database.

Basically there is this table in the ServiceManager database called the AutoIncrementAvailableRange table.  This value stores the next available number for a particular class property.  If the last work item ID that was handed out was 1234 this table would show 1235 and then once 1235 was used it would say 1236.  You get the idea.  So, by changing this number we can change the base number that we start from.  Let’s say for example that we always want our incident IDs to be in the 10,000+ range.  We could change thus number to 10000 and start from there.  Definitely don’t set it lower than the current number though!  That will most likely be very bad.

Use the SQL command below to set the new number you want
update AutoIncrementAvailableRange
set FirstAvailableValue = 10000 
where ManagedTypeId = 'F59821E2-0364-ED2C-19E3-752EFBB1ECE9' and ManagedTypePropertyId = '28B1C58F-AEFA-A449-7496-4805186BD94F'
Use the command below to check if the value changed to the one you set using command above
from ManagedType as MT, ManagedTypeProperty as MTP, AutoIncrementAvailableRange as AIAR 
where MT.ManagedTypeId = AIAR.ManagedTypeId and MTP.ManagedTypePropertyId = AIAR.ManagedTypePropertyId
Notice that at the end of the role "System.WorkItem", at the "FirstAvailableValue" column, the number is the number you have set.

Sunday, May 6, 2012

SCSM 2012 RTM : Self-Service Portal Installation

In this blog, I will be sharing with you of the SCSM 2012 Self-Service Portal (SSP) installation and configuration. The point i am sharing this as through my test and deployment experience, the SSP for SCSM 2012 is not easy.

Software Prerequisites:

Firstly, we have to make sure all the software prerequisites below are met:-
  • Windows Server 2008 R2 RTM or with SP1
  • IIS 7.5 with IIS 6 metabase compatibility
  • Self-signed SSL certificate (follow the FQDN of the SSP server)
  • ASP.NET 2.0
  • Microsoft .NET Framework 4.0
  • Microsoft Analysis Management Objects
  • Microsoft SharePoint Foundation 2010
  • Excel Services in SharePoint 2010 is required for hosting dashboards for advanced analytical reports


I will skip all the screen shot of the installation of SCSM 2012 RTM as i have recorded the process in the video below:-

You can go to this link for the video above.

Post-Installation and Configurations:

Soon after the completion of the installation. You may not get the Silverlight to load the page completely and it end up partially blank as below:-

The installation does not end here. you may now have to look a little bit more in depth of each component configurations.


From the IIS both SCSMWebContentServer and Service Manager Portal has to bind to the same certificate.

The FQDN that has to be changed manually.

Certificate for client browser:

You have to trust the certificate that binds to the SSP.

After all the above are verified, you should be getting a page look similar as below:-

SMPortal, it works !!

And here you can see my SSP showing the case i have logged through the Portal.

Other Useful Links:

  • Nothing more useful than the top-to-bottom details about SCSM 2012 which you can find from this link.

  • Useful sharing by Petri on SCSM 2012 Beta with screen cast step-by-step

Monday, April 30, 2012

Enable Schedule for SCSM 2012 ETL

By default, the schedules for the extract, transform, and load (ETL) jobs are not enabled. If ETL is now enabled, you will get no data from SCSM console when generating any report.

In this release of Service Manager (System Center 2012 – Service Manager), you can enable the schedules only by using Windows PowerShell.

Enable-SCDWJobSchedule –JobName Extract_<data warehouse management group name>
Enable-SCDWJobSchedule –JobName Extract_<Service Manager management group name>
Enable-SCDWJobSchedule –JobName Transform.Common
Enable-SCDWJobSchedule –JobName Load.Common