Huntress vs ThreatLocker: block everything, or watch everything
Comparing allowlisting with monitoring: ThreatLocker blocks what is not approved, Huntress watches what gets through. Which problem does your firm have?
Read articleEndpoint & Detection
From May 2027, Windows servers will reject NTLM connections that don't sign. How a small office finds the devices that would fail, before they do.
Short answer: Microsoft's November 10, 2026 Windows updates began a two-step change to NTLM, an older sign-in method Windows still uses inside office networks. Today, updated Windows computers offer NTLM signing and servers still accept connections that don't sign. From May 2027, Microsoft says Windows servers will require signing by default and reject devices that don't offer it. A scanner, storage box or older application that connects to your server without signing would stop working that day, so the time to find those devices is now, using the audit log Microsoft added in November.
Ridge Core
Obsidian Ridge's Ridge Core includes endpoint MDR and Microsoft 365 or Google Workspace ITDR at $25 per person per month, month-to-month with no minimum and business onboarding separate. A security team monitors and acts 24/7; Obsidian Ridge provides CISSP-led follow-through within one business day, serving the Research Triangle and businesses across the United States.
Discuss Ridge CoreWhen a computer opens a shared folder or another resource on a Windows server, the two machines have to agree on who is signing in. NTLM is one of the ways they do it. Signing adds a cryptographic check to that conversation, which makes it much harder for an attacker sitting in the middle to relay it somewhere else. Microsoft's page says the change makes sure authenticated NTLM sessions always set up a session key and negotiate real signing.
Phase 1, November 10, 2026. Windows client devices begin offering NTLM signing on all connections by default. Servers accept both signed and unsigned clients, and new audit events start recording which clients don't sign.
Phase 2, May 2027. Windows servers begin requiring NTLM signing by default. Microsoft says clients that don't offer signing will be rejected.
Microsoft lists these versions as affected: Windows 11 versions 23H2 through 26H2, Windows 10 Enterprise LTSC 2021, and Windows Server 2016, 2019, 2022 and 2025. It also says all supported Windows Server versions are capable of signing, so the server is not the problem. The devices that connect to it might be.
Microsoft's page does not name device types. The list below is ours. It is where we would look first, because each of these connects to a Windows shared folder or server and is not a current Windows PC that received the November update:
Whether each of these signs is not something we can tell you from here. The audit log can.
One question Microsoft's page leaves open: it says "Windows servers". It does not say whether a Windows 11 PC that shares a folder for the office will enforce the same default. Check that PC's audit log too. It costs nothing.
If your server runs Windows Server 2016, confirm the events actually appear in its log before you rely on an empty result. Microsoft lists 2016 as affected, and its auditing overview is not consistent about whether 2016 gets the enhanced events.
Microsoft documents two registry values under HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0:
| Setting | 0 (default) | 1 |
|---|---|---|
| ServerRequireNtlmSign | Server accepts signed and unsigned clients | Server rejects unsigned clients. No restart needed. |
| ClientAllowUnsignedNtlm | Client offers signing | Client does not offer signing. Microsoft calls this temporary, for compatibility only. |
Microsoft suggests setting ServerRequireNtlmSign to 1 early, once auditing shows no unsigned connections. We agree, with one condition: choose a quiet day and keep someone available, so that if a forgotten device fails, it fails while you are watching rather than on a Monday morning in May.
Microsoft also says it might remove these registry keys in the future. Treat them as a way to schedule the change, not a way to avoid it.
The same Patch Tuesday fixed CVE-2026-124194, an Outlook flaw attackers were already exploiting. Computerworld reports that a crafted message file makes Outlook connect to an attacker's server without the usual warning and leaks the user's NTLMv2 password hash. Microsoft rated it Moderate. The fix ships in the Microsoft 365 Apps and Office LTSC updates, so a fully patched Windows computer is not proof that Outlook is patched.
Two steps from us, not from Microsoft: confirm the Office update installed on every computer that runs Outlook, and make sure the office firewall blocks outbound file-sharing traffic (TCP port 445) to the internet. A leaked hash needs somewhere to go.
For a practice with a server in the closet, May 2027 is a scheduling problem, not an emergency. The risk is an outage on a day nobody chose: the scanner stops saving, the imaging station cannot reach its folder, or a document system cannot open files. Six months is plenty of time to find those devices if someone starts now. It is not enough if nobody looks until the day things stop working.
The on-premises tax server section of our Lacerte, Drake and CCH hardening guide covers the rest of the server baseline.
The audit itself is a one-off project for whoever manages your server. If you would like a second pair of eyes on what your audit log shows, bring the list to a free review.
Ridge Core
Obsidian Ridge's Ridge Core includes endpoint MDR and Microsoft 365 or Google Workspace ITDR at $25 per person per month, month-to-month with no minimum and business onboarding separate. A security team monitors and acts 24/7; Obsidian Ridge provides CISSP-led follow-through within one business day, serving the Research Triangle and businesses across the United States.
Discuss Ridge CoreLast updated
November 16, 2026. We refresh this content as the threat landscape and tools evolve.
It can. Microsoft says that from May 2027, Windows servers will require NTLM signing by default and reject clients that don't offer it. Anything that signs in to a Windows server with NTLM without signing would fail.
Microsoft does not name which devices those are, so the only reliable answer for your office is the audit log Microsoft added in November 2026.
Updates released on and after November 10, 2026 make Windows clients offer NTLM signing on all connections by default. Servers still accept signed and unsigned clients, and new audit events record the clients that don't sign. Microsoft ties the change to CVE-2026-118737.
Read events 4022 and 4023 in the Microsoft-Windows-NTLM/Operational log, or run the PowerShell script in Microsoft's KB5135557, which lists connections where the signing flag is missing.
Filter on the signing flag itself, not the event level, because Microsoft says signed and unsigned connections both log as warnings.
Yes. Microsoft documents a registry value, ServerRequireNtlmSign, that makes a server reject unsigned clients without a restart, and suggests turning it on early once auditing shows no unsigned connections. Do it only after the audit is clean, or you schedule the outage yourself.
Do not plan on it. Microsoft documents a client setting, ClientAllowUnsignedNtlm, as a temporary compatibility measure and says it might remove these registry keys in the future.
Its page does not describe a server-side exception for May 2027. Plan to update, reconfigure or replace any device that doesn't sign.
No. Microsoft says Kerberos is not affected, and that anonymous and Guest connections are exempt in both phases.
Comparing allowlisting with monitoring: ThreatLocker blocks what is not approved, Huntress watches what gets through. Which problem does your firm have?
Read articleTodyl sells a six-module platform including the network layer, channel-only, with no published pricing. Huntress sells a layer and publishes its rates.
Read articleFor a small business comparing two 24/7 SOC services: what each publishes about price, terms and how you buy, and what that tells you before a demo.
Read article