This isn't anything tracked by the site explicitly. You'll be able to see this in two different logs though: MP_Location.log and the IIS logs on the MP.
What challenge are you attempting to address?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Does anyone know how to get the IP address that the CM client used/uses to communicate with the MP?
Please do not reply on how to use v_GS_NETWORK_ADAPTER_CONFIGUR. That just returns all IP addresses for the operating system network cards.
Thank you, in advance.
This isn't anything tracked by the site explicitly. You'll be able to see this in two different logs though: MP_Location.log and the IIS logs on the MP.
What challenge are you attempting to address?
Thank you for the reply. I was concerned this might be the case. We require this information for so many reasons, including, but not limited to:
I have not found anything in the product that emphatically states the IP address used for communication. Instead, most posts reference a guesswork technique where they grab all NIC data, then manually remove what is perceived to not be the correct NIC. Truly, sad and unfortunate.
This seems like such a basic inventory item that should be captured for even the most basic of reporting.
Thank you, again, for the quick reply. Much appreciated.
Cheers
The problem is that Windows itself doesn't track (or know really) which IP is used to send network traffic. All Windows itself knows is which IPs are assigned to which NICs. And this is exactly what is sent to ConfigMgr using hardware inventory and heartbeat discovery.
Thus, there really is no way, from the client's perspective to be able to report this.
What's the scenario where this is an issue though? Is this for clients connecting over VPN and thus have multiple IPs?