joeman1881 Posted August 27, 2014 Report post Posted August 27, 2014 I am sure this is somewhere else on the forum, but I am having trouble finding a solution. When a machine is issued a new address via dhcp, sccm doesn't see the change immediately. This makes it so the server cannot communicate with the clients for what I'm told is a few hours/days. I haven't been able to confirm the wait time on this, but shouldn't Delta discoveries pick up new addresses? This becomes an issue when my technicians deploy a machine and attempt to reconnect at a later time for a last minute push of an application. The server still has the old address recorded so when I even try to ping from the console extensions, I do not get a reply even though server itself can ping the machines. We run into this often with wireless devices, and machines that haven't been turned on within the lease period. Does anyone run into this, or is there a way to keep the console more current with issued IP's? Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted August 27, 2014 Report post Posted August 27, 2014 No delta discovery will have nothing to do with IP Address. The site server will not initiate communicate with the PC, unless you are trying to push the CM12 client to the server. Remember that is the CM12 client that imitate all communications not he site server. If you can't ping the PC using it's name and get the right IP address for it then you have a DNS issue. Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted August 27, 2014 Report post Posted August 27, 2014 No delta discovery will have nothing to do with IP Address. The site server will not initiate communicate with the PC, unless you are trying to push the CM12 client to the server. Remember that is the CM12 client that imitate all communications not he site server. If you can't ping the PC using it's name and get the right IP address for it then you have a DNS issue. I shouldn't have a DNS issue because I can ping the machines successfully from the server itself and/or any other machine in the domain. I cannot ping the devices using console extensions and I can see it attempting to connect using the last recorded/discovered IP address not a DNS name. Eventually the console realizes that the IP has changed, but I am not sure what event kicks off this update of current addresses. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted August 27, 2014 Report post Posted August 27, 2014 What console extension are you talking about? Really this is a question for the person that wrote the console extension as to why they are not using the NetBIOS name or FQDN and are they using the data from HW inv or Heartbeat inv. If I had to guess it would be heartbeat. Quote Share this post Link to post Share on other sites More sharing options...
