Recently we have seen a couple of instances of updated AV software quarantining the eVo TD Service as a precaution.

Obviously it is not a virus but some of the repetitive file access projects particularly around PDF editing and optimisation look awfully like it.

We always state that the services, Program files, and Program Data folders together with any transactional folders should be excluded specifically in the Server AV configuration, or trusted.

The quarantine of a service being triggered simply stops the system, but even real-time inspection of files being read and written by Formate could significantly impact throughput due the server loading and delay inspection of the files by the AV suite.

Unusually Formate eVo v24 will continue for a few more months into 2025.

This is to allow us to review the underlying .NET basis of eVo and evaluate the work needed to move from the classic .NET framework (4.8.xx) as used now to .NET v8 (Core).

Alongside this we are going to take the chance to review the design and layout of Dashboard, with an aim of a freshen up and simplification, as we have to admit it has grown a little “cluttered” over the years.

We will publish further news as we make progress on this exciting project.

New Patch Release – Please see release notes in Dashboard Update Utility Headlines:

Microsoft is introducing a new XPS based printing system to eliminate print drivers and the associated vulnerabilities.

[Update: as of today 09.10.2024 WPP only in Windows 11 24H2]

Since the early days of Windows, Microsoft have allowed the easy silent distribution and installation of print drivers written by printer hardware manufacturers and others. To do this very powerful system level permissions are inherently granted to the Windows Printing subsystem, the Windows Print Spooler, which eventually led to these being exploited by bad actors, most famously with the “PrintNightMare” attack.

In response, Microsoft have gone beyond patching and are introducing “Windows Protected Printing”, to offer a print driver free printing system, built around generic embedded Type 4 class drivers. This will provide a secure environment in the sense it will remove the ability to install a custom written Print driver, and the associated potential for exploitation.

This will of course take time to become common, and is optional for the foreseeable future, but at present.

1. Switching on the option, is a one way trip, being irreversible. [Update: Existing incompatible drivers are uninstalled – if WPP switched off re-installation would be required]
2. Hardware manufacturers will need time to respond
3. Legacy hardware may not support the new print system, and if they don’t, probably never will.
4. Printing is going to be based on type 4 XPS drivers only.
5. Type 3 drivers will not work. meaning older printers may no longer be usable.
6. Printer functionality may become more limited, depending upon hardware manufacturer support.
7. Formate eVo print output is already XPS based, but virtual printers are unlikely to work.
8. Some Legacy ERP systems may be unable to print to Windows shared printer anymore.
9. Sending directly, “code” such as ZPL to a thermal printer or HPGL to a Plotter via a driver may be impossible.

Please speak to us before switching on Windows Protected Printing on a server hosting eVo,

As we will see our understanding evolve over the coming 12-24 months, the above should be viewed as simply our initial view, and may not be 100% accurate, and is intended to only raise awareness and prompt consideration at this point, not be definitive.

Only first job prints to eVo virtual printer from AS400\iSeries\UNIX, further print jobs held in host system print queue after installation of MS Update KB5040437 (server 2022), KB5040430 (server 2016)

2024-07 Cumulative Update for Microsoft server operating system, version 22H2 for x64-based Systems (KB5040437)

and equivalent updates for other Windows OS versions

Print problems from AS400 have been reported, but may affect any system such as UNIX hosts using Windows LPD (RPM users should not be affected)

First job prints, then subsequent jobs sit in As400 print queue and are not accepted by windows server.   restart allows one more job through.

Microsoft acknowledges problem LPD Service stops after CVE-2024-38027 – Microsoft Community –

this is a native windows LPD problem and seems like rollback is the current fix

High Volume Email for Microsoft 365

As we have reported many times Microsoft do not allow\want the sending of high volumes of emails through a standard O365 user account, making it difficult sometimes with back office systems such as Formate eVo.

To be fair Microsoft have offered authenticated SMTP as a step forward, but whilst it expands the boundaries, it doesn’t offer a real break through. Microsoft also offer a chargeable Azure Comms service which allows the bulk sending of emails, but it is far from simple;

Overview of Azure Communication Services email – An Azure Communication Services concept article | Microsoft Learn

We ourselves have had good success sending via 3rd party services such as MailGun, or SMTP2GO, and this remains our chosen solution.

However there now might another option coming! Microsoft are previewing HVE (High Volume Emailing) accounts.

Public Preview: High Volume Email for Microsoft 365 – Microsoft Community Hub

High Volume Email for Microsoft 365 still has limitations, isn’t universally available at present but may push the boundaries still further – Might be something worth checking out.