SMS and DHCP

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

SMS and DHCP

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> SMS and DHCP

Page: [1]

Message

<< Older Topic Newer Topic >>

SMS and DHCP - 6/6/2008 5:45:24 PM

cdemoss

Posts: 22
Score: 0
Joined: 9/30/2004
Status: offline

Hi, I've been searching for a bit to find the answer to this question, with no success. I hope it's not too dumb for everyone. :)

In our environment, we discovered that we had a dns duplication issue, which was causing some clients to not install properly, and some clients that appeared to work correctly via remote tools when in fact the ip recorded for that client instead redirected to a different client that had remote tools installed. This made me wonder, how often does sms update the ip addresses associated with a client? For example, if client A has a dhcp lease time of eight days, and when it renews it is assigned a different address, how long until sms updates the ip address for this client record?

I'd imagine that the client would write the new dns record to the dns server, which would then dynamically update the active directory, which seems to mean that the client record would be updated at the next active directory system group polling interval.

So anyways, does anyone have a definitive answer to this question?

I appreciate your time. :)

< Message edited by cdemoss -- 6/6/2008 5:46:15 PM >

Post #: 1

RE: SMS and DHCP - 6/7/2008 7:38:51 AM

skissinger

Posts: 1959
Score: 129
Joined: 9/13/2001
From: Sherry Kissinger
Status: offline

Check out this article. Active Directory System Discovery attempts to pull the IP address from DNS first. The client will also report IP addresses via Hardware Inventory. But basically... if DNS is messed up; you are going to have issues (as you've seen).

_____________________________

mofmaster@smsexpert.com (version 2007) | http://www.smsexpert.com | http://www.sccmexpert.com
Microsoft MVP - ConfigMgr

(in reply to cdemoss)

Post #: 2

RE: SMS and DHCP - 6/13/2008 2:15:46 PM

EdwardKK

Posts: 114
Score: 0
Joined: 5/14/2007
Status: offline

This is interesting.

I would have thought that any methods used by SMS to connect to a client would not use IP addresses stored in an SMS database from any discovery, but rather that when you activate remote tools it would do a live DNS look up at that instance. It makes no sense to me that IP information used for connectivity for remote tools or client installation would originate from any information gathered from AD discovery, or even heartbeat discovery. That information might be days out of date, and would be a stupid model for SMS to use for these tools.

I think the reason you're having problems is your DNS isn't right. If you correct yous DNS issues, your remote tools issues will go away.

Am I wrong here?

(in reply to skissinger)

Post #: 3

RE: SMS and DHCP - 6/16/2008 11:45:37 AM

cdemoss

Posts: 22
Score: 0
Joined: 9/30/2004
Status: offline

I agree that storing IPs for clients seems quite odd, especially with the current dns information at the server's disposal. To compensate, I've updated my heartbeat discovery to run every three hours, which should for the most part keep the clients up to date. I think most dns issues have been resolved, and this has been pretty much verified in that most clients now work properly and connect correctly when using remote tools.

Thanks for the assistance.

(in reply to EdwardKK)

Post #: 4

RE: SMS and DHCP - 6/17/2008 2:42:34 PM

amalekani

Posts: 9
Score: 0
Joined: 9/3/2007
Status: offline

Yes, SMS must not be using any gathered information to resolve the IP address, rather it would use the real-time DNS records to resolve the name. DNS issues might be causing u this problem. Did u try resolving the remote machine's IP address and vice versa from the command prompt of the SMS site servers? does it give u correct results?

(in reply to cdemoss)

Post #: 5