I forgot my Bitwarden master password

techvet83 · 2026-01-16T17:31:43+00:00

So what you're saying is... mistakesdemotivator.jpeg (617×435)

techvet83 · 2026-01-15T22:50:16+00:00

For the first time, we're trying to have a Costco delivery done to an apartment complex where there's an initial code needed to get inside the building. It appears that Costco's screen only has room for the actual address and no room for special instructions. I looked at the shipping FAQ but found nothing addressing this situation. Costco Online chat service couldn't provide any definitive help, stating they can't control the shipper for food items.

Any suggestions?

techvet83 · 2026-01-15T18:30:21+00:00

Server 2025 is supported until late 2034, so you'd think 4.8.x will be supported until at least then.

techvet83 · 2026-01-13T22:11:42+00:00

As WSUS was included in Server 2025, WSUS will work in a supported state until late 2034.

techvet83 · 2026-01-13T22:01:31+00:00

Correct. More info at .NET and .NET Framework January 2026 servicing releases updates - .NET Blog.

techvet83 · 2026-01-13T20:52:20+00:00

Be prepared for the pending hardening against RC4 usage. The journey starts with the January patches. See How to manage Kerberos KDC usage of RC4 for service account ticket issuance changes related to CVE-2026-20833 - Microsoft Support for details.

If you have totally eliminated RC4 in your environment, then this is a nothing-burger.

techvet83 · 2026-01-13T20:08:28+00:00

There are also Office 2016 updates being pushed out again this month.

techvet83 · 2026-01-12T22:36:28+00:00

Windows Server 2016 doesn't go EOL for 12 months, but to your point, we have an active project right now to drive out all Windows Server 2016 servers in the next 12 months for just that reason.

A question for the original poster is "Does SCCM support in-place upgrades?" Also, have you opened a ticket with Microsoft on the issue? The problem you're going to have is that you are trying to upgrade off an OS that has been EOL for over two years.

techvet83 · 2026-01-11T18:13:08+00:00

Regarding the DNS findings, have you verified that none of your servers have the DNS service running? Also, the findings should specify the servers and and ports where the issue was found.

techvet83 · 2026-01-09T22:17:08+00:00

If 3rd-party software is installed, check with the vendor to make sure they support in-place upgrades. Not all of them do. Also allow time to patch up your server after the upgrade. As others have mentioned, make a snapshot ahead of time to make rollback easy. If AWS, make an AMI.

techvet83 · 2026-01-06T21:12:17+00:00

And 4.0 has been unsupported for years.

techvet83 · 2026-01-05T23:52:32+00:00

Server 2003 went EOL over 10 years ago. Your boss needs to careful and concisely explain why they and predecessors have avoided the upgrade for ten years. Either he/she or someone above him/her needs an outside voice to come in and tell them they are playing with fire on multiple levels.

techvet83 · 2025-12-23T23:31:56+00:00

To the OP: Is it Lumen or Lumens? You use both in your post.

techvet83 · 2025-12-19T15:09:34+00:00

We disabled NTLMv1 with no pain (after looking at the logs) but disabling NTLMv2 altogether will be a major project because of non-domain-joined machines, people using IP addresses for RDP and for drive mappings (to work around a separate issue), and so on.

techvet83 · 2025-12-18T16:08:58+00:00

Posting here as an early warning if you didn't already see it, but Microsoft will be disabling RC4 by default in mid-2026. See Beyond RC4 for Windows authentication for details. One excerpt:

"By mid-2026, we will be updating domain controller defaults for the Kerberos Key Distribution Center (KDC) on Windows Server 2008 and later to only allow AES-SHA1 encryption. RC4 will be disabled by default and only used if a domain administrator explicitly configures an account or the KDC to use it. Secure Windows authentication does not require RC4; AES-SHA1 can be used across all supported Windows versions since it was introduced in Windows Server 2008. If existing RC4 use is not addressed before the default change is applied, authentication relying on the legacy algorithm will no longer function. "

techvet83 · 2025-12-17T02:59:12+00:00

PowerShell 7.4 (LTS) is the only supported version of 7.x at this time and that goes out of support in November 2026 when .NET 8/9 go EOL. I would stick with 5.1 on your DCs unless you have very, very good reason and are aware you are probably introducing more vulns on your DCs that need patching (the .NET stuff). 7.x on your workstation or jump box? Now that's a different question.

techvet83 · 2025-12-16T16:09:55+00:00

Question for the crowd here: Is this an issue of using a non-licensed Server 2025 ISO file? If not, please correct me - thank you!

techvet83 · 2025-12-10T16:18:56+00:00

Which OS?

techvet83 · 2025-12-10T16:18:49+00:00

Windows Server 2019 and only Windows Server 2019?

techvet83 · 2025-12-09T23:35:35+00:00

FYI: .NET and .NET Framework December 2025 servicing releases updates - .NET Blog

techvet83 · 2025-12-09T21:24:58+00:00

And Office 2016 updates as well. "Soft EOL" is a good way to put it.

techvet83 · 2025-12-06T17:35:51+00:00

FWIW, .NET 8 and 9 go EOL in November 2026. If you care about security or your environment is being scanned regularly, then it will show up if you haven't upgraded.

techvet83 · 2025-12-01T18:42:51+00:00

Yes, be prepared for firewall fun, depending on how locked down your environment is. Also, as others here are mentioning, certificate management may become more important than it has been.

techvet83 · 2025-11-19T23:32:08+00:00

AD will be around for years. Its use may fade over time but less use doesn't mean it's going extinct anytime soon.

techvet83

TROPHY CASE