A new patching year

Topic

New Reply

PATCH WATCH By Susan Bradley Tomorrow, as usual, Microsoft will release the January patches. Today, as usual, I’m recommending that you not install th
[See the full post at: A new patching year]

Susan Bradley Patch Lady/Prudent patcher

7 users thanked author for this post.

fisher75, lmacri, AlphaCharlie, Casey S, windbg, DLivesInTexas, abbodi86

Reply | Quote

Replies

There’s a typo in your Group Policy tree:

Computer Configuration\Policies\Windows Settings\…

shoud read

Computer Configuration\Windows Settings\Policies\…

Reply | Quote

See https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/ntlm-blocking-and-you-application-analysis-and-auditing/ba-p/397191  When accessed through GPMC.MSC and you edit a policy, they are stored in: Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options

It’s referring to the tree up on a domain controller, not the local group policy.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Obviously, I did not know that. Coincidentally, the same sub-structure exists on Group Policy (local), both on client systems and a Windows Server 2016 not setup as a domain controller. Neither has gpmc.msc, as expected.

Reply | Quote

On a Domain Controller, you can use secpol.msc to modify those settings.

Reply | Quote

I’ve disabled NTLM completely for over a year ago without big issues. Veeam was, at that time, the only problematic piece of software relying on NTLM. But they fixed it in a later version. It was only a couple of weeks ago when again I stumbled across an NTLM-related problem. I’ve setup a Synology NAS in our network, to act as a secondary backup source. ‘Active Backup for Business’ has several methods of backing up servers and the like. The one not working in my case, File Server, relies on NTLM to connect to Windows machines. Although the other method, Physical Server, does a very good job (and doesn’t need NTLM), it’s not as granular as File Server. Hope Synology will fix it in the near future.

Reply | Quote

In the recent newsletter post A New Patching Year, Susan said:

Life is too short to bang your head against the wall trying to make an older printer work in the new environment. Value your time accordingly — my general take is that sometimes it’s better to throw in the towel and get a printer you know will be properly supported. And if you often print material just to have an archive copy, remember Microsoft’s ubiquitous Print to PDF feature and keep the files instead.

So – how do you tell if a new printer is properly supported before you buy it? Do manufacturers advertise this?

Also, thanks for the Print to PDF tip!

Reply | Quote

Is there a way to find out if my current printer meets the criteria? I do use my printer quite often and I would hate to fall victim to this. It is however 4 years old this year, so I don’t know if it’s considered “old.”

Reply | Quote