The steps of the Woodgrove Bank customization scenario are as follows. Details about each of those steps are provided in subsequent topics.
Step 1: Open the Woodgrove.AutomatedActivity.AddComputerToADGroupMP Management Pack
Ken has to create a class and a form. He starts by opening the Woodgrove.AutomatedActivity.AddComputerToADGroupMP management pack that contains the definitions for the following class and form:
- The Automated Activity: Add Computer To AD
Group custom class that represents the new automatic activity.
This activity adds a new computer to a specified Active Directory
Domain Services (AD DS) group.
- The form that represents the Automated
Activity: Add Computer To AD Group class and that lets Ken
enter information about the computer that is being added and the AD
DS group to which the computer should be added.
You can import this management pack as part of the Woodgrove Bank customization scenario.
For more information about how to open the management pack, see Step 1: Open the Woodgrove.AutomatedActivity.AddComputerToADGroupMP Management Pack.
Step 2: Customize the Default Change Request Form
Often, customers want to adapt default forms to their organizations’ preferences. In this scenario, Ken adds an image that represents the company logo to the default change request form and then rearranges the layout of the fields on the form.
For more information about how to customize the default change request form, see Step 2: Customize the Default Change Request Form.
Step 3: Create the Workflow Rule and the WF Workflow
Ken creates the AddComputerToADGroupRule workflow that automatically adds the specified computer to the specified AD DS group after the compliance change request is approved.
For more information about how to create the workflow rule and the Workflow Foundation (WF) Workflow, see Step 3: Create the WF Workflow.
Step 4: Move the Assembly Files to the Service Manager Console
Ken moves the workflow assembly file and the form assembly file to the Service Manager Program folder.
For more information about how to move the assembly files to the Service Manager console, see Step 4: Move the Assembly Files to the Service Manager Console.
Step 5: Edit, Bundle, and Import the Custom Management Pack to Service Manager
Ken edits the custom management pack file to define the criteria that controls when the workflow runs. Then, he has to bundle and import the custom management pack.
For more information about how to edit, bundle, and import the custom management pack to Service Manager, see Step 5: Bundle and Import the Custom Management Pack to Service Manager.
Step 6: Extend the Change Area Enumeration List
Ken adds the new Compliance list item that represents the new type of change request.
For more information about how to extend the change area enumeration list, see Step 6: Extend the Change Area Enumeration List.
Step 7: Create a New Task
Ken creates the Start AD Users and Computers task that starts the AD Users and Computers administration tool from the Service Manager console. Ken can conveniently monitor the Active Directory group to which the new computer is being added.
For more information about how to create a new task, see Step 7: Create a New Task.
Step 8: Create a New View
Ken creates the Compliance Change Requests view, which displays change requests of the new type. This includes all change requests in which Area = Compliance.
For more information about how to create a new view, see Step 8: Create a New View.
Step 9: Create a New Change Request Template
Create a new Apply AppLocker Software Policy to Computer change request template for the new compliance change request type.
For more information about how to create a new change request template, see Step 9: Create a New Change Request Template .
Step 10: Create a Notification Template and Subscription (Optional)
Ken creates the Computer was added to AppLocker Policy Group notification subscription that sends an e-mail notification message to Ken when the status of an Automated Activity: Add Computer To AD Group activity is updated. This message notifies Ken that the workflow process is completed.
For more information about how to create a notification template and subscription (optional), see Step 10: Create a Notification Template and Subscription (Optional).
Step 11: Use the New Compliance Change Request Process
To test the new process, Ken creates a new compliance change request to add the ADComputer1 computer to the GP_AUTHAPPS group. Next, he submits and approves the new change request. Finally, Ken verifies in Active Directory Domain Services that the new computer has been added to the appropriate Active Directory group.
For more information about how to use the new compliance change request process, see Step 11: Use the New Compliance Change Request Process.
|The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.|