LANDESK Service Desk
This document shows you how to set up AMS integration with LANDESK Service Desk.
The Arellia Management Server (AMS) integrates with LANDESK Service Desk to create tickets for application elevation requests received via Arellia Application Control policies. These tickets can then be approved or denied directly from the LANDESK Service Desk.
This integration requires Application Control Solution 8.0 or greater.
To set up the AMS integration with LANDESK, do the following steps:
LANDESK Service Desk Configuration
Verify User Credentials
To verify user credential, do the following steps:
- Contact Arellia support for the latest Design Transfer XML to import into Service Desk.
- In the Security Manager Console and click the Configuration tab.
- Navigate to Settings > Foreign Software Systems > UserCredentials.
- Verify that the Default User Credential has access to the LANDESK Service Desk, or create a new credential that has access.
- Navigate to Settings > Foreign Software Systems > Foreign Software System Types > LANDesk Service Desk.
- Right-click LANDesk Service Desk and then click New > New LANDesk Service Desk Instance.
- Enter a Name and Base Uri of the Service Desk Instance.
- Click OK.
- Click the User Credential you configured in step four.
Approval Process
Create an approval process by doing the following steps:
- Click the Tasks tab.
- In the file library at the bottom of the left pane, click Workflow.
- Navigate to Automation >Approvals.
- Right-click Approval Processes and then click New > Approval Process > LANDesk Service Desk Approval Process.
- Enter a Name and Description for the new approval process.
- In the right pane under Settings, select the new LANDesk Service Desk Instance.
- Configure the newly created approval process to use the AMS Request Process and AMS Request Template credential.
- You have the option to change how often ticket status is checked by changing the time interval next to Check request status every.
- Click Save.
Approval Type
Create an approval type by doing the following steps:
- In the file library in the left pane, right-click the Approval Types folder and then click New > Execute Application Approval Request.
- In the Create Item dialog box, enter a Name and Description.
- Click OK.
- In the right pane under Settings > Options, select as the Process handler the approval process you created previously, LANDesk Service Desk Approval Process.
- Select the Policy specific and File specific check boxes.
Clone a Policy
To clone a policy for the LANDESK Approval action, do the following steps:
- Click the Policies tab.
- In the file library in the left pane, navigate to Policies > Arellia Solutions > Application Control > Actions > Messages > Advanced
- Right-click on Approval Request Form Action and select clone.
- In the Clone Item dialog box, change the name to LANDesk Approval Request Form Action.
- In the right pane under Settings, select as the Approval type the approval type you created previously, LANDesk Service Desk Execute Application Request Type.
- Save the action.
You can now use the new message as an application action that will collect requests from end-users and send them automatically to LANDESK Service Desk.
LANDESK Service Desk Configuration
When requesting approval, AMS creates a new service request using a template and lifecycle process. The template and process are business-specific, but there are some standard attributes that AMS will supply if present in the request so the approver understands what is being requested.
Name | Type | Description |
AmsApprovalId | String (38) | The ID of the AMS approval record. |
AmsInitiatorId | String(38) | The ID of the user or entity that initiated the request. |
AmsInitiatorName | String(255) | The name of the user or entity that initiated the request. |
AmsPolicyId | String (38) | The ID of the AMS policy from which the request originated. |
AmsPolicyName | String (255) | The name of the AMS policy from which the request originated. |
AmsAgentId | String(38) | The ID of the AMS agent from which the request originated. |
AmsAgentName | String (255) | The name of the AMS agent from which the request originated. |
AmsProcessId | String (38) | The ID of the AMS approval process from which the request originated. |
AmsProcessName | String (255) | The name of the AMS approval process from which the request originated. |
AmsFilePath | String (-1) | The path of the file the user attempted to execute. |
AmsUserReason | String (-1) | The reason given by the user for the request. |