To begin. I'm running SCCM 2007 SP2 using SQL 2005 on a separate server. I currently have Heartbeat and AD System discovery enabled. AD is limited to a specific test OU. All of this seems to be fine. The clients install properly. I can distribute software to them, remote, inventory, etc. I'm new to SCCM so I'm not sure what other configuration info may be of interest at the moment.My problem begins when a clients IP address changes. Shortly after a hardware scan has run, either manually or automatically, the new IP will display in ResourceExplorer but doesn't always show in the client's properties under collections. I'm not sure what updates this, if it's discovery or what, but regardless even once this is updated, SCCM uses DNS to attempt to remote control the machine. I right click the client - click remote tools and I get unable to contact host. If I manually change the DNS entry to the correct IP it will instantly work. My understanding of this is it should be using the IP addresses given it by the client's inventory cycles. This is very problematic internally, but especially externallywith all of my remote users who connect to us through vpn or mpls and are likely to get different addresses every time they connect. DNS also does not track these IPs. Any suggestions would be greatly appreciated. I assume I am at least correct in thinking that SCCM should be using inventory information for client IP and not DNS. Is this a simple client agent setting I am missing..?