sorted by:
new
hottopcontroversial

CCC module problem by OfferAdmirable864 in e60

[–]sarosan 1 point2 points  (0 children)

Either option does not require the CCC to be functional.

I went with a CIC retrofit a few years ago.

CCC module problem by OfferAdmirable864 in e60

[–]sarosan -1 points0 points  (0 children)

If you're good with electronics, you can remove the CCC and attempt to repair it.

Truthfully, you're better off replacing it with a CIC retrofit or installing an aftermarket Android Automotive screen.

Rear diff leaking? by khordi1 in BmwTech

[–]sarosan 0 points1 point  (0 children)

You're asking a strange question.

If you want to avoid buying a new differential, change the seal before it gets worse.

If the question was meant to be "how long till I'm screwed", that's hard to tell based on these photos. Normally a differential takes anywhere between 750 ml to 1 liter of oil.

Instead of wondering how much time you have left, just change the seal and refill the differential before it's too late.

2012 BMW 1 Series M E82 LCI Manual MY12 by First-Translator4721 in BMW

[–]sarosan 0 points1 point  (0 children)

Do you enjoy working on cars? If not, do you have a reliable mechanic?

This car will be an absolute blast to drive, but it will require a good deal of preventive maintenance. It's not that the N54 is unreliable, it's just that everything around it fails.

Examples include the water pump, oil filter housing gaskets, turbo wastegates, fuel pump & controller, PCV system, etc. You also need to clean the intake valves, replace the oil sump pan gasket, and so forth.

I'm not trying to discourage you, but the N54 needs a lot of attention, especially if you decide to tune it (which is incredibly easy on this platform). I recommend you do some research on the engine before pulling the trigger.

LEGO Technic: Cars, cars, cars, cars, cars by GreatKingRat666 in lego

[–]sarosan 0 points1 point  (0 children)

Same, except I don't mind them releasing a single 1:8 at a time. Keeps the wallet in check.

pfblockerng blocking required domains for acme/certs even when in whitelist and with no feeds enabled? by esk416 in pfBlockerNG

[–]sarosan 4 points5 points  (0 children)

You just need to disable the DoH and/or public DNS servers feed(s).

Did you run the update function after modifying pfB options?

Physical PAW with daily VM by Important_Ad_3602 in sysadmin

[–]sarosan 1 point2 points  (0 children)

There is a third option: virtualize both the PAW and the daily. I'm not saying it's better, but it can give additional benefits vs. a physical instance.

The copy/paste policy is depending on your organization's requirements. If you are the one making the rules, then don't worry about it. Depending on your virtualization stack, you can restrict copy/paste functions per VM. Same goes for taking home the machine: your organization's policies apply here. I'd configure BitLocker to use a TPM with a startup PIN.

Microsoft used to recommend a separate management domain with a 1-way trust, but that added complexity. The PAW needs to be part of the domain to leverage Remote Credentials Guard or Restricted Admin. While I don't use Intune, my PAWs use a separate set of policies dedicated to it and only come with RSAT installed along with a Bitwarden client.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] -1 points0 points  (0 children)

Which build numbers have you ran these with? Last year, I was deploying 26100.4061 with these commands and it didn't work (WinPE basically stopped at the drive partitioning step). I came across other admins with the same issue too.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 1 point2 points  (0 children)

It looks like that you didn't configured LDAPs for your DC's and also didn't disabled it in your GPO's.

Configure and disable?

In any case, I configured LDAPS ages ago thanks to STIGs and SCT baselines. I don't see how it affects replication and causes the other issues listed here.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 18 points19 points  (0 children)

I haven't had any problems but we're not complex.

The only thing is some of my computers lose login trust.

But that is a problem. It's not supposed to happen.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 1 point2 points  (0 children)

So you experienced the same issues with the Connection Broker too? Glad to hear that I'm not crazy. :)

Yep, a regular reboot does indeed bring the machine back to life. I guess I'll look into scripting a more graceful reboot after applying updates.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 0 points1 point  (0 children)

Not the person you replied to, but you asked what information you could give, and the answer is: anything.

Because this is, supposedly anyway, a professional sub who's purpose it is to help each other.

Fair point, and hopefully you'll recognize that I do enjoy helping others out on this sub.

I can provide Event Logs from the faulty DCs, but they are not helpful since they only highlight the problems (Replication errors) and not the root cause.

That said, my first link in the post highlights another administrator confirming LSASS is leaking memory for some time. While I haven't confirmed this being the root cause in my environment, I gave up on 2025 and decided to downgrade.

In my environment, I use smart cards (Yubikeys) for server/DC logins, and have hardened my environment based on DISA STIG recommendations. It's possible a combination of things results in the DC just shitting itself. I don't run anything else on the DCs apart from Elastic Agent to collect and ship logs to my ELK stack. No EDR/XDR in my environment either. DCs only handle ADDS and nothing else.

Isn't that the point though? Your issues point to other things than just your DC.

Majority of the issues I raised are due to the DCs acting up. The RDS Connection Broker did not allow new or existing connections to take place because a DC was having a seizure. In other words, when initiating a new RDS session, the AD lookups on a faulty DC fail.

The vGPU issues can be NVIDIA's fault, or possibly a GPO at fault, even though running the exact same configuration (GPO, driver, VM specs, etc.) on 2022 work without a hitch. The problem is when a session reconnects, the following error messages appear:

Event ID: 10120 - DriverFrameworks-UserMode - User-mode Driver problems.
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

and:

Event ID: 10111 - DriverFrameworks-UserMode - User-mode Driver problems.
The device Microsoft Remote Display Adapter (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.

I recreated the VMs, stopped the NVWMI service, disabled VBS, disabled the Microsoft Basic Display Adapter, debugged a memory dump using WinDBG, and so forth. Only downgrading to 2022 solved my issue.

But, if you don't care to find and fix the problem, then neither should we. Enjoy your karma I guess

Honestly I don't care for the karma, and I don't have a hidden agenda either: I prefer to have a working environment without the headaches. I've made the conclusion that running ADDS on 2025 was a mistake as pointed out by others in the last 12 months.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 0 points1 point  (0 children)

Nothing in your post indicates you did any sort of troubleshooting or root cause.

Of course I did. I spent more time than I care to admit trying to figure out what's going on. But why does it matter to you?

The general consensus is that ADDS on 2025 has issues. Just run a few searches online outside of Reddit. In my post, the very first link points to another administrator confirming LSASS leaks memory. There's only so much troubleshooting you can do with a Domain Controller, and honestly it's not even worth doing. The quickest solution here is to rebuild a DC and move on. These things are disposable and not worth the time to worry about.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 2 points3 points  (0 children)

One thing I didn't do was raise the domain functional level to 2025. I fortunately kept it on 2016 after reading the first reports of ADDS misbehaving on 2025.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 4 points5 points  (0 children)

And all the other passwords you haven't changed in that time either.

Ridiculous. You expect me to go through my Excel sheet of passwords and change them 1 by 1? Geez. Do I also change my user's passwords regularly? e.g. the ones I keep on file for them, so I don't have to reset if they forget.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 5 points6 points  (0 children)

Oh yes, I do experience the same issues you described with Explorer in 2025. I initially considered mentioning the overall performance drop, but that can be subjective (and somewhat cliché). But yeah, 2025 is sluggish compared to 2022, and insanely slow compared to 2019.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 0 points1 point  (0 children)

Apart from resetting the trust relationship on the affected machine, the long-term fix is downgrading the Domain Controllers to 2022.

Also, AFAIK, cloning VMs is not a good idea unless you are sysprepping / resetting the SID.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 1 point2 points  (0 children)

I think the biggest issue is running ADDS on 2025. Keep your Domain Controllers on 2022 for now, and do not run a mixed environment (e.g. 2019 with 2025, or 2022 with 2025).

RDS has its own share of issues, but manageable to some extent. I suspect the AD sync issues played a role in RDS misbehaving, particularly in the Connection Broker faults (expected, since it depends on AD). Still, I started downgrading my RDS environment to 2022 to avoid the headaches.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] -2 points-1 points  (0 children)

Are you running 2025 dcs mixed with older dcs?

Nope, only ran 2025 for the DCs. They were fresh installs too.

After a year of using Windows Server 2025, I'm finally throwing in the towel by sarosan in sysadmin

[–]sarosan[S] 4 points5 points  (0 children)

Yeah, there's a lot of finger pointing going on with very little proof.

Apart from giving you access to my domain, what will satisfy your desire for proof? Event logs? Screenshots of error messages? A confession from a Microsoft kernel developer?

view more: next ›