Use Orchestrator with Service Manager to Disable User Accounts – Part 2

14 Oct

In the previous post I showed you how to create the Orchestrator runbook that actually does the disabling of the user account. In this post I will show you how to use the Service Manager Authoring Tool to create a custom class based off the Service Request class that we will use in Service Manager later to build the templates. Remember that this step is optional as you do not need to have a custom class and could use the default service request class. The reason I like to use custom classes is because a lot of times you are capturing more input from the user than the default service request class has fields to put that info. With a custom class you can create as many properties as you want and name the properties according to the input capture.

  1. Open the Service Manager 2012 Authoring Tool. If you do not have the Authoring Tool yet it can be downloaded from here.
  2. Create a new Management Pack and call it something that describes the new class that you are going to be creating. For instance I will call mine Disable.User.xml.

  3. Next you need to create a new class. Right click on Classes and click Create other class…

  4. Search for the Service Request class and then click OK.

  5. Give you new class a descriptive name. For instance I will call mine DisableUserClass. Click Create.

  6. By default a new property will be created called Property_35. Scroll to the bottom of the properties and delete this new property.

  7. If you needed custom properties in your new class then you could easily create them here using the Create Property button. You can create several types of properties including strings, DateTime, lists, etc. In this case we do not need any new custom properties because the only input we will require from the user will be a selection of the AD user account to disable. Click Save and to save the management pack. Go back to the Service Manager console and Import the management pack into Service Manager.


    In the next post we will create a runbook template based off the runbook created in Post 1.

One Response to “Use Orchestrator with Service Manager to Disable User Accounts – Part 2”


  1. Use Orchestrator with Service Manager to Disable User Accounts – Part 1 « Travis Marshall's System Center 2012 blog - October 14, 2012

    […] Part 2 – Create new custom Service Request class with custom propertys (This part is optional as this could easily be accomplished using the default Service Request class instead.) […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: