Yes, it's SMS because when I tried to upgrade to SCCM in the test environment 
it gave some error about "Setup failed to install SMS provider:"
And there's some setspn command I tried that didn't work, and then I got called 
off that project so we could blow up Exchange via outsourcing it and from there 
other projects have taken over...

Discovery methods...oh hell I don't know I've ever looked (I inherited the SMS 
setup, but other than managing collections/packages/advertisements I don't do 
much in it).
Survey says....
Heartbeat (3 days),
Network (every 2 hours...and I see valid IP ranges),
AD system (our two domains listed) every hour
AD security group (every day).
AD System group (every day)

Brian...I was wrong, there's only two, but often at least one of them is wrong, 
usually the one on LAN (vs. WLAN) since their LAN IP changes if the go to a 
different floor and plug in CAT5.

Dave

From: Rod Trent [mailto:[email protected]]
Sent: Thursday, February 09, 2012 11:49 AM
To: NT System Admin Issues
Subject: RE: SMS chasing clients

First...is this truly SMS, i.e., not ConfigMgr?

Second...what all discovery methods are you using?


Rod Trent<http://myitforum.com/myitforumwp/community/members/rodtrent/>
[cid:[email protected]]<http://www.myitforum.com/>[cid:[email protected]]<http://twitter.com/rodtrent>[cid:[email protected]]<http://www.facebook.com/rodtrent>[cid:[email protected]]<http://www.linkedin.com/profile/view?id=2881785>

From: David Lum [mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Thursday, February 09, 2012 2:00 PM
To: NT System Admin Issues
Subject: SMS chasing clients

At %dayjob% we have users on 5 floors, and each floor has a VLAN assigned. It's 
common for a user to take their laptop to different floors and plug in, so it's 
not uncommon for DNS to have 5 entries for a single machine. What I'm running 
into is the SMS server doesn't always have the correct IP address of its 
clients - sometimes I have to kill some AD entries and then /flushdns on the 
SMS server for SMS to find where the hell the client currently is.

I don't know if changing DNS scavenging will help, or what. Anyone have any 
ideas?
David Lum
Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 503.267.9764


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

<<inline: image001.png>>

<<inline: image002.png>>

<<inline: image003.png>>

<<inline: image004.png>>

Reply via email to