Skip navigation
The purpose of this article is to cover configuring LANDesk® track on courier Service Desk with LDMS (LANDesk Management Suite) integration. The steps below will allow an analyst to access imported devices from within Service Desk and perform LANDesk Management Suite functions such as remote control, inventory, deploy software etc...
All of the Touchpaper.Framework.Web frameworks will need to have the appropriate patch applied if applicable. The IIS application pool will need to be setup to allow 32 bit applications if using a version of LDMS earlier than LDMS 9.0 SP2.
Installing the LDMS Remote Console
The LANDesk Remote console will need to be installed on every analyst machine and on the Service Desk server that has the Data Import service installed (Usually the Application Server). Steps for installing the LANDesk Remote Console:
DOC-1001
Note: Before creating the import mapping, attributes for each item added will first need to be created in Service Desk Object Designer. See the section "Creating LANDesk attributes in Service Desk" for creating these attributes.
Its a good idea to create a new Service Desk query to show what devices are going to be imported. This is also a good troubleshooting test to make sure that you are able to connect to the LDMS database from Service Desk.
Note: Additional step is required for LDSD 7.4 with LDMS 9.0 SP2
9.Leave the other values as default.
Note: Attributes track on courier names may be different; I chose to map Computer.ID to ID in Service Desk to be consistent on the name. This attribute track on courier will be used when setting up the connection type later in this article.
5.Save Window.
5.For the source select LDMS Connection under the Module and Computers for the Business Object. (This is the name of the data connection created in the previous steps and the data connection type name)
Video:
5.In the action pane, click Import Data Mapped. (This will manually start the import)
track on courier
The LANDesk Desktop Manager track on courier connection is needed to communicate with LDMS. This is different from creating a connection using Data Connections, which was created to import information from the LDMS data source. The following steps will walk you through setting up the connection and also defining the default path for the LDMS Console.
For LDSD 7.3.2 and previous versions there is only one installation path. track on courier Please note that all remote consoles will need to be installed to the same path for LDMS integration to work as you are limited to one installation path.
Management Gateway = Fill this in with the name of the LDMS Gateway if analysts will need to connect to machines outside your network through the gateway.
Before you can use your desktop management functions, you must first set up how Service Desk identifies the specific remote object that you want to manage on the connection that you have set up. You do this by selecting the business object from which you will use Desktop Integration, then specifying the attribute that contains the unique identifier for the remote objects that you want to manage. Service Desk will use this unique identifier to search for a match on your LDMS system. If a match is made, you can then connect to that remote object.
2.Traverse track on courier the business object tree to the Service Desk object that the devices were imported. This article walks through creating imports for Workstations so the path would be Business Objects | Configuration management | Configuration Item | Workstation
2.Go to Designers | Window Manager
1.Log track on courier into the console with a user that has Administrative privileges.
7.Click OK
Direct lookup from external data sources If you would like an attribute added to the incident window that is a direct lookup to the LDMS Database track on courier to pull a list of devices, then follow the steps below.
11.Save window. For addtional information on this please see the LDSDDesigner.pdf guide.
"Could not connect to LanDesk Database" track on courier error with integration to LDMS 9 SP2 onwards Re: Need help linking LDSD 7.4 with LDMS 9sp2 Re: Service Desk Integration with LDMS Re: Associating CI's with a User Re: LDMS Integration to Desktop Manager
LDMS Console patching for integration Service Desk and LDMS Integration Compatibility Matrix Cannot import from LDMS 9.5 with Service Desk 7.6 Management Suite 9.5 Integration Patch for Service Desk 7.4, 7.5, and 7.5 SP1 LANDesk Management Suite 9 Integration Patches for Service Desk 7.3.1, 7.3.2 and 7.4
View Stu McNeill's profile LANDesk Community powered by Jive SBS 4.5.7.1 | Legal Notices | Privacy Policy | On Twitter | On Facebook 2007 - 2013 LANDesk Software
The purpose of this article is to cover configuring LANDesk® track on courier Service Desk with LDMS (LANDesk Management Suite) integration. The steps below will allow an analyst to access imported devices from within Service Desk and perform LANDesk Management Suite functions such as remote control, inventory, deploy software etc...
All of the Touchpaper.Framework.Web frameworks will need to have the appropriate patch applied if applicable. The IIS application pool will need to be setup to allow 32 bit applications if using a version of LDMS earlier than LDMS 9.0 SP2.
Installing the LDMS Remote Console
The LANDesk Remote console will need to be installed on every analyst machine and on the Service Desk server that has the Data Import service installed (Usually the Application Server). Steps for installing the LANDesk Remote Console:
DOC-1001
Note: Before creating the import mapping, attributes for each item added will first need to be created in Service Desk Object Designer. See the section "Creating LANDesk attributes in Service Desk" for creating these attributes.
Its a good idea to create a new Service Desk query to show what devices are going to be imported. This is also a good troubleshooting test to make sure that you are able to connect to the LDMS database from Service Desk.
Note: Additional step is required for LDSD 7.4 with LDMS 9.0 SP2
9.Leave the other values as default.
Note: Attributes track on courier names may be different; I chose to map Computer.ID to ID in Service Desk to be consistent on the name. This attribute track on courier will be used when setting up the connection type later in this article.
5.Save Window.
5.For the source select LDMS Connection under the Module and Computers for the Business Object. (This is the name of the data connection created in the previous steps and the data connection type name)
Video:
5.In the action pane, click Import Data Mapped. (This will manually start the import)
track on courier
The LANDesk Desktop Manager track on courier connection is needed to communicate with LDMS. This is different from creating a connection using Data Connections, which was created to import information from the LDMS data source. The following steps will walk you through setting up the connection and also defining the default path for the LDMS Console.
For LDSD 7.3.2 and previous versions there is only one installation path. track on courier Please note that all remote consoles will need to be installed to the same path for LDMS integration to work as you are limited to one installation path.
Management Gateway = Fill this in with the name of the LDMS Gateway if analysts will need to connect to machines outside your network through the gateway.
Before you can use your desktop management functions, you must first set up how Service Desk identifies the specific remote object that you want to manage on the connection that you have set up. You do this by selecting the business object from which you will use Desktop Integration, then specifying the attribute that contains the unique identifier for the remote objects that you want to manage. Service Desk will use this unique identifier to search for a match on your LDMS system. If a match is made, you can then connect to that remote object.
2.Traverse track on courier the business object tree to the Service Desk object that the devices were imported. This article walks through creating imports for Workstations so the path would be Business Objects | Configuration management | Configuration Item | Workstation
2.Go to Designers | Window Manager
1.Log track on courier into the console with a user that has Administrative privileges.
7.Click OK
Direct lookup from external data sources If you would like an attribute added to the incident window that is a direct lookup to the LDMS Database track on courier to pull a list of devices, then follow the steps below.
11.Save window. For addtional information on this please see the LDSDDesigner.pdf guide.
"Could not connect to LanDesk Database" track on courier error with integration to LDMS 9 SP2 onwards Re: Need help linking LDSD 7.4 with LDMS 9sp2 Re: Service Desk Integration with LDMS Re: Associating CI's with a User Re: LDMS Integration to Desktop Manager
LDMS Console patching for integration Service Desk and LDMS Integration Compatibility Matrix Cannot import from LDMS 9.5 with Service Desk 7.6 Management Suite 9.5 Integration Patch for Service Desk 7.4, 7.5, and 7.5 SP1 LANDesk Management Suite 9 Integration Patches for Service Desk 7.3.1, 7.3.2 and 7.4
View Stu McNeill's profile LANDesk Community powered by Jive SBS 4.5.7.1 | Legal Notices | Privacy Policy | On Twitter | On Facebook 2007 - 2013 LANDesk Software
No comments:
Post a Comment