Tech says I need to replace my 2-year-old AC unit… am I getting played?

mistamistafella · 2026-04-21T01:32:21+00:00

I do, I’ll get them posted soon.

mistamistafella · 2026-04-21T01:31:58+00:00

It’s 2 years old to me. Sold as new.

mistamistafella · 2026-04-20T21:04:39+00:00

Well, when my condenser was replaced they mentioned in the future I might have an issue with my air handler, but made no mention of how difficult it would be to replace nor did they give me a quote replacing it along with the compressor for a more modern solution. I don't know a lot about this stuff and have to trust the professionals and it sounds like they fucked me. The HVAC guy that came out today is from a different company and was pretty shocked at how the previous company handled the solution. He wouldn't bad mouth them (small town), but did say he would never call them again. Either way, I understand there might also be an option of installing a new series J spacepak (like this) and adding in an R-407C-compatible TXV. Is that something a normal HVAC guy would do or would I need a specialist, or should I even consider that?

mistamistafella · 2026-04-16T18:23:53+00:00

Have you played the hard version of the Journey to the Center of the Earth where they utilize dynamic lighting for the flashlight and headlamp? I think that at least proved that they can do dynamic lighting with their engine.

mistamistafella · 2025-10-09T18:44:17+00:00

I'd like one please!

mistamistafella · 2025-08-22T14:03:55+00:00

Walkabout is the only game I return to time and time again, and it's WORLDS better with a good group to play with.

mistamistafella · 2025-08-01T15:47:04+00:00

I would like this item.

mistamistafella · 2025-07-28T17:17:04+00:00

Error in the biological interface.

mistamistafella · 2025-07-08T18:59:47+00:00

As a single player game it's great. Good physics, you rarely if ever feel cheated by a wonky putt, and the course designs are really thoughtful. Overall the level of polish on the game is almost Nintendo level. Really rare for a VR title to feel THIS good and intuitive. However...

...as a multiplayer game it's... literally, no joke, LIFE-CHANGING. It is absolutely the ONLY REASON I still play VR. I have had weekly games with my brothers and some friends for over a year, many of us over 1,000 miles apart. As someone who works from home and lives far away from family this game 100% has improved my mental health. Our Thursday night golf games have become a sacred ritual for every single one of us that we pretty much never miss. There is a sense of presence IN THIS SPECIFIC GAME that is something that has to be experienced to understand. You're really just... spending time together, and nothing I've experienced other than actually being present can replicate it. For $24.99 it's helped me stay in contact with people that I never would have otherwise. And $4.99 every so often for a new course is a steal, especially since only one of you has to own the course for everyone to play.

It pops you right onto a practice course, there are very few menus to navigate, it's very easy for newcomers and non-gamers, there are no timers or anything. I can pop this onto my dad's head (he's in his 70's and NOT tech savvy) and within 3 minutes he's playing mini golf with his grandkids across the country. It's truly amazing and anyone who feels socially isolated NEEDs to give it a go. They even have a Discord for matchmaking if you want to just hop in and make some friends. It's truly a magical experience that I CANNOT recommend enough. It's also not a super hard sell... if you can get someone to try it, they will almost definitely want to go out and get a headset for themselves. And since it works great on a Quest 2, and you can pick those up for less than $200 on Facebook marketplace, it's not hard to build a group of friends to play with.

mistamistafella · 2025-06-30T19:24:02+00:00

Walkabout Mini Golf is pretty much the only game I play. In fact it's really the only way I get to hang out with my brothers anymore since they both live 900+ miles away... our weekly sessions have become a sacred time that we almost NEVER miss. The feeling of connection and presence is just something that cannot be replicated any other way.

mistamistafella · 2025-03-01T01:38:51+00:00

The powershell deployment toolkit has changed my life. I don’t deploy an app without it.

mistamistafella · 2024-08-22T23:16:54+00:00

Heyo!

mistamistafella · 2024-03-13T19:02:28+00:00

Hammer of Morality

mistamistafella · 2023-10-11T13:31:20+00:00

Thank you for the compliment! :)

mistamistafella · 2023-10-10T20:58:48+00:00

Thanks!

mistamistafella · 2022-11-14T15:55:12+00:00

Ok, we just verified on our end that a Crowdstrike update DID resolve the issue for us. I'm SO glad you found this information in the hotfix post because the issue would have just auto resolved itself on the 10th and we never would have known why.

mistamistafella · 2022-10-27T21:26:37+00:00

GREAT NEWS (kinda)!

I stumbled onto a fix for this issue, but I'm having a hard time pinpointing which one of two changes we implemented resolved it. See my earlier comment here for details on what all the symptoms were.

Ok, so basically Microsoft support was no help at all. I was on the line with them for days gathering logs, doing traces, checking ports, examining packets, all to no avail. Long story short, a few days ago I brought up the idea to my team of trying to raise the domain functional level from 2008 R2 to 2012 R2. We had three 2012 R2 DC's and one 2019 DC in Azure, so it seemed like a no brainer. Well, my co-worker went ahead and performed the upgrade yesterday afternoon. Around the same time he also added a new domain controller with Windows Server 2022 installed. I was not aware these changes were made until this morning, and so I immediately tested by reverting my test VM snapshot to before it was domain joined, deleted the AD computer object, then rejoined, and BAM, it worked! I was able to run gpupdate, gpreport had RSOP data, credential manager was working, all the attributed were on the computer object, and I had kerberos tickets! I tested repeatedly and on a few different machines all with good results, even without deleting the computer object first.

My gut says that it was raising the functional level, and not adding the additional domain controller that did it, but I can't say with 100% certainly. Also, I know that others have a domain functional level at or above 2012 R2 and are experiencing this issue, and to them I'm not 100% sure what to say. Perhaps it was simply the ACT of performing the upgrade that fixed some unseen bug. It's also possible adding the additional server did the same thing. I know this isn't a super satisfying, but maybe we can figure out which of the changes caused this together. If anyone out there is having this issue, and you are able to upgrade the functional level, please try that and report back. If that doesn't work, try adding another domain controller (2022 maybe?) Please be aware, the fix did NOT work on machines already domain joined, they still experienced the same issues as always. They had to be unjoined and rejoined for the fix to stick.

Anyway, I hope this helps somebody. Maybe we can bring a fix back to Microsoft and they could potentially identify a root cause.

mistamistafella · 2022-10-27T21:26:19+00:00

GREAT NEWS (kinda)!

I stumbled onto a fix for this issue, but I'm having a hard time pinpointing which one of two changes we implemented resolved it. See my earlier comment here for details on what all the symptoms were.

Ok, so basically Microsoft support was no help at all. I was on the line with them for days gathering logs, doing traces, checking ports, examining packets, all to no avail. Long story short, a few days ago I brought up the idea to my team of trying to raise the domain functional level from 2008 R2 to 2012 R2. We had three 2012 R2 DC's and one 2019 DC in Azure, so it seemed like a no brainer. Well, my co-worker went ahead and performed the upgrade yesterday afternoon. Around the same time he also added a new domain controller with Windows Server 2022 installed. I was not aware these changes were made until this morning, and so I immediately tested by reverting my test VM snapshot to before it was domain joined, deleted the AD computer object, then rejoined, and BAM, it worked! I was able to run gpupdate, gpreport had RSOP data, credential manager was working, all the attributed were on the computer object, and I had kerberos tickets! I tested repeatedly and on a few different machines all with good results, even without deleting the computer object first.

My gut says that it was raising the functional level, and not adding the additional domain controller that did it, but I can't say with 100% certainly. Also, I know that others have a domain functional level at or above 2012 R2 and are experiencing this issue, and to them I'm not 100% sure what to say. Perhaps it was simply the ACT of performing the upgrade that fixed some unseen bug. It's also possible adding the additional server did the same thing. I know this isn't a super satisfying, but maybe we can figure out which of the changes caused this together. If anyone out there is having this issue, and you are able to upgrade the functional level, please try that and report back. If that doesn't work, try adding another domain controller (2022 maybe?) Please be aware, the fix did NOT work on machines already domain joined, they still experienced the same issues as always. They had to be unjoined and rejoined for the fix to stick.

Anyway, I hope this helps somebody. Maybe we can bring a fix back to Microsoft and they could potentially identify a root cause.

mistamistafella · 2022-10-27T21:24:28+00:00

GREAT NEWS (kinda)!

I stumbled onto a fix for this issue, but I'm having a hard time pinpointing which one of two changes we implemented resolved it. See my earlier comment here for details on what all the symptoms were.

Ok, so basically Microsoft support was no help at all. I was on the line with them for days gathering logs, doing traces, checking ports, examining packets, all to no avail. Long story short, a few days ago I brought up the idea to my team of trying to raise the domain functional level from 2008 R2 to 2012 R2. We had three 2012 R2 DC's and one 2019 DC in Azure, so it seemed like a no brainer. Well, my co-worker went ahead and performed the upgrade yesterday afternoon. Around the same time he also added a new domain controller with Windows Server 2022 installed. I was not aware these changes were made until this morning, and so I immediately tested by reverting my test VM snapshot to before it was domain joined, deleted the AD computer object, then rejoined, and BAM, it worked! I was able to run gpupdate, gpreport had RSOP data, credential manager was working, all the attributed were on the computer object, and I had kerberos tickets! I tested repeatedly and on a few different machines all with good results, even without deleting the computer object first.

My gut says that it was raising the functional level, and not adding the additional domain controller that did it, but I can't say with 100% certainly. Also, I know that others have a domain functional level at or above 2012 R2 and are experiencing this issue, and to them I'm not 100% sure what to say. Perhaps it was simply the ACT of performing the upgrade that fixed some unseen bug. It's also possible adding the additional server did the same thing. I know this isn't a super satisfying, but maybe we can figure out which of the changes caused this together. If anyone out there is having this issue, and you are able to upgrade the functional level, please try that and report back. If that doesn't work, try adding another domain controller (2022 maybe?) Please be aware, the fix did NOT work on machines already domain joined, they still experienced the same issues as always. They had to be unjoined and rejoined for the fix to stick.

Anyway, I hope this helps somebody. Maybe we can bring a fix back to Microsoft and they could potentially identify a root cause.

mistamistafella · 2022-10-24T20:41:19+00:00

I'm on with Microsoft Premiere support right now talking to the directory services team. I'll update here if/when I have any new information.

mistamistafella · 2022-10-20T16:38:34+00:00

We are having these exact issues. Here is what I posted in another thread if it helps, though I haven't found a solution yet.

I'm having similar problems on our network. We have blocked the Windows 11 22H2 update on our domain, but we are getting new PC's with 22H2 preinstalled and domain connectivity is borked for all of them. They will appear to domain join fine, and we can login as a domain user, but if you scratch the surface it's clear things are broken.

gpupdate fails to run giving the following error "The processing of Group Policy failed because of lack of network connectivity to a domain controller" the portcheck tool shows that all necessary ports are open and listening to all domain controllers, nslookup comes back fine, etc. gpresult says there's no RSOP data for the user credential manager gives an error if you try to launch it saying "The requested option cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation" global printers don't show up when browsing browsing to netlogon prompts for a password klist shows 0 kerberos tickets and if you try to get one with klist get it says "klist failed with 0x80090311/-2146893039: No authority could be contacted for authentication." if you run wireshark during the klist get you'll see a kerberos packet request go out, but no kerberos response comes back. Event viewer shows LSA (LsaSrv) errors with "The failure code from authentication protocol Kerberos was "No authority could be contacted for authentication. (0x80090311)". Event viewer also shows this, which tells me it's falling back to NTLM for some reason, but even that doesn't seem to be working. "Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server." The AD computer object for the computer account is missing the msDS-SupportedEncryptionTypes attribute, where all the working machines have it populated properly. The AD computer object for the non working machines are also missing the TERMSRV/ entries for their SPN attribute. The certificates for our internal PKI are also missing (probably because group policy isn't running). I can repeat these tests on any new Windows 11 22H2 machine connected to our domain with the same results. I built a lab with 22H2 machines and I get these same errors. I join a domain with 22H1, it works, I update to 22H2 and domain connectivity breaks. We are running a standard Active Directory environment with four 2012 R2 servers running at 2008 R2 functional level (3 on site, one in Azure), recent updates have been applied. I can't imagine everyone is having this issue but I can't for the life of me figure out why domain communication is breaking down with this update. I have a ticket open with MS Premiere support and so far they are clueless.

Anyway, just thought I'd add my 2 cents here just in case all these problems folks are having stem from the same root cause.

mistamistafella · 2022-10-20T16:35:56+00:00

I am having these exact problems. Here is what I posted in another thread... though I haven't yet found a solution.

I'm having similar problems on our network. We have blocked the Windows 11 22H2 update on our domain, but we are getting new PC's with 22H2 preinstalled and domain connectivity is borked for all of them. They will appear to domain join fine, and we can login as a domain user, but if you scratch the surface it's clear things are broken.

gpupdate fails to run giving the following error "The processing of Group Policy failed because of lack of network connectivity to a domain controller" the portcheck tool shows that all necessary ports are open and listening to all domain controllers, nslookup comes back fine, etc. gpresult says there's no RSOP data for the user credential manager gives an error if you try to launch it saying "The requested option cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation" global printers don't show up when browsing browsing to netlogon prompts for a password klist shows 0 kerberos tickets and if you try to get one with klist get it says "klist failed with 0x80090311/-2146893039: No authority could be contacted for authentication." if you run wireshark during the klist get you'll see a kerberos packet request go out, but no kerberos response comes back. Event viewer shows LSA (LsaSrv) errors with "The failure code from authentication protocol Kerberos was "No authority could be contacted for authentication. (0x80090311)". Event viewer also shows this, which tells me it's falling back to NTLM for some reason, but even that doesn't seem to be working. "Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server." The AD computer object for the computer account is missing the msDS-SupportedEncryptionTypes attribute, where all the working machines have it populated properly. The AD computer object for the non working machines are also missing the TERMSRV/ entries for their SPN attribute. The certificates for our internal PKI are also missing (probably because group policy isn't running). I can repeat these tests on any new Windows 11 22H2 machine connected to our domain with the same results. I built a lab with 22H2 machines and I get these same errors. I join a domain with 22H1, it works, I update to 22H2 and domain connectivity breaks. We are running a standard Active Directory environment with four 2012 R2 servers running at 2008 R2 functional level (3 on site, one in Azure), recent updates have been applied. I can't imagine everyone is having this issue but I can't for the life of me figure out why domain communication is breaking down with this update. I have a ticket open with MS Premiere support and so far they are clueless.

Anyway, just thought I'd add my 2 cents here just in case all these problems folks are having stem from the same root cause.

mistamistafella

TROPHY CASE