I've tried everything I can from reading various forum posts to technet docs but can't seem to get this to work. The ConfigMgr Client won't show a "Connection Type" and it won't populate the Site Code. I've attached a screenshot of the log file (LocationServices.log). Any insight would be greatly appreciated. I have boundaries defined, AD network discovery is enabled, I can't think of what's causing the problem. Thanks!

Hey AdrianKeithM The client is not able to get site information from AD or SLP. Maybe the site information is not published in AD. Clients will need this information for registration. Check out this link http://www.madanmohan.com/2010/10/how-to-make-sure-smssccm-site.html. Moiz

As Moiz has mentioned, it seems your clients do not know where to look for a management point. This is easily fixed. Has your AD Schema been extended? Read this documentation for more information: http://technet.microsoft.com/en-us/library/bb633121.aspx Alternatively, a Server Locator Point can be implemented, and clients can be reinstalled with the SMSSLP=[servername] parameter. This documentation will guide you through configuring a server locator point: http://technet.microsoft.com/en-us/library/bb680672.aspx Cheers.LinkedIn

I think we stayed away from extending the AD schema because of some issues that it would pose (according to the team we're working with) so we implemented the SLP but that doesn't seem to be working either (obviously). Does that site (madanmohan.com) still pertain to my issue if we haven't extended the AD schema? Thanks for the responses guys. This has been a headache and the hosting company doesn't seem to have someone specialized enough in SCCM/FEP deployment and so we've been floundering with minimal (if any) coverage. I need to get this figured out. I have ZERO experience with SCCM/FEP so any and all guidance would be great. -- Just an edit, I'm already using the SMSSLP parameter, so that should be fine. It worked at one point but all of a sudden it stopped working. Thanks again guys.

No problems AdrianKeithM, we'll get it sorted, I'm sure. When you are on a client, and go to Control Panel and then into Configuration Manager, does it display a site code? Does it say 'Intranet Only' or 'Internet Only' next to connection type? If you have your SMSSLP Installed and are installing clients with the SMSSLP parameter, the only other real thing that would stop clients from discovering is if the clients are not falling under a site. Have you got boundaries configured? When you are viewing a collection, do the clients have anything listed under 'Site' ? Cheers. PS: unless you are currently experiencing significant problems with active directory, replication or otherwise, extending the AD Schema is not going to cause any problems, and it is generally better than using an SLP. LinkedIn

I think we stayed away from extending the AD schema because of some issues that it would pose (according to the team we're working with) I'd be very interested in what issues this team believe would be encountered by extending the schema. While the shema extension is not mandatory, it is highly recommended.

can you check if you are getting the SLP server name in the registry entry : - HKEY_LOCAL_MACHINE SOFTWARE\Microsoft\CCM\ If you are not then add the registry and try running the discovery and check the log.

Hi AdrianKeithM, Can you post your client installation commandline where you are using the SMSSLP parameter ? Thanks,

Hi , 1. Try to Telnet from sccm cleint machine to SCCM server and check if it is able to connect. 2. Check the CertifcateMaintance.log on client machine to confirm the communication with AD and MP. If you see any error related to MP try this you can do a quick check to see if MP server is responding to http or not: http://MP-server-name:portnumber/sms_mp/.sms_aut?MPcert http://MP-server-name:portnumber/sms_mp/.sms_aut?MPlist where the "portnumber" is the http port number configured in IIS for your MP server. By default it's "80" but it could be changed to something else by your administrator. You need to find it out first from IIS configuration. 3. Make sure that Client are approved in the console. 4. Try to ping SLP , MP and AD server that client is using for commuication.

I think we stayed away from extending the AD schema because of some issues that it would pose (according to the team we're working with) so we implemented the SLP but that doesn't seem to be working either (obviously). Does that site (madanmohan.com) still pertain to my issue if we haven't extended the AD schema? Thanks for the responses guys. This has been a headache and the hosting company doesn't seem to have someone specialized enough in SCCM/FEP deployment and so we've been floundering with minimal (if any) coverage. I need to get this figured out. I have ZERO experience with SCCM/FEP so any and all guidance would be great. -- Just an edit, I'm already using the SMSSLP parameter, so that should be fine. It worked at one point but all of a sudden it stopped working. Thanks again guys. There is zero reason not to extend the AD Schema, we've been doing this since SMS2003 and is well understood. You will find the team who said this either have a really screwed up AD (Their fault) and they are hesitant to touch it (they need to hire skilled consultants or do the work to stabilise their AD if this is an issue) or they just cannot be bothered so fob you off. There are alternatives though. Look at the documentation, I know it may seem daunting but you have focus via this forum on what to look at ... http://technet.microsoft.com/en-us/library/bb693467.aspx http://technet.microsoft.com/en-us/library/bb680980.aspx http://technet.microsoft.com/en-us/library/bb694195.aspx http://technet.microsoft.com/en-us/library/bb632435.aspx You must read this stuff to get enough edge to administer this product :-)

HI Schema need to be extended its highly recommending if your discovery method is AD(please share exadsch.log and CCM log) services prerequisites for client computer should meet SQL working/running with proper credential and also check SQL services property and ensure showing proper account logon user name and password check site system role then management point property and connection type (HTTP or HTTPS) if you are not using PKI then please select HTTP IN sccm 2012 SLP has been integrated with MP role if failed all above mentioned steps remove and add MP role again after extending schema

Hi AdrianKeithM, Login in to SLP Server and Open Event Manager click System and check for DCOM errors Error Sample: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D452CB77-FB08-4CB3-B7EE-2F5369982BBE} to the user Server1\IUSR_Server1 SID (S-1-5-21-3497608462-2776652222-1368968922-1003). By seeing my sample, you need to give DCOM permission to "Server1\IUSR_Server1" or the SID "(S-1-5-21-3497608462-2776652222-1368968922-1003)" same way you need to find the user name in your server and provide permission using the below instruction. 1. Click Start -> Run -> Type -> dcomcnfg, expand Component Services -> Computers -> My Computer -> DCOM Config. 2. Scroll down and find the application (SMS_SERVER_LOCATOR_POINT) Right Click -> Properties and select the Security tab. 3. Click Customize under "Launch & Activation Permission" -> click Edit -> Add in the account found in Event Log and set local and remote activation 4. Restart IIS and check in the client side now to verifiy. _________________________ . Ur's -> SithaYuvaraj

Did you fix this Adrian?