cancel
Showing results for 
Search instead for 
Did you mean: 
manishkeshav
Intrepid explorer

How does a FlexNet Agent work if machines are cloned and then renamed

Good day

As we deploy new VM's in a clients environment with the FlexNet Agents as part of the build, IP's and hostnames will be changed.

So, we take 1 image, clone it and then rename the host.

How does the FlexNet Agent pick up the new VM details? Would it be after a re-boot?

regards
Manish

0 Kudos
7 Replies
Highlighted

Re: How does a FlexNet Agent work if machines are cloned and then renamed

As long as the changes were made before the agent runs its scan, I would expect it to pick up those changes, unless a specific change requires a reboot to take effect. The one thing to keep in mind when doing this, is that FNMS will try to match inventory records based on certain criteria. In this regard, if you are not seeing inventory records for cloned devices, they could be merging with another record. All of the logic for matching can be found under the following path on the application server:
%ProgramData%\Flexera Software\Compliance\ImportProcedures\Inventory\Matcher


Flexera dcollins
Flexera

Re: How does a FlexNet Agent work if machines are cloned and then renamed

once the hostname has been successfully changed it should pick it up at the next scheduled time for the agent to generate a ndi (generally every 24 hours, it's defined in the WebUI)

it's worth noting however if your cloning a VM and want it to come in as a separate record you need to change more than just the hostname, from the top of my head it also merges on the domain and serial number.
(the matching logic should match on hostname and domain name if the serial number is not available. )
For more information on the importer matching logic, you can see the 'Common: Resolving Inventory Records' section in the Gathering FlexNet Inventory PDF.
https://www.linkedin.com/in/dave-collins-7aa71a3b
0 Kudos
FrankvH
Active participant

Re: How does a FlexNet Agent work if machines are cloned and then renamed

At this moment we have a support case open that the rename is not reflecting back in FNMS. This is not specific related to cloning but just in general rename of VM or physical server.

We see the agent report back with new name (ndi contains new name) it is updating the device but not the hostname.

I found out be removing the discovered device and inventory the next time the agent reports it has the correct name.

Wait for solution from Flexera.

0 Kudos
Flexera AamerSharif
Flexera

Re: How does a FlexNet Agent work if machines are cloned and then renamed

Hi Manish and Frank,

Do you the version of FNMS in use? FNMS 2018 R1 and earlier used to have a defect (Only impact windows device/s connected to domain) if device is renamed, host name was not getting updated in FNMS but other properties (hardware and software data) were getting updated, even latest inventory file does report new device name. 

FNMS 2018 R2 and later have fix for this issue. 

If my understanding is correct, you can apply the attached SQL fix to inventory database (not compliance database) that will fix the issue.

Note: This fix should not be applied to FNMS 2018 R2 and later versions and applies to On-Prem version only.

Hope this will help.

Aamer