Change Autodiscover Friendly Name Generation
candidate for implementing
J
Jason Mainwaring
When you install the Agent software the Autodiscover looks up/generates initial Inspectors using the Hostname of the Server, this sometimes conflicts if you have multiple customers with the same server name i.e. DC01It might be beneficial to prefix the Autodiscover Inspector names with the "Roar Agent Name" which I believe needs to be unique
Merged in a post:
Duplicate Friendly Names on Agents/Inspectors
K
Kevin Fuller
Several of our clients have the same server names. It would be great if we could have a way to detect if this server name is a duplicate to avoid any failure or allow duplicate server names.
C
Carl Schneider
Creating a naming template for different types of discovered assets would be fantastic. For network equipment, we do: [Manufacturer] - [Site In Manage] - [Friendly Name]Being able to automate this would be great.
S
Sruli Wolff
Thanks Jason!The main issue here is the fact that if a duplicate exists, it just skips the discovery and you don't know anything about it until you start realising that inspectors are missing, at which point you need to look in the logs, etc...Two quick fixes I can think of for this:Allow the duplicates to show in the discoveries but not allow them to be 'added' until they are renamed to something unique.Do like windows does with duplicate file names, just auto-add a (1) to the end, etc... and let the user rename it themselves later.Either way, it needs more visibility to better enhance your auto-discover feature as that is one of the best sellers. Being told that the autodiscover does xyz....., and then having to add lots of your active-directory inspectors manually since a bunch of your clients main DC's are named DC1, is not a great start to trying to get the MSP to stay.