pabely ✭✭✭✭✭

11.0.7, that is a blast from the past. No GUI on that. What hosting Server are you using!!

https://SERVERNAME:8443/helpdesk/WebObjects/Helpdesk.woa/?username=admin&password=admin assuming you have a Tech Admin account called admin with a password of admin and you run over Port 8443

Yes appears to be the same as you, sorry I have have that ""Display Full Text in Request and Notes" set, always the hover help expansion as it is too much with lost of columns. Let me play with the settings a little more.

I can reproduce the wordwrap if I hover over the Ticket Note and it expands for me but not otherwise because it truncates the Note Description with a ...

You really need to log this with support who should be able to help you if their own documentation is not sufficent for you.

You can't, it is a MS requirement so I have setup a Ticket Task every 85 days to remind to action this. A pain if you have multiple Inbound Mai accounts which all need refreshing with new Tokens. I did raise a Feature Request on SW to auto refresh the access Token via an API call in background then it will fall-back on the…

Action would be "Is any of" and select which Techs from the list.

I have done a quick Test on my test system and it appears to be correct that Action Rules are not checked during Ticket Import so I would say that WHD is working by design.

Select the ones you want to delete from the Asset Type list then just do delete. I think only later releases of WHD allow you to do this.

Not sure if the Action Rule engine applies during such a data Import, I only use these for one off data load when moving Tickets form another system.

Ok, and the Bulk Import is via Setup > Data Import > Import Tickets?

Does the Action Rule have the correct Rule Triggers and are you using the cascade option correctly?

Yes indeed, SQL 2019 supported since the WHD12.7.10 release.

Not knowing how you deploy things but with WHD12.7.10 it supports external PostgreSQL 14 Databases so you might consider putting your database (if you are PostgreSQL Database based) on another Linux Server which just leaves the foreground & background daemons on your WHD Server, may help. On this new Linux Database Server…

I have used CentOS 7 in past as it is supported until 2024 but must admit I haven't tried with WHD12.7.10 but cannot think much has changed on the SW side.

According to the WHD12.7.10 Installation and upgrade Guide on the following flavours of Linux are supported: Red Hat Enterprise Linux (RHEL) RHEL 6.5 (64-bit) RHEL 7.0 (64-bit) RHEL 8.6 (64-bit) CentOS CentOS 6.5 (64-bit) CentOS 7.0 (64-bit) Fedora Fedora 24 (64-bit) Fedora 25 (64-bit) so I would not bother with anything…

I was doing Sync Based on Asset number rather than Serial number

Ok, tested with just one Asset on my test system and it appends it fine, no new Asset entries so should work fine.

warranty (required field) is an Asset Custom field of type date?

My preference would be to build a new Server with Windows 2019, install WHD 12.7.7 and copy database across and upgrade from there, remembering to copy across WHD license and config files then append DNS to be as old Server once decommissioned.

Not sure that will work but will be interested to know either way.

This is what we used to do https://thwack.solarwinds.com/product-forums/web-help-desk-whd/f/forum/17376/whd-video-in-notes but it maybe different now

Just tried to reproduce wordwrap issue but could not, this has just come from a normal Tech Note update or was cut/paste form say Word? I do remember issue with YouTube links, it was a while ago, I will have to do some research on that one on some of our old Support Tickets

Are you able to show us an example to I can verify again a WHD12.7.10 installation I have?

If you look at the right of the Thwack page there are examples within the "Most Downloaded" part The Administration Guide has some additional detail as well.

Always a minefield when you want to mix authentication methods for difference audiences. 

Would your end users be accessing WHD via the Client Interface or just via E-Mail?

I don't think so, if you are using AzureAD for your login, they have to be within this Tenant or Multiple trusted Tenants. You will need to use a third party SAML like Okta which can validate against multiple sources.

Definitely, we have customers with multiple installations servicing different departments & companies as well as one big installation servicing different areas of the business. The big question of what to do is always do you want Tech Admins to have access everywhere with an install, for some with HR involved it is…

Your logic is correct. You should not be using a Distribution Group, a 'real' mailbox should be used. You are likely to need to get an updated Client ID & Client Secret and thus Token from Azure once the change has been made.