I am in an organization where it is very commonplace that computer names get reused. As an example, a computer may get imaged and issued out as Computer 01. A year down the line it may get retired. A different system gets imaged and sent out as Computer01 (if the name is available). This is not ideal, which I understand, but it was the documented process for our organization before I came on-board. Since the new 6.0 upgrade now prevents you from using the same computer name in Assets, I'm wondering how people in similar situations are dealing with this. Am I looking at trying to force a process change? I would much rather use unique computer names that don't get reused.

Interested in hearing any ideas or changes that could help me. Thank you
Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment


Upgrade to version 6.2 that was just released and it will allow you to have duplicate assets again.
Answered 10/09/2014 by: h2opolo25
Red Belt

  • Is there anything official that states that 6.2 corrects the issue? I didn't see it in the 6.2 release notes. Or did you notice that it was fixed after your own upgrade to 6.2?
    • I believe it did state somewhere in there that it was fixed. Before I wrote the above comment I double checked it by creating an asset that had the same name as an existing asset and it worked. I remember it did not work when I was on 6.0
      • You're absolutely right. "K1-16557 Do not require asset names to be unique". Thank you for pointing that out to me. We'll schedule an upgrade window for 6.2 to correct the issue
Please log in to comment
Answer this question or Comment on this question for clarity