DonC72

I hear that. So, yea, the SQL fix will absolultely not work for us. I'd wish it would be added as a simple right click menu, but no go. So, I had to redo all switch names and interfaces, as that does not work either. Very annoying that the work around has to be a home grown and not company provided.

Are you speaking of this fix? Changes to interface names are now correctly discovered by web node management. I will certainly test it. I am guessing this means that via the web interface, do we rediscover or poll a device for this to be fixed? We're not only renaming all devices, but setting up advanced alerts via key…

Thanks, I will give it a try.

Thanks. I am still holding off. I was reading thru the SP4 release hoping it would be addressed, and still not. I hate losing the data, but we are just rediscovering everything that we change. I can't beleive something like this is not important enough to have made it to a service pack. I'd much rather right click and…

Yes, that would be very helpful, I just took at look thru our custom property editor, and a rather large amount of the names do pull the domain name, which would further complicate this. As a side, is it possible to test it on a select few first as opposed to popping that in there and doing everything in one fell swoop? 

I'm not much of an SQL whiz. Is this pretty straightforward? On a scale from 1-5, 5 being most knowledgeable, I'd be a -1 regarding SQL "how to"

Hello. Has any ground been made on this? I'm at the point where I have to basically delete all "old" nodes with the old nomenclature and have to rediscover them, which wipes out all reporting and historical data. I know I can easily rename the nodes via Atlas, but that will lead to confusion with reporting, won't it?…

Thanks! I did see that earlier, but was hoping it was fixed in the latest version. I did open a ticket a while back and beleive it was closed as I am fairly certain that it was supposed to be in this version per the notes. I'd rather not have to do the queries, but can as a last resort. Thanks

I figured out the alert condition to send an email. Is there a way to create a report with this so I can have it show up on the page with possibly a reason why it is unmanaged? That would be top notch.

Excellent, thank you! How would one be notified? 

Thanks ! That was going to be the follow up. I can easily customize the bar to display nothing, which would work. I guess now I just have to find a large North America map similar to the one that comes with Atlas. Are there any public domain maps available? When I resize it, the icons look quite bad, they don't really…

It has never worked for us. Typical scenario.... NPM has device XYZ NCM has device XYZ Map has YXZ. Business says to change the name to abc. Delete XYZ Node from NPM Delete XYZ node from NCM Run Orion Import to NCM to import device ABC Delete XYZ Node from map Refresh Atlast Map Maker Add new ABC device Redraw all of the…

Where is the customer portal? And I am definitely going to try the above workaround. Wish me luck.

Thanks! That's perfect. We already had step 1-3 already defined for all of our nodes, this works like a charm. Pretty simple, too.

I had to do the same for our MPLS rollouts & renames - I had to remove the old and rediscover unfortunately. I'll be following this one. I have many more to do, hopefully there is a way. 

Good question, I am wondering the same thing. For those that know, is it possible to have these devices listed on a page and/or have an email sent out to folks letting them know that xyz has been unmanaged?

Great feature idea.