1 Reply Latest reply on Jul 7, 2015 5:21 PM by nicole pauls

    LEM creates duplicates of provisioned XenApp servers as they are created

    calibretto23

      We currently use non-persistent provisioned XenApp servers that build off of a single image so that we can spin up servers as needed. We followed the procedure to delete the certificate data as suggested in a previous question but are now seeing the server duplicate daily whenever they connect rather than reconnecting as the previously used entry. This makes a daily chore of cleaning up the prior nodes that are disconnected. Is there anyway to help LEM attempt to identify the agents via another means like system name or another identifier?

        • Re: LEM creates duplicates of provisioned XenApp servers as they are created
          nicole pauls

          One approach is to use LEM's automatic recycling mechanism to cycle out those old nodes that haven't connected in a long time. We built this to help people in VDI environments automatically delete dynamically provisioned systems.

           

          Manage > Appliances > Properties

          LicenseRecycling.PNG

           

          An agent node will only "reconnect" to a previous agent's connection if the certificates match, otherwise it's considered a new node and there's not really a way to work around it. You could offload the certs as a part of de-provisioning and copy them back as a part of re-provisioning with some scripts, but that's about all I can come up with.