pabely ✭✭✭✭✭

Yes I agree but as I detailed earlier even big ERP Apps like SAP have the same workaround. I cannot see it being a justification to holding up the whole release when many people are waiting for the checklist enhancements.

And if you do a "java -version" as Local Admin it shows you are running OpenJDK 8.0 or above?

WHD12.7.10 Release Notes now available and do specifically say support for Windows Server 2022. The Installation / Upgrade Guide does specify a Java version check though on Page 34 and if it has a lower level than OpenJDK 8.0 then to use the switch as already detailed here.

Hot off the press WHD12.7.10 seems to have been released on Portal but Release Notes & Install / Upgrade Guide still point to the 12.7.9 versions so cannot confirm 100% if this release supports Windows Server 2022 or not currently. Hopefully SW can update their web site links quite quickly.

Yes that should work as should set JAVA_TOOL_OPTIONS="-Dos.name=Windows 7" Other applications (like SAP) which deliver Java have similar problems with Windows Server 2022 and this gets you past it. As @percyplant pointed out, as WHD12.7.9 is not officially supported in Windows Server 2022, the use of these are at your own…

Not supported currently, contact support to see if they have any workarounds. I would hope that they will support Windows Server 2022 in next release of WHD.

Are you taking about the account on the Customer Portal? If so contact them, details on the SW Support site although you might need to be an existing register contact to do this or fill in a Form signed by a known contact.

Release Notes for 12.7.8 detail a fix for "Techs can now view all FAQs created by techs and clients.". This maybe your issue to upgrade to 12.7.9 + HF1

Are you trying to run on a Windows 2022 Server?

If you have a similar issue I would log with support and supply healthcheck report and environment details as it will need more detailed analysis than this forumn can supply.

Re-able Basic Auth in your Tenant to give you a few weeks grace, upgrade to 12.7.5 or above.

No 12.7.2 was the first release with this option

Hi Dave, There is no read only mode. You can disable End User Login via Setup > Clients > Options > Client Login = Unticked. Deactivate unnecessary Technician accounts - Setup > General > License > Tech licensing. Finally stop WHD from responding to linked Inbound E-Mail - Setup > E-Mail > Incoming Mail Accounts > E-Mail…

I don't think changing it will help, it may make it worse in creating ALL new Assets using the serial number. Sounds like a full backup before, then try out of hours.

You are doing the Sync and allowing WHD to generate it's own number sequence. The first Option "Asset No." could have Sync'ed on Serial number so it would have seen it as the same Asset, unfortunately it is seeing it as a new Asset and thus creating a new record for it.

Does a second record exist within SCCM? Also what are you Sync on within Attribute Mapping Tab in the Discovery connection in WHD?

First time I have seen this but as I said, Modern Auth worked fine for us with older releases.

You might have been suffering from this https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/authentication/access-denied-when-connect-to-office-365 - Also I have seen a delay in Azure propagating changes immediately.

OAUTH has worked since release 12.7.2, we have been through this, 12.7.3, 12.7.5, 12.7.7 to 12.7.9 and it continued to work through all WHD version releases. Not sure if this was the real issue but their API might have been updated as Azure is a moving target. This error usually occurs when using expired login credentials…

I have seen when adding a Note, entering default custom fields & checklist items and trying to change status at the same time that it misses the closure, I tend to do everything else then do the Closure (Change Status) straight afterwards but I am used to ITSM systems where you first Propose Solution and then Force Close…

I cannot say I have seen this as described, if it is reproducible I would record a Video and submit to Support.

I do not believe this is a Feature of a Client Admin - I suggest you raise a Feature Request as that sounds like a good idea.

If this is not giving you any application issues, I would just ignore.

To get a new Icon to appear in Client UI as a Box with an arrow going NE to open a new browser Tab.... Setup > General > Options > Show Icons for Referenceable URLs = Ticked

I have not seen that before. Support would be the best medium to get advice on this.

Any release above 12.7.2 has the Modern Auth settings within the Inbound Mail setup screen but you can go straight from 12.7.1 to 12.7.5 so might as well go for a more stable release with more bug fixes.

Yes see Basic Authentication Deprecation in Exchange Online – September 2022 Update

Strongly recommend going to at least release 12.7.7 via 12.7.5

Correct, painful one to experience. Have seen this with someone who had 1000+ unread e-mails in their mailbox which quickly got sucked into WHD as new Tickets and deleted in their mailbox. 

This looks like the issue with Office365 Mailboxes where Basic Auth has been switched off by MS, you need to temporary extend Basic Auth, hard stop at 31st Dec and move to using Modern Auth. This will require the help of your Azure Admin.