1 Reply Latest reply on Sep 26, 2011 2:32 PM by JSMCPN

    Clone server with agent installed

    Rookie

      After the clone and server rename, the agent appears to be still registered under the old server name

       

      Is there an easy way to fix this without removing the agent and re-installing it.

        • 1. Re: Clone server with agent installed
          JSMCPN Expert

          Hi Dale :)

           

          First, while technically possible, it is not best practice to include a LANDesk Agent in a source image.

          The three main reasons are:

           

          1 - Each LANDesk Agent installation has a GUID assigned to it in order to distinguish it from other devices.  If you clone a device with LANDesk installed, the clone will have the same LANDesk Unique ID as the source machine.

           

          2 - If you have a LANDesk Management Gateway, the SSL certificate that allows a device to communicate through the Gateway is unique to each LANDesk Agent installation.  If you clone a device with a Gateway SLL certificate installed, that certificate will be a duplicate of the source and cause problems for both devices.

           

          3 - Once the source image is captured, the Agent inside it will become outdated the next time a change is made to the Agent configuration on the Core server, such as changing a setting or installing a patch or Service Pack.  The result over time is the need to reinstall the latest Agent on the clone.  This kind of defeats the purpose of putting the Agent in the source image in the first place if you have to reinstall it after cloning!

           

           

          If you really need the Agent installed on a source image, before cloning the source, you have to make absolutely sure that the following registry keys have empty values.  Be sure to stop the "Intel Local Scheduler Service" before clearing the keys to make sure they don't come right back:

           

          32-bit computer:

           

          "HKEY_LOCAL_MACHINE\Software\Intel\LANDesk\Common Api" - contains a REG_BINARY value called "UniqueID"

          "HKEY_LOCAL_MACHINE\Software\LANDesk\Common Api"  - "UniqueID" exists here too

           

          64-bit computer - also check:

           

          "HKEY_LOCAL_MACHINE\Software\Wow6432Node\Intel\LANDesk\Common Api"

          "HKEY_LOCAL_MACHINE\Software\Wow6432Node\LANDesk\Common Api"

           

          The "UniqueID" value must be empty for all instances in the Registry.  When blank, a new GUID will be created when the Inventory Scanner runs for the first time on the clone.

           

          In addition, if there is a Management Gateway in your environment, you need to delete the unique Gateway Certificate files from the source image:

           

          C:\Program Files\LANDesk\Shared Files\cbaroot\broker\broker.*

           

          The problem here is that Gateway Certificates do not auto-regenerate like the UniqueID does, so neither the source nor the clone will have a Gateway Certificate like they normally should.

           

          However, because you are cloning a Server rather than a Workstation, the lack of a Gateway Certificate will not be a problem if the clones are always on a local network that can talk to the Core without going through the Gateway.

           

          Having said that, it's still better to clone a device without LANDesk installed, no LANDesk UniqueIDs in the registry, and then install the Agent AFTER the clone boots up.