When I do an NSlookup I receive an error, "Can't find server name for address <MY_DNS_SERVERIP>"
Do, it does appear to be a DNS issue? How should i resolve? Thanks, Brian Date: Wed, 15 May 2013 13:10:17 -0700 Subject: Re: [mssms] Automatic Client Discovery Fails From: [email protected] To: [email protected] you can also check clientlocation.log on the client and see site code and MP that is pointing to. So you upgraded/installed this clients and now when you hit auto discovery button in control panel can't find the Site/Server(s)? certainly strange. Most common cost for this is name resolution in my past experiences. On Wed, May 15, 2013 at 11:58 AM, Brian McDonald <[email protected]> wrote: Yes, this has been confirmed except boundaries. Checking on that now. How am I still able to receive adverts? Thanks, Brian Sent from my iPhone On May 14, 2013, at 7:45 PM, "CESAR.ABREG0" <[email protected]> wrote: Can the client resolve the server names, FQDN and netbios? And are boundaries correct. sent from BBFrom: Brian McDonald <[email protected]> Sender: [email protected]: Tue, 14 May 2013 17:25:36 -0500To: [email protected]<[email protected]> ReplyTo: [email protected] Subject: RE: [mssms] Automatic Client Discovery Fails Ok, so I'm using AD sites and Services. I shouldn't require an SLP. So, I should just ignore that error in the LocationServices.log, right? Also, the problem here is when I go into the ConfigMgr in the Control Panel and Advanced the automatic site discovery is unsuccessful. This is what I'm trying to figure out. From: [email protected] To: [email protected] Subject: RE: [mssms] Automatic Client Discovery Fails Date: Tue, 14 May 2013 21:08:04 +0000 Sounds like that client didn’t have a SLP specified during install then. I would assume that’s why the log is showing as no site code returned from SLP. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Tuesday, May 14, 2013 5:00 PM To: [email protected] Subject: RE: [mssms] Automatic Client Discovery Fails The SMSSLP key is blank.... From: [email protected] To: [email protected] Subject: RE: [mssms] Automatic Client Discovery Fails Date: Tue, 14 May 2013 20:55:08 +0000 Whats your SLP showing on the client? Is it correct? Check the below reg key. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\SMSSlp From there, you can query the SLP from that machine and see what its returning: http://novajitz.wordpress.com/2013/01/21/get-sccm-slp-assignment-using-powershell/ http://$slpserver/sms_slp/slp.dll?site&ir=$ipstr $slpserver = Your SLP $ipstr = IP of your client Give that a shot! Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Tuesday, May 14, 2013 4:48 PM To: [email protected] Subject: RE: [mssms] Automatic Client Discovery Fails My SCCM Primary does have write permissions to the Systems Management OU. From: [email protected] To: [email protected] Subject: RE: [mssms] Automatic Client Discovery Fails Date: Tue, 14 May 2013 15:42:36 -0500 Ugh... This hasn't corrected the initial problem, unfortunately. LocationServices.log shows the following: LSGetAssignedSiteFromSLP : No site code returned from SLP :( Brian Date: Tue, 14 May 2013 13:29:47 -0700 Subject: Re: [mssms] Automatic Client Discovery Fails From: [email protected] To: [email protected] BTW, we had some issue with DPs when SMS03 was decommissioned but objects were still published in AD. All our CM07 clients were trying to resolve and get content from our SMS03 DPs. On Tue, May 14, 2013 at 1:21 PM, Marcum, John <[email protected]> wrote: Yep…take away the SMS 2003 servers rights to the container. J From: [email protected] [mailto:[email protected]] On Behalf Of CESAR.ABREG0 Sent: Tuesday, May 14, 2013 2:41 PM To: [email protected] Subject: Re: [mssms] Automatic Client Discovery Fails Your sms03 up and running? If they are, they are publishing their info. sent from BB From: Brian McDonald <[email protected]> Sender: [email protected] Date: Tue, 14 May 2013 14:38:24 -0500 To: [email protected]<[email protected]> ReplyTo: [email protected] Subject: RE: [mssms] Automatic Client Discovery Fails Yes, I did confirm this. Problem is there are instances of old SMS 2003 server on here as well. I deleted these yesterday but looks like they're back now. Not sure why? Date: Tue, 14 May 2013 11:47:24 -0700 Subject: Re: [mssms] Automatic Client Discovery Fails From: [email protected] To: [email protected] SCCM site properties make sure MP and site are publishing to AD and server(s) have write permissions the system management OU. This a presumption that you extended schema for 07. <image001.png> On Tue, May 14, 2013 at 10:41 AM, Brian McDonald <[email protected]> wrote: What exactly should I check in AD? Yes I'm using an SLP and MP. Thanks, Brian Sent from my iPhone On May 14, 2013, at 11:41 AM, "CESAR.ABREG0 ." <[email protected]> wrote: site being published in AD? and name resolution for site system on clients. are you providing SLP or/and MP to clients? On Tue, May 14, 2013 at 8:46 AM, Brian McDonald <[email protected]> wrote: Anyone suggestions on troubleshooting automatic client discovery failure? Thanks, Brian From: [email protected] To: [email protected] Subject: [mssms] Automatic Client Discovery Fails Date: Tue, 14 May 2013 09:21:03 -0500 Hi All, I have several Windows XP SP3 clients in my environment that are showing up as Active and Approved in the SCCM 2007 console, however, Automatic Client Discovery fails. I found instances of my old SMS 2003 (SLP and old Primary Site Server) in AD under the Systems Management Container. This was cleaned up/deleted and the following day I noticed they've come back. LocationServices.log shows the following: LSGetAssignedSiteFromSLP : No site code returned from SLP Thanks, Brian Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
