Archive | October, 2012

User Orchestrator with Service Manager to Disable User Accounts – Part 3

14 Oct

In Post 1 I showed you how to create a runbook to disable a user account with the only input being the Activity Guid of the runbook in Service Manager. In Post 2 I showed you how to create a new management pack and class in the Authoring Tool. In this post we will create a runbook template in Service Manager 2012 using the runbook from Post 1 and then create a Service Request template based on the custom class from Post 2 containing the new runbook activity template.

  1. If you have configured the Orchestrator connector in Service Manager 2012 then after a synchronization you should see the runbook create from Post 1. Go to Library and then Runbooks to see all runbooks that have been imported.

  2. Click on the DisableUser runbook and then in the Tasks pane click on Create Runbook Automation Activity.
  3. In the next window give your template a descriptive name such as Disable User Runbook Template, leave the class as Runbook Automation Activity and choose the management pack that was created in Post 2. Click OK.

  4. Next the template will pop up. Give it a descriptive title, choose an Area such as Directory\Account Management and a State such as Release. Also it is very important to check the “Is Ready For Automation” checkbox as this will allow the runbook to run automatically without an administrator needing to manually check the box later.

  5. Next click the Runbook tab at the top. You can either edit the mapping for the ActiveGuid on this template or on the Service Request template later. I will go ahead and map it here by clicking Edit Mapping, expand Object and click ID. I cannot map the PortalUser mapping here because it depend on data from the Service Request. Therefore it will be mapped later in the Service Request Template.

  6. Click Close and then OK. At this point your runbook template is complete.
  7. Next we need to create the Service Request template. In the Library section go to Template and click Create Template. Give the template a name such as Disable User Service Request Template. Choose the class from Post 2, when you browse for this class you will need to change the filter to All Basic Classes in order to see the custom class. Be sure to save the template in the new management pack created in Post 2

  8. Next, fill out the fields on the General tab of the template the way you want then to be when new service requests of this class are created.

  9. Next click the Activities tab and add a new activity. Choose the template created earlier in this post. This will bring up the template as shown below.

  10. Click on the Runbook tab of the template. You can now map the PortalUser property mapping because the DisableUserClass is now available to map to. Be sure to map this property to whatever field that you are going to map it to later when creating the request offering. For example, later I will map the portal user to the Notes field of the Service Request so as shown below, I will also map the runbook property to the Notes field of the DisableUserClass.

  11. Click Close and then click OK twice to complete the creation of the template.

In the next post we will create a request offering based off of this service request template. We can then add the request offering to a service offering and publish both to the portal.

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.