SCCM 2012R2 multihomed client, Wake on LAN unreliable

We are seeing a strange problem related to Wake on LAN on client computers with both wired and wireless network interfaces.

All clients are initially imported with the wired MAC address, booted via PXE and image installed. The client then boots up and contacts SCCM. End users then typically use them via wireless and one would expect SCCM to "learn" both the IP/MAC configuration of the wired and the wireless interfaces. (These networks use separate vlans and IP subnets)

SCCM and our routers are configured for directed broadcasts.

Network sniffing has confirmed that for these clients, SCCM attempts to send the broadcast to the wifi subnets instead of the wired subnets. All directed broadcasts sent to wired subnets have been confirmed to arrive as expected and those clients wake up as expected.

However, over time the wired network interface appears to be dropped by SCCM, causing Wake on LAN to fail because it obviously won't work using the IP/MAC information for the wireless adapter. When checking the client properties in Configuration Manager, some clients are incorrectly listed without a wired network interface.

How should we proceed to troubleshoot this issue? Any pointers/ideas/suggestions are welcome.

February 18th, 2015 9:05am

"one would expect SCCM to "learn" both the IP/MAC configuration of the wired and the wireless interfaces."

Why would one "expect" this?

ConfigMgr uses heartbeat discovery to discover IP address information. What is your heartbeat discovery interval set to?

Free Windows Admin Tool Kit Click here and download it now
February 18th, 2015 9:53am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics