aanthonisse · Technical consultant · ✭✭✭✭✭

I don't know both of them, but Simon looks more interesting as a toy and training device.

The correct answer for today is marked as Wrong

The odds are probably against it, but I go for the Average Joe.

Congratulations to all winners.

Be in five places at once means you have to do 5 times as much work...... ;-)

I agree

Brabanthallen, 's-Hertogenbosch, The Netherlands . Saves me a lot of travel time.

I clicked too soon and punched in the wrong answers... No green board this month for me.

Check this. It might fix your problem. support.solarwinds.com/.../Error-displays-in-the-Web-Help-Desk-Mobile-application

I did not check if I got points for correct answers. Winning one of the prizes is worth more than points :-)

The pots and pans in week 3 would make a good addition the our new kitchen ;-)

I have seen more implementations that make use of AI and ML in the past year. Especially in data analytics for security related services, like XDR.

Logic is the beginning of wisdom.

Another all green month :-)

Congratulations @"jasonstak2079"!

Yes, I am using the internal Postgres 13. You got me thinking though. For Azure hands-on training and WHD testing purposes I might be able to use a Postgres docker in Azure and connect that to a WHD installation on a more recent Linux distro.

The "smart idea" was a colleague who created the hosts file so he could use names in de ldap config instead of ipadresses without documenting that specific piece of information.

After digging a bit further I found out that the public IP address of the LDAPS server that was the first one in the list had changed. This caused WHD to timeout before it could try all other servers in the list. That LDAP server has no public DNS record, so it was an entry in the hosts file of the server that runs WHD. I…

In the log I see this error when I try to logon with a local user: 2024-01-02 13:41:09.279 [https-jsse-nio-443-exec-5] ERROR whd.helpdesk.com.macsdesign.whd.auth - Error while attempting to synchronize user principal <UserPrincipal loginId: XXX isAuthenticated: true password: non-null passwordHash: null> with WHD user…

Hi Phil, Yes, we do. I set the logging to debug and went through the logs. I see ithat WHD tries to access each LDAP server in the configured order. There are a lot of there errors: WARN c.s.w.s.SymetricCryptoManager - Problem while decrypting string: {AES}[snip] with algorythm: AES…

Hi, This sounds as a fun project to do. I have migrated our system from on-premise Windows with an old WHD and PostgreSQL 9 to a Linux server in Azure and the latest WHD and PostgreSQL 13 in one go about a year ago. If I were you I would start with a dump/copy of your existing data in a development environment. The…

It is a great excuse to visit Oktoberfest in Munich, that's for sure.

When creating or updating a ticket, you can use the clientReporter field to assign a client to a ticket. Updating the clientReporter is permitted for tech accounts. I think you should be looking in that direction. The documentation has been updated for the latest version:…

Maybe when onboarding those external users as guest users in the tenant where SSO is configured? If that does not work, you need to setup some sort of directory where all users are synced to from the different sources and set up SSO to that directory.

Thanks, I missed that.

Yes. When I have spare time (duh!), I could test it with an Azure tenant and guest accounts in that tenant. Not a priority, the current setup works.

Just what I had found out then. We would like to be able to do two-factor authentication for the techs, but a lot of normal users login using LDAP from different sources.

Thanks for this information. Is it possible to use LDAP and SAML side-by-side to be allow users who are not in the connected AzureAD tenant to login using their company credentials?

We use WebHelpDesk for our internal servicedesk and some customers have their own tech account. Using the built in rights and division in customers we are able to keep things seperated.

It used to work on our Windows server with WHD 12.7.4. I migrated to a CentOS server with 12.7.9 HF1 and it stopped working. Authentication works, but I keep getting the error Error processing mailbox messages: Mailbox does not exist. We opened a case with Solarwinds.