The ability to tell an SCCM client to IGNORE specific NICS for site determination or SCCM Client communications
The ability to tell an SCCM client to IGNORE specific NICS for site determination or SCCM Client communications.
We have a number of clients that are multi-homed, the SCCM client is often choosing interface that cannot communication with the SCCM infrastructure to determine site membership.
Our clusters fall into this category. 'secure web application servers' that have a "Client Network", "Admin Network", "Backup Network" and "Management Network" connections.
May something similar to the NOSMS file, that will tell the client to not use specific interfaces but continue to inventory, configure, etc.
When a device is out of corporate network working on VPN, the device does receive 2 sets of IP address one local ISP and the other VPN IP address. Now randomly client picks up local ISP address for site assignment and client communication, need an ability to ignore local ip address for site assignment when on VPN.
Mr R Bank commented
After all this time this is still a problem with multi-homed SCCM clients - they end up trying to get content from remote locations due to incorrect boundary matches (home networks for VPN, backup networks etc.). We should be able to set either a primary NIC, or exclude NICs.
Take a look at this blog. This might work for you.