We may use ILM2 to import user information from customer AD and then populate to HP service desk so that helpdesk staff will know where is the end user,OU,contact number,etc , for further helpdesk service. So can ILM2 export user data from AD to HP service desk? I heard HP service desk is not in the supported list? Any walk arround? One I can think is to use csv file... advice? If export to csv for service desk to use, does it mean HP SD and ILM will both keep a copy of the users full profile information?

CSV file is an option.You could also develop an ECMA - it is not really hard: Developing a File-Based Import Management Agent Developing a Call-Based Export Management Agent Developing a File-Based Export Management Agent Cheers,MarkusMarkus Vilcinskas, Technical Content Developer, Microsoft Corporation

Alternative:HP service desk, can be set-up to use AD as LDAP store nativelyand import all info from AD. In the LDAP connection you can define which attributes should be imported and linked towards an ServiceDesk account. If you also set the parameter "ldapnostrictlogin" you can have LDAP based accounts next internal HP Service desk accounts.snippet from the helpfile of Service Desk: Lightweight Directory Access Protocol (LDAP) You can integrate HP Service Manager to an LDAP directory service to share contact information across your network. Once you have enabled an LDAP integration to HP Service Manager, you can then configure HP Service Manager to automatically create operator records for LDAP users by either of the following methods: Defining a user template for LDAP log ins Defining a system default record for all log ins Using either method, you can map fields in the operator record to contact information in the LDAP directory service. This mapping allows HP Service Manager to create an operator record with all the available contact details defined in the LDAP directory service. If you create an LDAP user template, you can make changes to all users built from this template by editing the template operator record. If you create a system default record, then you must manually make changes to each individual operator record that HP Service Manager creates. If you create both an operator template and a system default operator record, HP Service Manager uses the operator template to create new operator records. Note: After you have mapped fields in an operator record to a LDAP directory service, only users who are both LDAP administrators and HP Service Manager system administrators can update and add new operator records. HP Service Manager applies this restriction because HP Service Manager synchronizes any changes you make to the operator record with the corresponding LDAP entry. In addition, if you create new operator records, then HP Service Manager also creates new users in the LDAP directory. Note: Typically, HP Service Manager system administrators will want to map only the operators file to an LDAP directory, however they can also map any other system table, for example, the contacts or device table, to an LDAP directory. You can map a HP Service Manager table to only one LDAP server at a time, although you may specify a different LDAP server for each table. When mapping between HP Service Manager and LDAP directories, you can decide which data source you want to be primary. In cases where there are duplicate entries between data sources, HP Service Manager displays only the data listed in the primary data source." Cheers,Frank. Kind Regards, Frank van Rijt Deleting an operator record does not cause HP Service Manager to delete LDAP users. Only an LDAP administrator can delete LDAP entries. HP Service Manager denies access to LDAP users unless the system administrator defines either an operator template or a system default operator record.