The role model in Service Manager is quite complex and contains many levels: a scopes, a user roles and a user role profiles. Although scope and user roles are well documented and available in UI, the user scope profile is very hidden part of the role model, but one of the most powerful feature if you working with custom classes and custom relationships.
When you want to apply template on work item it’s extremely easy: you need to call ApplyTemplate method of the EnterpriseManagementObject or EnterpriseManagementObjectProjection class instance (with one exception – template shouldn’t contains activity for Service Requests, Change Requests or Release Records). But what if you want to create new object based on template? From first view it’s look not very hard – just call appropriated constructor. But in fact this is just first step of list of required steps: required or optional.
As you know when you deleted connector in SCSM all configuration items discovered (or imported) by this connector will also be deleted. But good question is how determinate which CIs will be deleted? This can be done using some SQL queries but this is complex, unsupported way and you must have SQL Management Studio installed. But we have a power of PowerShell and can use it to get this information.
UPDATED: Thanks to Aaron to pointing me to the right direction. Approach below allows you get CIs updated by specified connector. But SCSM stores all connectors for CI object and even if no properties was updated during connector’s sync process, this connector will be added to object. In other words, if you have object that discovered by more than one connector then this object will be removed only if all connectors will be removed.
This article describe how to generate link to specified request offering or to Generic Request on the Self-Service Portal. This can be helpful in email massages or on the custom portals\external systems. To do that you should complete two steps: get IDs of the Service Request and Request offering and generate link.
Office365 is a cloud-based solution which allows you to host email and SharePoint at microsoft’s servers on the cloud. And if you already use this solution and starting using the SCSM when early or later you want to send notifications to Exchange Online mailboxes. That simple at first glance solution is not really simple. The main problem that Office365 doesn’t support Windows authentication. So the only way is send all emails through your local SMTP relay. In this post I’ll talk how to setup and configure all chain to send notifications from SCSM to Office365.
Sometimes you need to know which objects contain the queue. This can be done easy with PowerShell.
When you have installed the SCSM web-portal you will have two sites: standard root site for team work and child site SMPortal with SCSM web-portal itself. If you want to use one SMportal you can move it to root level.
Some time ago Travis was publish the article about how to deploy SCSM web-parts to existing Sahrepoint server. But this instruction is very complex, and same tasks can be acomplished with much more easy way without manually copying files, editing the web.config and etc.