Do you also have the "Automatic Update Device Name" selected in connection management under System Variables?
Steven R. Gibbs
Sr. Systems Consultant
We have already enabled "Automatic Update Device Name" in connection management under System Variables but still new device name is reflecting with TEST (1) even after deleting old device TEST.
Any solution on this?
I don't know of any other method that will automatically update the Name of the device if it once had a duplicate and the name has a (1) or (2) behind the name. The only way to update the name would be to manually change the name by removing the appended nomenclature.
Are you capturing any Financial information where it would be more appropriate to "Merge" the two records together to retain the data from the original record?
I guess the big question is "WHY" do these records require reaming? Is the agent getting installed prior to the final name being applied so the GUID created would be different than the one that would be created if the name was the same as the one prior to being re-imaged?
If the GUID was originally created using a device name of "PC1' and then the agent got installed again on a fresh build while the name is "newPC1"... then the GUID would be different and a new record would be created vs. the device taking over the same record as "PC1". If the agent get installed or reinstalled when the device names where the exact same, then no duplicates are created.
What would happen if you re-install the agent AFTER you name the device back to the name it once had? Will two records still exist? What happens if you modify the Identity.ini file and make 2 changes:
Remove the "values" after the "Last Identity Sent=" (get rid of all the numbers after the "=" sign)
Remove the line almost at the bottom of the file "GUID=00010088EE12006ABCFD444F77FE1989EFB4" (Typically 3rd line from the bottom - Delete entire row)
Capture the old GUID and Compare to the NEW GUID to see if GUID actually changed.
I would also recommend a review of your process low. Maybe you should "Deprecate" the device you are re-imaging prior to reinstalling the new agent on the fresh build. This will then automatically rename the deprecated device record to append the name to (0)… The new device shouldn't have the (1) at the end...
Contact support and see if they have a better solution for you that won't require too much effort on your part.
Good luck and let us know what you end up doing.
Bonjour Steve and Vipul,
If you have any 'automated' way to do that (auto mergin device) I would love to have it
I just have 420 devices in that state
As I mentioned before, you would be best served to contact support to identify root cause and see if they have an "automated" process to correct these devices to merge the data. I do not have any other answers for you at this time.
You are looking for an option to automatically remove the (1) from the device name or to automatically fusion the device with (1) and the device without (1)?
I know the root cause and I can not do anything for
first cause: integration of the device in the AD it cause the 'Domain name' change
second cause: the upgrade from WIn 7 to Win 10 or re-imaging same device
I can not do anything, because I do not have any power to obligate the 50 to 70 persons in our premises the change theire way of doing things