ddevore9

We need this as well. It's been part of server since 2012, I'm really surprised support for this has not been added at some point.

I've got the same concerns. Development of WHD has been very, very slow to say the least. We would be interested in knowing the upgrade path and costs for customers that have up to date paid support with WHD.

Who are you buying renewals from? I just pulled up the customer portal and the 1 year 15 tech license support I'm getting quoted for renewal is $1815. So try the math on the new product with 15 technicians and 25,000 devices (chromebooks, iPads, workstations all included). I get $69 per tech per month for 1 year as 12,420…

Luckily Aruba Airwave has been getting much more powerful over the last few years, the heat maps and switch management works great now. From what I’ve seen with the next major release of Airwave there are some giant improvements. 

We would like to move all of our maps over to SolarWinds from AirWave as well.

This would be a big help in our environment.

Sorry, I was referring to the altered WHD username. I found that if I turn off General - Authentication - Remember Login ID it clears up this issue, now the username field is blank on log off and that works even better for us. Thanks again for all of your assistance with this!! Dennis

That does work, pretty weird though. I noticed when I log off I'm left with the fake username pre-filled in the login screen (I tried chrome, firefox and edge). I really do appreciate you following up with us with this issue. 

Awesome, I appreciate the update! 

Same here. I guess I'd have to put in a request for LDAP authentication to allow technicians to login using their current LDAP credentials instead of having a separate WHD password. I'm hoping someone in the know might chime in with a solution.

Hi Milan, that his how it's currently set. It used to work. As a test I just changed it from Username back to Email address. When it is set as email address my LDAP password works, as soon as I change it back to Username I need to use the locally set password instead of LDAP. Any known way to make the username attribute…

I opened a case with support and was given a very weak answer that offered absolutely no solution. The solutions are to either downgrade (not sure if there are more or less bugs in the last release), and he also put in a feature request since this is not a feature in the product...

Apparently in 12.5.2 this may not be the case. After updating my linked technicians are unable to use their usernames to authenticate using LDAP credentials (tech account is linked to ldap user account). They have to set a password to use that. Unless I'm incorrect we are now unable to authenticate technician usernames…

I really do appreciate that your following up with our questions, if the product will use our client LDAP passwords and remember the tech view we will be good to go. I am on 12.5.1 without the hotfix, if applying the hotfix will fix the logins for linked tech accounts I can apply it this weekend. I just really don't want…

This exactly what we are seeing. How is making out technicians login with a non-ldap password or as a client then switching every time more secure? Pretty much every other service we use manages to securely work using LDAP connections. This leaves more passwords to manage and depends on the users picking a secure password…

I appreciate it, have a nice day!

Agreed. I'm looking into alternative solutions right now, not looking at any alternatives for this by solarwinds. Did the same with dameware.

So I was getting complaints from one tech and one client, I just sat with both to see what was happening. It looks like both were accessing tickets using the client interface, not the tech side. They added a note to the ticket, but clicked save at the bottom without clicking the + button to append the note to the ticket.…

Quick question, currently all of my tech accounts are linked to client accounts. On my own tech account I removed the LDAP authentication and set a password manually. I verified there is a client account associated with my account but now I can't login using my LDAP password. I have not applied this patch yet, will the…

I had the same thing happen. I reached out to support and they knew right away that the version of tomcat in this release has an issue. They sent me instructions to update to the latest version (easy) and it's working like a charm now. Reach out to support to confirm it's the same thing, I'm sure it is. Very random...

It may be related to the bug in this thread RESOLVED having issues after upgrading to 12.5.1 .

I've heard complaints since upgrading this morning that clients and or techs add notes to their tickets and nothing is added to the ticket. I then go back into the same ticket and add a note and it works fine. Has anyone else seen this? Is it possible to roll back without loosing all the new work done by techs today?