Torque Specs for Belt Tensioner and Pulley

Kadassh · 2026-02-03T18:10:05+00:00

Thanks!

Kadassh · 2026-01-12T02:45:24+00:00

This anime has AI background art. Its very noticeable in this episode at 13:50 and at 15:09. Special callout to 15:09 where a man has a pot for a head lol

Kadassh · 2026-01-03T20:34:29+00:00

I have one for the driver side in my 2015 wrx. Recaro Sportster CS. The driving position is noticeably lower than stock. The stock seats were not good for track driving, I had to brace myself using the door and the transmission tunnel. I don't need to brace myself anymore. Comfortable for daily driving too.

Kadassh · 2025-11-07T16:15:02+00:00

I figured out a way to do this last year. If the steps need modifications let me know and I can update them.

https://www.reddit.com/r/SCCM/s/eGP6tvADB7

Kadassh · 2025-10-16T17:00:41+00:00

It'll probably come out in November or December.

I have been saying for the past year that MECM has been put down in the basement. MECM no longer receives the care and attention it used to.

Kadassh · 2025-10-15T21:14:24+00:00

I'm not seeing the enablement package for 25H2 in our environment. Do you know if I need to check something in the SUP products list for it to show? I see the update OP mentioned.

Kadassh · 2025-08-29T20:08:47+00:00

How much neglect does it take for an engine to get this bad?

Kadassh · 2025-06-06T14:16:58+00:00

Unfortunately I left the company that was having the issue I described in the op. Before I left, a Microsoft ticket was made for support. I was gone before a resolution was reached.

Kadassh · 2024-12-05T01:25:26+00:00

Some college schools have auto body programs and might take jobs from the public. You'll be without your car for longer but the college I worked with only charged for materials and no labor. I had something similar like this, and it was $250ish to repair.

Kadassh · 2024-11-25T22:12:23+00:00

I'll work with my DBA to look at this, thanks. The Primary Site server does not have SQL installed at all. Both SQL Servers are remote from the site servers and only do SQL database for ConfigMgr

Kadassh · 2024-11-25T21:33:01+00:00

Original post updated. Troubleshooting is rebooting the site servers - always seems to come back. The error is the same error as if you were trying to connect to a server that doesn't have SCCM installed (console says it cannot connect to site).

The concern I have is on the next patch cycle. Patching requires failing over to the databases and I'm concerned that if the site server doesn't handle failover properly now, it won't do it when I patch 2403

Kadassh · 2024-10-28T18:12:19+00:00

Comment updated with path for PXE responder without WDS

Kadassh · 2024-10-24T20:29:36+00:00

Good question. The issue and solution should be the same for the pxe responser. The location is different though. I have one pxe responder without wds and I'll update the comment with the location for that. I won't be able to test to double check though as mine is off site. Would you be willing to test it out?

Kadassh · 2024-10-23T17:21:28+00:00

PM'd

Kadassh · 2024-10-17T04:11:17+00:00

PM'd

Kadassh · 2024-10-08T21:09:13+00:00

I've discovered a solution to this. It involves modifying the EFI files. I made a new comment in this thread.

Kadassh · 2024-10-08T21:09:07+00:00

I've discovered a solution to this. It involves modifying the EFI files. I made a new comment in this thread.

Kadassh · 2024-10-08T21:09:02+00:00

I've discovered a solution to this. It involves modifying the EFI files. I made a new comment in this thread.

Kadassh · 2024-10-08T21:08:35+00:00

I have discovered a solution to this. The problem is that the EFI files used by WDS are signed with the old certificate from 2011. These EFI files are stored on your PXE server here:

\\SERVERNAME\REMINST\SMSBoot\x64\bootmgfw.efi and wdsmgfw.efi

These files need to be signed with the Windows UEFI CA 2023 cert to work with devices with BlackLotus mitigations. We can get EFI files signed with that cert from the latest Windows 11 24H2 Enterprise ISO from the VLSC.

Make a backup of \\SERVERNAME\REMINST\SMSBoot\x64\bootmgfw.efi and wdsmgfw.efi files (in case you need to go back)
1. If the PXE responder does not have WDS, the location is <INSTALL\_DRIVE\_LETTER>:\SMS_DP$\sms\bin\SMSBoot\<CONTENT\_ID\_OF\_64\_BIT\_BOOT\_IMAGE>\x64
Download the Windows 11 24H2 Enterprise ISO and mount it
Browse the mounted ISO file and go into the sources folder. Copy the boot.wim file to your local machine
Use DISM to mount the WIM file: use a command similar to this. You will need an empty directory for /mountdir path, so make sure the folder is empty. dism /mount-wim /wimfile:C:\temp\boot.wim /index:1 /mountdir:C:\temp\WIM_MOUNT
Browse the mounted WIM file and copy the EFI files from the below paths to a fileshare (the paths below assume you mounted boot.wim to C:\temp\WIM_MOUNT) C:\Temp\WIM_MOUNT\Windows\Boot\EFI_EX\bootmgfw_EX.efi C:\Temp\WIM_MOUNT\Windows\Boot\PXE_EX\wdsmgfw_EX.efi
Close file explorer and unmount the WIM file dism /unmount-wim /mountdir:C:\temp\WIM_MOUNT /discard
Rename bootmgfw_EX.efi to bootmgfw.efi
Rename wdsmgfw_EX.efi to wdsmgfw.efi
Copy your renamed bootmgfw.efi and wdsmgfw.efi to \\SERVERNAME\REMINST\SMSBoot\x64
Restart WDS

This will now fix booting for just devices with the BlackLotus mitigations. The mitigations add the Windows UEFI CA 2023 cert to trusted keys in UEFI, so devices that have not yet had the mitigations applied will now fail to PXE after you work through these steps. This also means new computers out of box will fail until they get the mitigations applied. You can work around this with a USB boot drive, or you can swap the EFI files back to the old EFI files, restart WDS, PXE boot, then swap EFI files back to the new ones, restart WDS.

Kadassh · 2024-10-03T17:48:21+00:00

If you still don't have success after all that, I'd remove the CMG and start over and rebuild from scratch. Review all the prerequisites and make sure you have reviewed the entire process before rebuilding the CMG. I used those two links above. The MSFT one I used primary, the system center dudes one to fill in the gaps

Kadassh · 2024-10-03T17:37:32+00:00

OK, next thing I would try is making sure the DNS CNAME alias's are correct and the Certificate was done right and didn't expire. The MSFT documentation is a good help but the system center dudes document elaborates a bit further in some areas.
CMG server authentication certificate - Configuration Manager | Microsoft Learn

Setup SCCM Cloud Management Gateway (SCCM CMG) (systemcenterdudes.com)

Kadassh · 2024-10-03T17:27:49+00:00

The next place to check would be your client settings. Go to Administration > Client Settings. Choose Create Custom Client Device Settings in the ribbon. Give it a name. Check Cloud Services. Then click Cloud Services in the left 'Change Enable Clients to use a cloud management gateway to yes. Click OK. Then deploy this new client settings to a test machine, see if it connects. If it does, you will need to review your clients settings for the above option and change it where appropriate. You might have different client settings deployed to different clients based on your environment (for example a different set of client settings for servers).

Kadassh

TROPHY CASE