System Center Service Manager
System Center Service Manager tips tricks and discoveries across the web. Follow this blog and receive notification via email on new posts, or grab the feed URL.
Thursday, April 9, 2015
Script to Monitor Service Manager Workflows
Wednesday, September 3, 2014
Tip: Approve all In Progress Activities in Service Manager
SMLETS and powershell makes our lives much easier when it comes to administration. However, review activity relationships are slightly different than most other relationships. It can sometimes be difficult to figure out what to do when it comes to powershell and reviewers.
The below powershell script retrieves all review activities, retrieves the reviewers for those activities, and then sets the decision to approved. This will allow the review activity to review the decisions, and then complete itself - exactly as it would happen inside the console.
If you don't care how it works, then just grab the script and run it on your management server where you have SMLETS installed.
If you want to learn a little and become a better Service Manager Administrator, I have broken down the script.
If you don't have SMLETS, you can get it from Codeplex.
The script with explanation comments:
#This is pretty self-explanatory, but we are importing SMLETS.
Import-Module SMLETS
#Before we can retrieve any objects, we need to get the object class. The Object class we are looking for is "ReviewActivity". Why the "$" (dollar sign) at the end? As part of this particular cmdlet, the search is using regexp. The "$" marks the end of the line. We use this because there are cases where the cmdlet would retrieve more than one object class due to regexp matching.
$RAC = get-SCSMClass System.WorkItem.Activity.ReviewActivity$
#We need to filter out object results to only "In Progress" review activities. "Activity Status" is an enumeration.
$ActStatusEnumInProgress = Get-SCSMEnumeration ActivityStatusEnum.Active$
#We need the GUID of the enumeration so our "filter" switch will retrieve the correct results.
$InProgressEnumId = $ActStatusEnumInProgress.id
#Here, we are querying the review activity objects. The "class" switch specifies what class we want, in this case, "review activity".
#The "Filter" switch is a server side filter that is far more efficient than "Where-object". We can filter on any column for that object.
$RAS = get-SCSMObject -class $RAC -filter "Status -eq '$InProgressEnumId'"
#So far, we should have all of the Review activities that are in progress. You can type $RAS to see a list of the review activities.
#We probably have more than one activity in an array, but we need to perform actions on each individual object.
foreach ($RA in $RAS){
#We are going to retrieve any relationships for each activity, where the activity is the source of the relationship.
$RElObj = Get-SCSMRelationshipObject -BySource $RA
#We do not want all relationships, only the reviewer relationship.
foreach ($Obj in $RELObj) {
if ($Obj.TargetObject.ClassName -eq "System.Reviewer") {
#Now we are getting the reviewer object itself, but rather than specifying class and filter, we have the GUID. We can use the "id" switch.
#Once we get the object, we are piping the object into the "Set-SCSMObject" command, which will update the object. The only thing we have to do is set the status to approved for each of the reviewers and internal SCSM workflow will take care of the rest.
#The command below will not actually make any changes. The "whatif" switch is a powershell switch that essentially tells you what the command is going to do, but does not commit the command. This is a great way to test non-destrutively.
#Many commands perform actions without output, so it is sometimes difficult to see what is going on. The "verbose" switch will output additional details at command execution.
#If you are ready to execute the command and approve your activities, simply remove "-whatif".
get-SCSMObject -id ($Obj.Targetobject.ID) | Set-SCSMObject -Property Decision -Value "Approved" -whatif -verbose
}
}
}
Import-Module SMLETS
$RAC = get-SCSMClass System.WorkItem.Activity.ReviewActivity$
$ActStatusEnumInProgress = Get-SCSMEnumeration ActivityStatusEnum.Active$
$InProgressEnumId = $ActStatusEnumInProgress.id
$RAS = get-SCSMObject -class $RAC -filter "Status -eq '$InProgressEnumId'"
foreach ($RA in $RAS){
$RElObj = Get-SCSMRelationshipObject -BySource $RA
foreach ($Obj in $RELObj) {
if ($Obj.TargetObject.ClassName -eq "System.Reviewer") {
get-SCSMObject -id ($Obj.Targetobject.ID) | Set-SCSMObject -Property Decision -Value "Approved" -whatif -verbose
}
}
}
When you begin writing powershell scripts, it is a good idea to keep them in a repository, as you will most likely need them more than once, especially when it comes to System Center. If you want to talk more about powershell or System Center, come see me at Techfest Saturday, September 13th at the Sparkhound booth!
Techfest Registration: Techfest Registration
Techfest Site: Houston Techfest
Friday, August 1, 2014
Orchestrator - Misrepresented and Misunderstood
Tuesday, April 22, 2014
Query ALL Service Manager ENUMS and their Hierarchy
SELECT [EnumType].[EnumTypeId] AS Id,
[EnumType].[ManagementPackId] AS ManagementPackId,
ep.EnumTypeName,
[EnumType].[EnumTypeName] AS Name,
[EnumType].[EnumTypeAccessibility] AS Accessibility,
[EnumType].[ParentEnumTypeId] AS ParentId,
DisplayName
into #eview
FROM dbo.EnumType
LEFT Join dbo.EnumType ep on EnumType.EnumTypeId = ep.EnumTypeId and ep.ParentEnumTypeId IS NULL
LEFT OUTER JOIN DisplayStringView DS1 ON DS1.LTStringId = dbo.[EnumType].[EnumTypeId] AND DS1.LanguageCode = 'ENU'
INNER JOIN dbo.ManagementPack
ON dbo.ManagementPack.ManagementPackId = [EnumType].ManagementPackId AND dbo.ManagementPack.ContentReadable = 1;
with tree as (
SELECT ManagementPackid, Id, name,
cast(DisplayName as varchar(max)) as Hierarchy,
DisplayName,
ParentId
FROM #eview
Where ParentId IS NULL and displayName IS NOT NULL
UNION ALL
SELECT c.ManagementPackId, c.Id, c.name,
p.hierarchy + ', ' + cast(c.DisplayName as varchar(max)),
c.DisplayName, c.ParentId
FROM #eview c
join tree p on p.Id = c.parentID
WHERE c.displayName IS NOT NULL
)
select ManagementPackid, parentid, Name, Hierarchy, DisplayName
from tree
order by 3
drop table #eview
Thursday, February 13, 2014
Get Parent Affected User for Notifications
$Context/Path[Relationship='CoreActivity!System.WorkItemContainsActivity' SeedRole='Target' TypeConstraint='WorkItem!System.WorkItem']/Path[Relationship='WorkItem!System.WorkItemAffectedUser' TypeConstraint='System!System.User']/Property[Type='System!System.User']/FirstName$
Obviously it is only the first name and the references will need to be changed to match the reference alias in the MP.
Tuesday, September 3, 2013
SCSM 2012: Self Service Portal Service category color customization
http://www.expiscornovus.com/2012/05/06/scsm2012-self-service-portal-service-category-color-customization/
SCSM 2012: Self Service Portal Service category color customization
The Self Service Portal is a solution on SharePoint 2010 which deploys some web parts. Like Travis Wright described in his latest Self Service Portal blogpost those web parts use Silverlight .xap files. After some .NET Reflector work on the Portal.BasicResources DLL. I found that a lot of the color styling for the portal is being done by using brushes.
A brush is an Silverlight object which can be used to paint for example solid colors or linear gradient. In that DLL I found a .xaml file which defined some solidcolorbrushes and they had a key. In Silverlight they use a 8 digit notation for the color, this is a RGBA value.
The Self Service Portal actually has a settings.xml file which can be used to define some basic settings. I noticed it also had some setting keys for colors. This triggered me to add a key for one of the brushes, ExpanderHeaderBgBrush. My attempt worked. After adjusting the Settings.xml and clearing my browsers cache I saw a new green color!
1. Go to C:\inetpub\wwwroot\System Center Service Manager Portal\ContentHost\Clientbin (or another location if your installation directory was different
2. Open the Settings.xml file
3. Add a setting key for ExpanderHeaderBgBrush with your desired RGBA color:
Tuesday, July 23, 2013
Isolating Powershell Sessions in Workflows in Service Manager
One common issue I have ran into with writing workflows for Service Manager is the powershell sessions seem to be shared. When I call a set of cmdlets, such as the Active Directory cmdlets, they do not always load/unload properly, causing issues with subsequent scripts.
Solution:
We can isolate the powershell sessions inside the Service Manager Workflows. While powershell experts may know this, most of us don't, so here is my non-expert explanation.
- When you run Service Manager Workflows, they run in the same process.
- If these workflows are running powershell, the powershell sessions are sometimes (or always) shared.
- By "running powershell inside a powershell" we can isolate our scripts, preventing issues between shared sessions.
- Once the script is complete, it cleans itself up, and completely closes the sessions.
Powershell {
Another Example with Parameters:
Powershell {
param($Name, $pcc);
get-process $Name -ComputerName $pcc;} -args "explorer", "localhost"
Friday, May 3, 2013
Create and Assign Service Manager Incidents Directly from SCOM on Demand
The Issue
If you use Operations Manager and Service Manager, you know by now that SCOM will automatically create Incidents in Service Manager. However, for most organizations, this just doesn’t make sense because they do not have a 1-to-1 Alert-to-Action ratio. You can set up basic criteria to limit the automatic creation, but this usually still results in too many unnecessary incidents. As a result, most organizations do not utilize this connector, which at one point was one of the most requested features of SCOM – to do really cool things with ticketing systems.
The Solution
So, instead, I have created a solution that will allow you to create incidents on demand directly from a SCOM Alert, while utilizing all the cool features of the Service Manager SCOM Alert connector. All you have to do is right click the alert(s) to create the on-demand tickets.
What are some features of the solution in conjunction with the native Connector:
- Right click one more multiple alerts and assign incidents directly to the specified group/user
- Closing the alert closes the ticket and vice-versa
- The Assigned User and the Ticket Id are maintained in the alert as sourced from SCSM
- The affected component in SCOM is automatically added as a related configuration item in SCSM
- Easily can be extended to do more fun stuff with only basic PowerShell Knowledge
How Does it Work
The solution utilizes the following components:
- SCOM and SCSM obviously
- A very small PowerShell Script
- SCOM CMDLETS
Workflow:
- A user right clicks the alert and sets the resolution State.
- A Command Subscription triggers based on the resolution state, sets a couple of custom fields, and changes the resolution state to “Generate Incident” a
- The SCSM Alert connector triggers based on the new resolution state, generates an incident, and applies an incident template based on data in the custom fields.
How to Implement the Solution
These Steps need to be performed in SCOM
Step One
Copy the following PowerShell script code and save on your SCOM management server as UpdateCustomFieldPowershell.ps1. (I took this code from another blog online and modified it as my own. Unfortunately, I don’t know who wrote the original script.)
Param($alertid)
$alertid = $alertid.toString()
write-eventlog -logname "Operations Manager" -source "Health Service Script" -eventID 1234 -entrytype "Information" -message "Running UpdateCustomFieldPowershell"
Import-Module OperationsManager; "C:\Program Files\System Center 2012\Operations Manager\Powershell\OperationsManager\Functions.ps1"; "C:\Program Files\System Center 2012\Operations Manager\Powershell\OperationsManager\Startup.ps1"
$alert = Get-SCOMAlert -Criteria "Id = '$alertid'"
write-host $alert
If ($alert.CustomField2 -ne "AlertProcessed")
{
$AlertResState = (get-SCOMAlertResolutionState -ResolutionStateCode ($Alert.ResolutionState)).Name
$AlertResState
# $alert.CustomField1 = $alert.NetBIOSComputerName
$alert.CustomField1 = $AlertResState
$alert.CustomField2 = "AlertProcessed"
$alert.ResolutionState = 254
$alert.Update("")
}
exit
Step Two
We need to create some new alert resolution states. The alert resolution states will trigger the script. You want to create a resolution state for each support group you would assign an alert. You can use whatever format you want. I used the format of “Assign to GROUPNAME”. Also keep in mind the Resolution State Ids and order you will use. I made my alphabetical. DO NOT use the resolution state 0,1,254, or 255.
To create new resolution states:
- Go to the SCOM Console
- Go to the Administration Workspace
- Go to Settings
- Select Alerts
- Select the new button, create a resolution state and assign an Id. Resolution states will always be ordered by their Id
- Repeat for each resolution state
After you create your alert resolution states, you will need to create one more that triggers the SCSM Connect. Name this Alert Resolution State “Generate Incident.” Also, make sure this is the exact name as the script requires. If you want to change the name, you will have to update the script. Also, set the Id to 254.
Step Three
We need to set up a command channel and subscription that will trigger and run the script.
- Open the SCOM Console
- Go the the Administration Workspace
- Go to Channels
- Create a new Command Channel
- Enter the full path of the above script
- Enter the command line parameters as shown in the example below (Be sure the use the double and single quotes correctly)
- "C:\OpsMgrProductionScripts\SCOMUpdateCustomField.ps1" '$Data/Context/DataItem/AlertId$'
- Enter the startup folder as C:\windows\system32\windowspowershell\v1.0\
- Save the new Channel
Next, we need to set up the subscriber for the command channel.
- Open the SCOM Console
- Go the the Administration Workspace
- Open subscribers
- Create a new subscriber
- In the addresses tab, click Add
- In the subscriber address, set the channel type to command and then select the channel you set up in the previous steps.
- Save the address and the subscriber
Next, we need to set up the Command Subscription
- Open the SCOM Console
- Go the the Administration Workspace
- Open Subscriptions
- Create a new Subscription
- On the subscription criteria, check the checkbox “with a specific resolution state”
- Select all the new resolution states except “Generate Incident” (Do not select anything other than the assignment states)
- On the subscribers, add the new subscriber you created in the previous steps
- On the Channels, add the new channel you created in the previous steps
- Save the subscription
Step Four
The last thing we have to do in SCOM is set up the Alert connector. The alert connector will be triggered based on the resolution status of “Generate Incident”.
- Open the SCOM Console
- Go the the Administration Workspace
- Go to connectors and select Internal Connectors
- Open the SCSM Alert Connector
- Create a new subscription in the connector
- In the criteria of the subscription
These Steps need to be performed in SCSM
Step One
The first thing you want to do is enable and connect your SCSM SCOM Alert Connector. If you do not know how to do that, you can refer to technet. http://technet.microsoft.com/en-us/library/hh524325.aspx. Verify it works before moving any further.
Step Two
- Create a new Management Pack dedicated to storing the SCOM Incident Templates in SCSM
- Create a SCOM incident template for each group that you want to assign via SCOM. Typically, this is about 10-20 templates. For testing purposes, I would just start with one or two.
- Add the correct group as the assigned to in each template. It is not necessary to fill any other information.
Step Three
- In SCSM open the SCOM Alert Connector
- Go to the alert routing rules and add a new rule
- For each rule select one of the templates that you created
- On the select criteria type, select the Custom Field radio button
- For custom field one, enter the exact name of the resolution state you used in SCOM. For example, if you are going to assign to the server team, and the name of resolution state is called “Assign to ServerTeam”, this is the exact phrase you need to enter into Custom Field one.
- Select Custom Field two from the drop down
- For custom field two, enter “AlertProcessed”
- Click OK
- Repeat for each template
Time for Testing!
Now you are ready to test. Find an alert in SCOM, right click the alert and set it to a resolution state for assignment. Give the subscription time to run and the SCSM connector time to run. Usually, if the connector is running every 2 minutes, it takes the total process about 5 minutes to complete. While the actual workflows are running in a second, it simply takes time for both of them to trigger.
Troubleshooting
If there are any issues with the configuration, the event logs will usually tell you about failures. If it is not working, but you don’t see any failures, your criteria probably do not match.
Conclusion
This is a great alternative solution to automatically creating tickets from SCOM. You can still automatically create tickets as well simply by adding subscriptions to the SCSM SCOM Alert connector. If you have any issues, question, leave a comment.
Tuesday, January 15, 2013
Notes Regarding SCSM 2012 Upgrade
I just wanted to share some notes regarding the Service Manager 2012 SP1 Upgrade, that might not be obvious unless you thoroughly read the documentation. I hope these notes help prevent some problems.
Release Notes:
http://technet.microsoft.com/en-us/library/jj614520.aspx
The SCSM Console New Requirement:
Upgrade Note2-core 2.0 GHz CPU
4 GB of RAM
10 GB of available disk spaces
new requirement of Microsoft SQL Server 2012 Analysis Management Objects (AMO). Microsoft SQL Server 2012 AMO is supported on SQL Server 2008 and SQL Server 2012
Self-Service Portal: Web Content Server with SharePoint Web Parts
8-Core 2.66 GHz CPU
8-core, 64-bit CPU for medium deployments
16 GB of RAM for 20,000 users, 32 GB of RAM for 50,000 users (See the Hardware Performance section in this guide.)
80 GB of available hard disk space
When you upgrade from System Center 2012 – Service Manager, you perform an in-place upgrade of the Self-Service Portal. - This is the only thing the documentation says. I am not sure what it means.
Authoring Tool Workflows
When you use the Service Manager SP1 version of the Authoring tool to create a workflow, then custom scripts using Windows PowerShell cmdlets called by the workflow fail. This is due to a problem in the Service Manager MonitoringHost.exe.config file.
To work around this problem, update the MonitoringHost.exe.config XML file using the following steps.
<?xml version="1.0"?> <configuration> <configSections> <section name="uri" type="System.Configuration.UriSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> </configSections> <uri> <iriParsing enabled="true" /> </uri> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Microsoft.Mom.Modules.DataTypes" publicKeyToken="31bf3856ad364e35" /> <publisherPolicy apply="no" /> <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.EnterpriseManagement.HealthService.Modules.WorkflowFoundation" publicKeyToken="31bf3856ad364e35" /> <publisherPolicy apply="no" /> <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.EnterpriseManagement.Modules.PowerShell" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" /> </dependentAssembly> <publisherPolicy apply="yes" /> <probing privatePath="" /> </assemblyBinding> <gcConcurrent enabled="true" /> </runtime> </configuration>
SCOM Agent Supported in SCSM 2012 SP1
Wednesday, July 11, 2012
SCSM Cube Processing and Analysis Services is a Beast
Back story: I am currently working on a DEV and PRD SCSM 2012 RTM environment for a client. Each environment is up. DEV is being heavily used, but PRD is not. They have slightly different configurations, and each cube processing issue was resolved using two different methods.
Because development is non-impacting, after troubleshooting for a few hours and not being about to resolve the issue, i figured it was best to reinstall the DW. After uninstall, reinstall, and re-sync everything works ALL data intact.
DEV Steps:
- Go into the console > Administration
- Unregister the DW
- On the DW Server, Go to Add/Remove Programs > Uninstall System Center 2012 Service Manager
- If you get an error about a log not being found, do this:
- Shift Right Click "Add/Remove Programs" and select run in a different process
- After the uninstall, restart the machine
- After the machine restarts, go into the registry of the DW Management Server and remove the following keys and all sub keys:
- System Center
- Microsoft Operations Manager
- Restart the Machine again
- Go REMOVE/DELETE the DW databases
- Go REMOVE/DELETE the DW Analysis services database
- On the DW Management Server, perform a fresh install, following the prompts and creating new databases.
- Once the install is complete, re-register SCSM to the DW
- Leave it Alone for 24 hours
- After 24 hours check to see if all the jobs and cubes have processed
|
|
|
|
|
Message : An Exception was
encountered while trying to process a cube. Cube Name:
SystemCenterChangeAndActivityManagementCube Exception Message: An exception
occurred while processing the cube. Please see the event viewer log for
more information. Cube: SystemCenterChangeAndActivityManagementCube
Stack Trace: at
Microsoft.SystemCenter.Warehouse.Olap.OlapCube.Process(ManagementPackCube
mpCube).
|
Warning
|
7/11/2012
7:53
|
Data Warehouse
|
33573
|
None
|
Message : An Exception was
encountered while trying during cube processing. Message=
Processing warning encountered - Location: , Source: Microsoft SQL Server
2008 R2 Analysis Services Code: 1092550657, Description: Errors in the OLAP
storage engine: The attribute key cannot be found when processing: Table:
'ActivityAssignedToUser', Column: 'ActivityDimKey', Value: '2'. The attribute
is 'ActivityDimKey'..
|
Warning
|
7/11/2012
7:53
|
Data Warehouse
|
33574
|
None
|
Message : Cube Processing workitem
has failed.
This is most likely caused by the DWDataMart (primary datamart) being out of sync from other marts. This is an intermittent problem and will resolve on its own as the Load jobs complete their runs. However, to work around this issue, administrators can manually start the Load.Common load job, wait for it to complete and then start the Cube processing job. |
Error
|
7/11/2012
7:53
|
Data Warehouse
|
33573
|
None
|
Message : An Exception was
encountered while trying during cube processing. Message= Processing
error encountered - Location: , Source: Microsoft SQL Server 2008 R2 Analysis
Services Code: -1054932986, Description: Errors in the OLAP storage engine:
The process operation ended because the number of errors encountered during
processing reached the defined limit of allowable errors for the
operation.. Processing error encountered
- Location: , Source: Microsoft SQL Server 2008 R2 Analysis Services Code:
-1054932978, Description: Errors in the OLAP storage engine: An error
occurred while processing the 'ActivityAssignedToUser' partition of the
'ActivityAssignedToUser' measure group for the
'SystemCenterChangeAndActivityManagementCube' cube from the DWASDataBase
database.. Processing error encountered -
Location: , Source: Microsoft SQL Server 2008 R2 Analysis Services Code:
-1054932986, Description: Errors in the OLAP storage engine: The process
operation ended because the number of errors encountered during processing
reached the defined limit of allowable errors for the operation..
Processing error encountered - Location: , Source: Microsoft SQL Server 2008
R2 Analysis Services Code: -1056964601, Description: Internal error: The
operation terminated unsuccessfully..
Processing error encountered - Location: , Source: Microsoft SQL Server 2008
R2 Analysis Services Code: -1055129598, Description: Server: The operation
has been cancelled..
|