r/SCCM • • 1h ago

Unsolved :( System.Net.WebException: Unable to connect to the remote server (WSUS error)

Post image
1 Upvotes

Hello,

For the past few days, we have been seeing errors in our MECM environment in both WCM.log and wsyncmgr.log stating that the site server is unable to establish a remote connection to the WSUS server.

The issue appeared suddenly. The last successful synchronization was working normally, and approximately one hour later the synchronization started failing without any known changes being made to the MECM or WSUS configuration.

According to the logs, the primary site server can no longer connect to the Software Update Point (SUP) where WSUS is installed. The error reported is essentially:

"Remote connection failed" / "Unable to connect to the remote server"

We have already verified the following:

  • WSUS services are running.
  • IIS is running correctly.
  • The WSUS website is bound to HTTPS on port 8531.
  • The WSUS server is actively servicing clients and has many established connections on port 8531.
  • The SSL certificate is valid and not expired.
  • DNS resolution works correctly between the servers.
  • Both servers are located in the same subnet (10.100.206.0/24).
  • ARP resolution works correctly between the two servers.

However, the following behavior is extremely unusual:

  • The primary site server and the SUP server can no longer ping each other.
  • TCP connections between the two servers fail in both directions.
  • Test-NetConnection to port 8531 fails from the site server.
  • Even SMB/RPC related ports such as 445 and 135 cannot be reached between these two servers.
  • Other servers in the environment can successfully reach the SUP server.
  • WSUS clients can still connect to the SUP and are actively communicating with it.

We also tested Windows Firewall rules and even created explicit allow rules between the two servers, but the behavior did not change.

At this point, the issue does not appear to be related directly to WSUS, IIS, certificates, or DNS. It looks more like a communication problem that affects only these two specific servers, despite them being in the same subnet.

Has anyone experienced something similar before, or are there any additional areas (VMware networking, NSX, endpoint security, Windows networking, etc.) that we should investigate?

Thanks.


r/SCCM • • 8h ago

ARM64 OSD - T14s Gen 7 won't boot WinPE 26100, but WinPE 28000 works

1 Upvotes

I’m starting to look at ARM64 imaging for the first time and currently only have one ARM device to test with, a Lenovo ThinkPad T14s Gen 7.

Our environment is ConfigMgr 2603 with KB39398030 and KB3794246 installed. I upgraded our ADK to 10.1.26100.9457 with the matching WinPE add-on. The WinPE included with this ADK is 10.0.26100.1. I created a separate ARM64 boot image and assigned it to an ARM test task sequence.

When PXE booting the T14s, I verified in SMSPXE.log that ConfigMgr sees the ARM architecture (Client Arch: 000b / architecture 12), selects the ARM64 boot loader (smsboot\arm64\bootmgfw.efi), and selects my ARM64 boot image. The boot image loading bar gets to the end, the screen goes black, the Lenovo splash screen appears again, and the computer then boots back into the installed Windows OS and displays the Windows logon screen.

I tested the SCCM ARM64 boot image both with and without Lenovo’s WinPE driver package for the T14s Gen 7. I also created SCCM bootable USB media using the ARM64 image and had the same result.

To take ConfigMgr completely out of the equation, I created multiple vanilla ARM64 WinPE USB media directly from the ADKs:

  • ADK 10.1.26100.9457 / WinPE 10.0.26100.1: will not boot. The image loads, the screen goes black, the Lenovo splash screen appears again, and the computer falls back to the installed Windows OS.
  • WinPE 10.0.26100.1 + Lenovo’s ARM WinPE drivers: same result.
  • WinPE 10.0.28000.1: successfully boots into WinPE, reaches a command prompt, and sees the internal SSD.

So with standalone, non-SCCM USB media, this T14s will boot into WinPE when the media is built from the 28000 ADK/WinPE, but it will not boot into WinPE when built from the supported 10.1.26100.9457 ADK / WinPE 10.0.26100.1.

A few other things I’ve ruled out:

  • Secure Boot has been tested both enabled and disabled with the same result.
  • For the ConfigMgr boot image, I tested Use Windows Boot Loader signed with Windows UEFI CA 2023 both enabled and disabled.
  • The T14s Gen 7 is running the latest Lenovo BIOS.

Microsoft currently lists ADK 26100.x as supported with ConfigMgr, while the 28000 branch is not currently listed as supported with any ConfigMgr Current Branch release. I’m reluctant to move our ConfigMgr environment to 28000 when Microsoft currently shows it as unsupported.

Has anyone else run into newer ARM hardware that won’t boot the supported 26100 ARM64 WinPE but will boot 28000? Is anyone currently using 28000 WinPE/ADK with ConfigMgr OSD despite it not currently being supported?

Any other thoughts, tips, or things I should try with 26100 would also be appreciated. I’d also be interested in experiences with this particular T14s Gen 7, or recommendations for another Lenovo or Dell ARM model that might be a better device to test with. We’re a Lenovo/Dell shop, so I’d prefer to stay with one of those vendors if I pick up another ARM device for testing.