How to image devices with a LANDESK Agent installed

Posted onAuthorMrNetTek

email me

Issue

Imaging a device with a LANDESK Management Agent installed can cause the devices that receive the image to overwrite each other in the database.

 

Cause

LANDESK inventory looks at a Unique ID/Device ID when inserting the scan. This ID is created when the agent installed on the device.

 

Resolution

Important: It is strongly recommended that the LANDESK agent not be included in an image.  The recommended way to install the LANDESK Agent with imaging is to use LANDesk Provisioning and include a Configure Agent action in your provisioning template.  Besides causing duplicate devices, the LANDESK agent is often updated and adding it to the image will quickly cause your image to be outdated.

If the agent must be included in an image or Non-Persistent VDI image, the unique identifiers must be deleted out of the registry prior to the capture of the image.  Before creating an image of the machine do the following:

LANDesk Management Suite 9.0 and later

  1. Install the LANDESK agent, then STOP all LANDESK related services
  2. Delete the following Registry Keys for 32 bit clients:

HKLM\SOFTWARE\Intel\LANDesk\Common Api\UniqueID
          HKLM\SOFTWARE\LANDesk\Common Api\UniqueID

          HKLM\SOFTWARE\LANDesk\Inventory\LogonHistory\Logons
          HKLM\SOFTWARE\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents

         

Delete the following Registry Keys for 64 bit clients:

HKLM\SOFTWARE\Wow6432Node\Intel\LANDesk\Common Api\UniqueID

          HKLM\SOFTWARE\Wow6432Node\LANDesk\Common Api\UniqueID

          HKLM\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory\Logons

          HKLM\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents

 

3. On Windows XP delete C:\Documents and Settings\All Users\Application Data\LANDESK (delete the entire directory and subdirectories)

4. On Windows 7, 8, and 8.1 delete C:\ProgramData\LANDesk (delete the entire directory and subdirectories)

5. From the command line (as administrator) in the \LDCLIENT directory run the following

“clientdbutil.exe /create”

6. Verify that a new database, (LDClientDB.db3) was created in the same path as you deleted above

 

Reference

https://community.landesk.com/support/docs/DOC-1688

In addition, it is a good practice to ensure that the image does not contain any DRIVERS.DB3 file.