2 of 2 people found this helpful
Agent IDs are assigned sequentially, and an Agent gets an ID on its first connection to the LEM appliance. This ID is encoded in the certificates that the Agent gets on first run, so if you're getting duplicates that would suggest that the Agent install folder was copied to multiple machines (perhaps VDIs?)
We have directions on using LEM agents in a Windows Image, so you may need to look at that and resolve the duplicate agents by resetting Agents to a "first run" state by deleting their certs.
Directions on resetting agents, you may need to look in SysWOW64 instead of System32 on new systems (section "Reset the LEM Agent Certificate"): Troubleshoot LEM agent connections
Using the LEM Agent in a Windows image: Include the LEM Agent in a Windows image - SolarWinds Worldwide, LLC. Help and Support
Thank You Curtisi;
The folks that deployed the VDI desktops found something was not happening due to a script being blocked at user logoff which did not clean the certs before the system was cloned for the next user.
We did have knowledge of the include Agent in a Windows image doc.
I was just reading something interesting about the VMWare InstantClones.
The following is from vmware-horizon-view-instant-clone-technology.pdf
Master VM: The VM that you create and configure as the model for the virtual desktops you plan to
Master VM snapshot: A reproduction of a master VM exactly as it was when you took the snapshot. The snapshot
includes the state of the data on all VM disks.
Internal template VM: A linked clone of the master VM, based on the master VM snapshot. This VM is used for the
AD domain join.
Replica VM: A thin-provisioned full clone of the internal template VM. The View Storage Accelerator
feature uses a content-based read cache digest of this VM.
Running parent VM: A linked clone of the replica VM, based on a snapshot the system takes of the replica VM.
Instant clone: A desktop VM created from the memory and disk of the running parent VM. After the instant
clone is created, it shares the read disks of the replica VM, exactly like a linked clone.
I'm wondering if the root problem here is the instant clone is created from the Running Parent VM. ie. The spop folder not being deleted like when you prepare a Master Image.
Just trying to keep you posted.
1 of 1 people found this helpful
If the master image has a populated contegospop\spop folder, that will cause problems when it's cloned to make a new VDI.
Because the VMs were off of a "running parent VM", I had the desktop team install the agent clear the spop folder and leave the agent in a manual start, after the clone process finishes and the VM starts, The Ad team created a GPO to start the service. All looking good here.
Thanks for keeping us straight.
We had similar issues with agents and come to the same conclusion, we then had a different issue with the amount of dhcp addresses we use, essentially our users are quite mobile within our networks and its not unusual to see the same machine with 3 or 4 ip addresses in a day depending on which VLAN they are connected to
I think the agent should only use the ID and certificate to authenticate itself with maybe an approval button on the console, after that the agent should not take the IP address into account for authentication
we have managed a work around however we cant use licence recycling now and have to manage licences manually which is a burden
That could be useful to modify the agent for really busy VDI environments. You should put that in as a Feature Request.