Automatic site discovery doesn't work (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message

Peekstra -> Automatic site discovery doesn't work (3/12/2008 4:54:20 AM)

Hi,

as the subject says, I can't get the autodiscovery to work. Previously, it was working though... but I have reinstalled SCCM several times since then. I've checked the following things:

Active directory publishing is enabled (and no errors in any of the component status items)

The sitecomp log states that it is publishing the info (without any error)

The active directory has been succesfully extended

The system management container is present and both the SMS service account AND the computer account have been granted full control to this object and the child objects

The active directory has been added to the site boundaries

I've checked the Sytem Management objects with adsi edit and the correct server name is present (dnshostname).


So at the moment, I've ran out of ideas of what to check next.[&:]

Also, when I previously installed SCCM, I had the client running on several computers, but sofar, only one of them has reappeared as approved while auto approval (in trusted domains) is selected in the configuration setting.

Any help to get the discovery to work again is much appreciated!

thanks!


Peekstra.



rjarrett -> RE: Automatic site discovery doesn't work (3/12/2008 8:33:40 AM)

I had corrupt kerberos tokens once that caused behavior like this.  Test that your site server is really still in the domain.  Create a new Domain User ID.  Logon to the site server using that domain logon.  If you have corrupt kerberos tokens, it will not let you log on.  If not, then you can be fairly confident that your site server is really "alive" in the domain.

The reason it had not been detectable was that I could logon to my SCCM Admin account because its credentials had been cached.  So I was going along, thinking I was logging into the domain when in reality the site server was acting more like it was in a workgroup.

It was weird.  I disjoined/joined the site server to the domain and voila!



Peekstra -> RE: Automatic site discovery doesn't work (3/12/2008 9:29:06 AM)

Just to make sure I've removed the SCCM server from the domain, removed the computer account, and re-added the server again.

This produced some errors because now the new machine account was missing from the system management object. After adding the new account SCCM could update the data without any problems.

Sadly, this didn't solve the problem as the workstation still can't find the SCCM server.

Thanks for the help Rob!


Peekstra.



mhudson -> RE: Automatic site discovery doesn't work (3/12/2008 11:08:57 AM)

If the computer is outside the IP boundary and is only in the AD boundary then discovery will not work.  For instance you have the boundary setup for 127.0.1.1/24 and Test-AD 

If the computer has an ip of 128.x.x.x then it will assign the client but if you cilick on discovery it will fail.  Adding 128.x.x.x. to the boundary list, watiting 5 mins and clicking discovery will work.



rjarrett -> Automatic site discovery doesn't work (3/12/2008 11:36:51 AM)

I believe this also applies to workgroup computers or unknown clients.  If your client has not been joined to the domain, and your SCCM site boundaries are exclusively done by AD sites, I have seen some issues.  For example, if your AD site "Site-192-169-1" is associated with subnet 192.168.1.0 in AD and you use the AD site in SCCM, then you may see certain features not behave as expected. 

Specifically, I have seen some issues with the OSD that seemed to be resolved by adding a "second" boundary in SCCM.  When I add an "AD Site" called "Site-192-168-1" and an "IP Boundary" of 192.168.1.0 to the site boundaries, things started working.  Again, this was OSD troubleshooting, not site discovery.

You could easily test that theory by adding the IP Boundary for the client you are testing and see if it corrects the problem.



Peekstra -> RE: Automatic site discovery doesn't work (3/12/2008 12:24:32 PM)

Does a workstation need to be logged in to the domain for autodiscovery to work? I just found out that autodiscovery works fine at my two Vista systems.

Until now I had only checked our XP stations when logged in as a local administrator. The access rights on the system management object allow readonly access for anonymous users so that should work...?

Rob: I had already tried adding a second boundary.

Matthew: I'm currently only using an active directory boundary.

thanks,

Peekstra.



lcpc78 -> RE: Automatic site discovery doesn't work (3/13/2008 11:55:19 AM)

I couldn't find it in your posts,  but what discovery method are you using?  I'm a little unclear on what "autodiscovery" method you are referring to.  If you don't select on of the following discovery methods:

AD System Group
AD Security Group
AD System
AD User
Heartbeat
Network

Chances are you won't get anything to discover.  Have you checked to see which of these discovery methods are enabled since you reloaded SCCM?  I typically configure AD System Discovery and Heartbeat.  When I configure the AD System I throw in the entire domain so it will find all the systems.  Hope this helps.




Peekstra -> RE: Automatic site discovery doesn't work (3/17/2008 7:14:01 AM)

Maybe that was unclear in my first post: I meant autodiscovering the SCCM server at the client.

Thanks.



lcpc78 -> RE: Automatic site discovery doesn't work (3/17/2008 10:28:55 AM)

Ah..I see what you mean now.  Anything out of the ordinary in your locationservices.log or clientlocation.log? 

Luis



rjarrett -> Automatic site discovery - Workgroup Computers (3/17/2008 10:58:46 AM)

To follow up on the Workgroup thread.  I cannot answer your question definitively, but I have some feed back.  You asked, "Does a workstation need to be logged in to the domain for autodiscovery to work?"  No!

My Client
I started with a Workgroup computer on the 192.168.1.0 subnet. 

My Site Server
My SCCM site had one "AD Site" which corresponded to the 192.168.1.0 subnet. 
There were no "IP boundary" boundaries. 
My site server had the Server Locator Point service installed 
WINS was not configured with the Server Locator Point entry.

My Tests

Test 1.  I attempted auto discovery with my "workgroup only" machine.  No success.

Test 2:  I added the SLP alias to WINS via http://support.microsoft.com/kb/883620.  I then added the "IP Boundary" of 192.168.1.0/255.255.255.0 to my site server's boundaries.  I attempted auto discovery on my "workgroup only" only machine.  Success.
 
I should have added an intermediate step of just adding the IP Boundary, but I was not thinking ahead.  I suspect it was strictly the boundary that did the trick, but it could have been the SLP or a combination.



Peekstra -> RE: Automatic site discovery doesn't work (3/17/2008 11:09:31 AM)

I've looked into the logs from a client which I just installed from the SCCM console. The client says that it is assigned to the correct site, but discovery fails.

The LocationServices.log says:

Persisting the management point authentication information in WMI]LOG]!><time="15:07:46.361+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3800" file="lssecurity.cpp:763">

<![LOG[Persisted Management Point Authentication Information locally]LOG]!><time="15:07:46.393+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3800" file="lssecurity.cpp:770">

<![LOG[Attempting to retrieve default management point from AD]LOG]!><time="15:48:51.386+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3856" file="lsad.cpp:2537">

<![LOG[Retrieved Default Management Point from AD:  *** my server name ***]LOG]!><time="15:48:51.635+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3856" file="lsad.cpp:2543">

<![LOG[Persisting the default management point in WMI]LOG]!><time="15:48:51.635+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3856" file="lsad.cpp:3850">

<![LOG[Persisted Default Management Point Location locally]LOG]!><time="15:48:51.666+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3856" file="lsad.cpp:3863">

<![LOG[Attempting to retrieve proxy MP from AD]LOG]!><time="15:48:51.728+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3856" file="lsproxymp.cpp:938">

<![LOG[Unknown task LSProxyMPModificationTask in non-quarantine - ignoring.]LOG]!><time="15:48:51.759+-60" date="03-17-2008" component="LocationServices" context="" type="2" thread="2364" file="scheduledcleanupendpoint.cpp:404">

<![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="15:48:51.759+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3856" file="lsad.cpp:457">

<![LOG[Retrieved Proxy Management Point from AD: *** my sccm server name ***]LOG]!><time="15:48:51.790+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3856" file="lsproxymp.cpp:945">

<![LOG[Unknown task LSProxyMPModificationTask in non-quarantine - ignoring.]LOG]!><time="15:48:51.822+-60" date="03-17-2008" component="LocationServices" context="" type="2" thread="404" file="scheduledcleanupendpoint.cpp:404">

<![LOG[Attempting to retrieve local MP from AD]LOG]!><time="15:48:51.837+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3856" file="lsad.cpp:3778">

<![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="15:48:51.837+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3856" file="lsad.cpp:457">

<![LOG[Retrieved local Management Point from AD: sccm.nuffic.nl]LOG]!><time="15:48:51.853+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="3856" file="lsad.cpp:3790">

<![LOG[DhcpGetOriginalSubnetMask entry point not supported.]LOG]!><time="15:49:41.813+-60" date="03-17-2008" component="LocationServices" context="" type="2" thread="2988" file="ccmiputil.cpp:169">

<![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="15:49:41.813+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="2988" file="lsad.cpp:457">

<![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="15:49:41.906+-60" date="03-17-2008" component="LocationServices" context="" type="1" thread="2988" file="lsad.cpp:2261">

<![LOG[Failed to resolve 'SMS_SLP' to IP address from WINS]LOG]!><time="15:49:50.949+-60" date="03-17-2008" component="LocationServices" context="" type="3" thread="2988" file="lswins.cpp:324">

<![LOG[LSGetSLP : Failed to resolve SLP from WINS, is it published]LOG]!><time="15:49:50.949+-60" date="03-17-2008" component="LocationServices" context="" type="3" thread="2988" file="lsad.cpp:2277">

<![LOG[LSGetAssignedSiteFromSLP : Unable to get the list of SLPs

Which seems ok to me (I don't use WINS)

And from the clientlocation.log:

![LOG[Current Management Point is sccm.nuffic.nl with version 5931 and capabilities: <Capabilities SchemaVersion="1.0">

</Capabilities>.]LOG]!><time="15:07:46.457+-60" date="03-17-2008" component="ClientLocation" context="" type="1" thread="3024" file="smsclientclass.cpp:1094">

<![LOG[GetCurrentManagementPointEx]LOG]!><time="15:40:28.195+-60" date="03-17-2008" component="ClientLocation" context="" type="1" thread="2364" file="smsclientclass.cpp:1039">

<![LOG[Current Management Point is *** our sccm server *** with version 5931 and capabilities: <Capabilities SchemaVersion="1.0">

</Capabilities>.]LOG]!><time="15:40:28.226+-60" date="03-17-2008" component="ClientLocation" context="" type="1" thread="2364" file="smsclientclass.cpp:1094">

<![LOG[GetCurrentManagementPointEx]LOG]!><time="15:41:04.831+-60" date="03-17-2008" component="ClientLocation" context="" type="1" thread="2364" file="smsclientclass.cpp:1039">

<![LOG[Current Management Point is sccm.nuffic.nl with version 5931 and capabilities: <Capabilities SchemaVersion="1.0">

</Capabilities>.]LOG]!><time="15:41:04.878+-60" date="03-17-2008" component="ClientLocation" context="" type="1" thread="2364" file="smsclientclass.cpp:1094">

<![LOG[Getting Assigned Site]LOG]!><time="15:49:39.525+-60" date="03-17-2008" component="ClientLocation" context="" type="1" thread="2988" file="smsclientclass.cpp:922">

<![LOG[Assigned Site is NUF]LOG]!><time="15:49:39.540+-60" date="03-17-2008" component="ClientLocation" context="" type="1" thread="2988" file="smsclientclass.cpp:933">

<![LOG[Autodiscover Site]LOG]!><time="15:49:41.813+-60" date="03-17-2008" component="ClientLocation" context="" type="1" thread="2988" file="smsclientclass.cpp:1310">


I think the clients themselves are working fine (as the logs indicate), but it's only the autodiscovery which isn't working when logged in as a local administrator.


Peekstra



Peekstra -> RE: Automatic site discovery doesn't work (3/17/2008 11:44:25 AM)

Thanks for testing rjarrett! It's good to know that autodiscovery should work when not logged in. I've re-added the IP boundary (next to the AD boundary) but the autodiscovery still fails.

So I think that WINS is doing the trick here because that information is available without being logged in to the domain?



rjarrett -> Automatic site discovery - Updated Results (3/17/2008 2:05:58 PM)

My Client
I started with a Workgroup computer on the 192.168.1.0 subnet. 

My Site Server
My SCCM site had one "AD Site" which corresponded to the 192.168.1.0 subnet. 
There were no "IP subnet" boundaries assigned. 
My site server had the Server Locator Point service installed. 
WINS was not configured with the Server Locator Point entry.

My Tests

Test 1.  I attempted auto discovery with my "workgroup only" machine.  No success.

Test 2.  I added the "IP subnet" of 192.168.1.0/255.255.255.0 to my site server's boundaries and attempted auto discovery with my "workgroup only" machine.  No success.

Test 3:  I removed the "IP subnet" boundary and added the SLP alias to WINS via http://support.microsoft.com/kb/883620.  I attempted auto discovery on my "workgroup only" only machine.  No success.  

Test 4:  I added the "IP subnet" boundary and the SLP WINS alias and then attempted auto discovery on my "workgroup only" only machine.  Success. 

While not definitive, it seems that both are required for workgroup based machines.  Does anyone have any other input?



Peekstra -> RE: Automatic site discovery - Updated Results (3/18/2008 4:21:32 AM)

Rob, I'm not able to test this as I can't add WINS to my production environment.

I wish that one of the client logs would indicate what is going on here. The clientlocation.log only seems to contain entries with the end-user being logged in, not of my manual discovery attempts.



rjarrett -> RE: Automatic site discovery - Updated Results (3/18/2008 11:28:20 AM)

Peek,

I may have missed it in the thread.  Is your client a workgroup or AD client? 



Peekstra -> RE: Automatic site discovery - Updated Results (3/18/2008 12:03:33 PM)

All our clients are AD members.



rjarrett -> RE: Automatic site discovery - Updated Results (3/18/2008 3:57:56 PM)

Alright.  That eliminates the need for pursuing the SLP thread any further. 

My remaining thoughts center on your client IP/Subnet Mask and your SCCM boundaries, but I will have to think on it.



Peekstra -> RE: Automatic site discovery - Updated Results (3/19/2008 10:06:33 AM)

Rob, it really isn't a big problem for me as the clients are working just fine. I'm still curious though why this error is happening.



rjarrett -> Workgroup Computers (3/24/2008 1:43:46 PM)

Peekstra,

I realize you are onto bigger and better things, but for those who may have had troubles with auto discovery, this link contains the details about when an SLP is/is not required.  So, I thought I would post it for reference.

http://technet.microsoft.com/en-us/library/bb693467.aspx

You do not need to install a server locator point if both of the following conditions apply:
  • You have extended the Active Directory schema for Configuration Manager 2007, and all sites in the hierarchy are published to Active Directory Domain Services.
  • You do not manage either workgroup clients or clients from another forest.

Install a server locator point if either of the following conditions applies:
  • You have not extended the Active Directory schema for Configuration Manager 2007 or not all sites in the hierarchy are published to Active Directory Domain Services.
  • You have workgroup clients or clients from another forest.





Peekstra -> RE: Workgroup Computers (3/25/2008 4:21:26 AM)

Thanks again for the info Rob! I've removed the SLP because I qualify of running without one as your technet info explains.

The "discovery unsuccesfull" message when logged in as the local admin still remains however.



betemtl -> RE: Automatic site discovery doesn't work (4/10/2008 11:20:47 AM)

Hello,

I am having the same problem here that my client on a workgroup can't discover the SCCM server in a domain, once it joins the domian, it discovers it sucessfully. I got same errors in the logs as Peekstra mentioned above. According to your previous testing, should I have wins server to make that work?

As I know, being in a workgroup is nesseccary to make an image using OSD.

Thanks



rjarrett -> RE: Automatic site discovery doesn't work (4/10/2008 1:21:57 PM)

Don't confuse OSD requirements with client requirements.  The OSD will image a machine in one of three ways:
  1. PXE.  In which the machine boots up, gets its DHCP information, contacts the PXE server, downloads the boot image, boots, and then runs the imaging Task Sequence.  The WinPE boot creates a random computer name and does enough to make the PXE imaging server happy with its credentials.  The Task Sequence then image the machine and either joins the machine to the domain or leaves it in a workgroup.  It then installs the client.  If the Task Sequence is designed to join the new client to the domain, then you should get auto site code configuration.  If the client is left in a workgroup, then you will need "workgroup" support for clients.  (See previous posts about Server Locator Point and WINS).
  2. Network.  In this case, you use a boot image that boot straps the logon from the client, bypassing the PXE part.  Basically, it does the same things in the imaging process.
  3. Standalone.  The whole image is installed from an ISO or disk.  See Item 2, except it gets the image file locally.

By contrast, the client requires either AD or and SLP to complete its installation.  When a client is in AD, it should install and configure without problem.  When a client is in a workgroup, it needs help finding SCCM from WINS. 

In summary, the OSD has a whole pre-image infrastructure to handle machines that are not in the domain.  It then brings the client up to the point where it either uses AD or WINS to establish communication with its site server.  Whereas existing machines can simply pick-up with talking to AD or WINS for their communication requirements.



betemtl -> RE: Automatic site discovery doesn't work (4/10/2008 2:17:58 PM)

Thanks rjarrett for your promot respond. What we are doing here is PXE way for OSD. According to the steps in the book, we should have the SCCM client installed on the reference PC which will capture the image from, and that PC should be in a workgroup not in a domain. The problem is: when you try to discover the site while you are in a workgroup it gives me unsuceessful message.

and I confirmed that from two books that the PC shouldn't be in the domain and it should be in the workgroup to capture an image. Then after that you add it to the domain using the task sequance.



betemtl -> RE: Automatic site discovery doesn't work (4/11/2008 5:34:45 PM)

I got it working now. There was no need to have sms client on the reference PC.



rjarrett -> RE: Automatic site discovery doesn't work (4/15/2008 10:23:30 PM)

Good to hear.  This post shows a modified graphic that explains the real flow.

http://www.myitforum.com/forums/m_174880/mpage_1/key_/tm.htm#175083



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.2666016