locked
SCCM 2012 agent installations fail to find a Site to be Manage RRS feed

  • Question

  • We have SCCM 2012 for some years, with many clients working properly. The problem occurs for with the new agent installations, which are installed correctly but fail to find a Site to be Manage. It is the same problem with manual installations and sent agent with the management console.

    What is what might be causing this problem?

    When trying to enter the site manually: Configuration Manager did not find a site to manage this client

    Upon entering from the client to the address https: //nameserver/sms_mp/.sms_aut MPLIST working properly.

    ClientLocation.log:
    Unable to verify sitecode 'P03'. Cannot continue site assignment. ClientLocation 30/9/2016 4:31:11 p. m. 2808 (0x0AF8)

    ccmsetup.log:
    Failed to get site version from AD with error 0x87d00215 ccmsetup 30/9/2016 4:07:20 p. m. 3312 (0x0CF0)

    I will be grateful for your help, if you need more information please let me know.
    Monday, October 3, 2016 5:50 PM

All replies

  • Hello

    I would ask you to check your Boundary Groups and make sure you have one set up for "Use this boundary group for site assignemnt" in the references tab of your boundary group.  If you want to test assignment without using a boundary group, you can hard code the assigment to a management point by using the manual installation command:  CCMSETUP.exe SMSSITECODE=ABC SMSMP=SERVERNAME.FQDN.COM.  That should get it assigned without boundary groups needed to make sure that it's not an assignment issue.

    That may help you get a bit more information to help troubleshooting.


    Regards, Regin Ravi

    Monday, October 3, 2016 6:02 PM
  • Those snippets are useless. Please post the entire relevant portions of the two log files.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, October 3, 2016 6:57 PM
  • Hi ReginRavi
    thanks for your answer

    I already create boundary group for site assignemnt & I use this comand to install the agent:

    CCMSetup.exe /mp:Nameserver /logon SMSSITECODE=P03. 

    the agents install correctly but still cannot find the Site.

    I detected the antivirus is blocking SMSEXEC.EXE, I have created exceptions but still blocking
    Blocked by Access Protection rule            NT AUTHORITY\SYSTEM               E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\BIN\X64\SMSEXEC.EXE

    Is this necessary for assignment the Site?

    Monday, October 3, 2016 7:55 PM
  • ClientLocation.log

    Getting Assigned Site ClientLocation 30/9/2016 4:16:15 p. m. 280 (0x0118)
    Getting Assigned Site ClientLocation 30/9/2016 4:16:16 p. m. 3560 (0x0DE8)
    Autodiscover Site ClientLocation 30/9/2016 4:16:20 p. m. 3560 (0x0DE8)
    Client is set to use HTTPS when available. The current state is 224. ClientLocation 30/9/2016 4:16:20 p. m. 3560 (0x0DE8)
    Getting Assigned Site ClientLocation 30/9/2016 4:19:09 p. m. 3952 (0x0F70)
    Getting Assigned Site ClientLocation 30/9/2016 4:19:10 p. m. 2808 (0x0AF8)
    Autodiscover Site ClientLocation 30/9/2016 4:19:17 p. m. 2808 (0x0AF8)
    Client is set to use HTTPS when available. The current state is 224. ClientLocation 30/9/2016 4:19:17 p. m. 2808 (0x0AF8)
    Getting Assigned Site ClientLocation 30/9/2016 4:30:26 p. m. 2232 (0x08B8)
    Getting Assigned Site ClientLocation 30/9/2016 4:30:27 p. m. 4020 (0x0FB4)
    Getting Assigned Site ClientLocation 30/9/2016 4:30:41 p. m. 2148 (0x0864)
    Getting Assigned Site ClientLocation 30/9/2016 4:30:42 p. m. 2808 (0x0AF8)
    Autodiscover Site ClientLocation 30/9/2016 4:30:46 p. m. 2808 (0x0AF8)
    Client is set to use HTTPS when available. The current state is 224. ClientLocation 30/9/2016 4:30:46 p. m. 2808 (0x0AF8)
    Assigning client to site 'P03' ClientLocation 30/9/2016 4:30:53 p. m. 2808 (0x0AF8)
    Unable to verify sitecode 'P03'. Cannot continue site assignment. ClientLocation 30/9/2016 4:31:11 p. m. 2808 (0x0AF8)
    Getting Assigned Site ClientLocation 30/9/2016 4:31:52 p. m. 3604 (0x0E14)
    Getting Assigned Site ClientLocation 30/9/2016 4:31:53 p. m. 808 (0x0328)
    Autodiscover Site ClientLocation 30/9/2016 4:31:58 p. m. 808 (0x0328)
    Client is set to use HTTPS when available. The current state is 224. ClientLocation 30/9/2016 4:31:58 p. m. 808 (0x0328)
    Autodiscover Site ClientLocation 30/9/2016 4:32:04 p. m. 808 (0x0328)
    Getting Assigned Site ClientLocation 30/9/2016 4:33:59 p. m. 3872 (0x0F20)
    Getting Assigned Site ClientLocation 30/9/2016 4:34:00 p. m. 1292 (0x050C)
    Autodiscover Site ClientLocation 30/9/2016 4:34:03 p. m. 1292 (0x050C)
    Client is set to use HTTPS when available. The current state is 224. ClientLocation 30/9/2016 4:34:03 p. m. 1292 (0x050C)


    Monday, October 3, 2016 8:13 PM
  • Are you using HTTPS client communication?

    Do you have AD extended and is the site information properly published in AD?

    How exactly are you installing the agent?

     


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, October 3, 2016 8:20 PM
  • /mp does *not* set the management point to use by the client. Setting the SMSMP property does this.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, October 3, 2016 8:21 PM
  • Hi Jason

    • Im using HTTP client communication 
    • I install the agent manual by the comand: CCMSetup.exe /mp:Nameserver /logon SMSSITECODE=P03
    • i try to install by client push installation.

    I need to check if the AD extended and if the site information is published in AD, I find it strange that clients who are already installed are working properly.

    Monday, October 3, 2016 9:09 PM
  • ccmsetup.log is irrelevant as you are well past installing the client agent.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, October 3, 2016 9:09 PM
  • I will try with that command, thanks.
    Monday, October 3, 2016 9:11 PM
  • > "I find it strange that clients who are already installed are working properly."

    Why? AD is mainly used for service location in ConfigMgr. Once a client knows where the MP is, AD isn't really used anymore. Thus, existing clients really don't care.

    As noted also, /mp does *not* set the MP for a client, set the SMSMP property for this.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, October 3, 2016 9:14 PM
  • I found that the roles FSMO are distributed across multiple domain controllers in other countries, in different subdomain.

    for example, schema master is running in another DC that is in another subdomain with its own SCCM.

    Could this be the reason why the client does not find de Site?
    Tuesday, October 4, 2016 11:00 PM
  • No. That has nothing to do with ConfigMgr or service location.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, October 5, 2016 12:31 AM
  • I try the command ccmsetup.exe SMSSITECODE=ABC SMSMP=SERVERNAME.FQDN.COM but still can not find the site.

     Schema is extended and I check the site information is published in AD.

    Is there anything else I need to check?
    I detected the antivirus is blocking SMSEXEC.EXE, I have created exceptions but still blocking, Is this necessary for assignment the Site?

    Wednesday, October 5, 2016 3:47 PM
  • What do the logs say now?

    Do you happen to have a group policy in place setting the site code?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, October 5, 2016 3:48 PM
  • In Active Directory the container system management should have a file named SMS-Site-P03 right?

    In my case that file does not exist. Could this be the problem?
    Thursday, October 6, 2016 3:37 PM
  • Well, it's not a file, but yes, there should be objects there named for the site. However, that's completely unneeded if you specify the SMSMP property on the command-line.

    Without seeing the logs again, I can't even hazard a guess.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, October 6, 2016 3:46 PM
  • I did the installation using the command ccmsetup.exe SMSMP=SERVERNAME.FQDN.COM /logon SMSSITECODE=P03

    still can not find the site

    ClientLocation.log

    Getting Assigned Site ClientLocation 6/10/2016 10:52:43 a. m. 932 (0x03A4)
    Getting Assigned Site ClientLocation 6/10/2016 10:56:38 a. m. 3512 (0x0DB8)
    Getting Assigned Site ClientLocation 6/10/2016 10:57:53 a. m. 2428 (0x097C)
    Getting Assigned Site ClientLocation 6/10/2016 10:58:52 a. m. 3292 (0x0CDC)
    Getting Assigned Site ClientLocation 6/10/2016 11:01:00 a. m. 3952 (0x0F70)
    Getting Assigned Site ClientLocation 6/10/2016 11:01:01 a. m. 3236 (0x0CA4)
    Autodiscover Site ClientLocation 6/10/2016 11:01:04 a. m. 3236 (0x0CA4)
    Client is set to use HTTPS when available. The current state is 224. ClientLocation 6/10/2016 11:01:04 a. m. 3236 (0x0CA4)
    Autodiscover Site ClientLocation 6/10/2016 11:01:23 a. m. 3236 (0x0CA4)
    Assigning client to site 'P03' ClientLocation 6/10/2016 11:01:52 a. m. 3236 (0x0CA4)
    Unable to verify sitecode 'P03'. Cannot continue site assignment. ClientLocation 6/10/2016 11:01:53 a. m. 3236 (0x0CA4)
    Autodiscover Site ClientLocation 6/10/2016 11:02:02 a. m. 3236 (0x0CA4)
    Getting Assigned Site ClientLocation 6/10/2016 11:02:38 a. m. 3012 (0x0BC4)
    Getting Assigned Site ClientLocation 6/10/2016 11:02:40 a. m. 3744 (0x0EA0)
    Autodiscover Site ClientLocation 6/10/2016 11:02:43 a. m. 3744 (0x0EA0)
    Client is set to use HTTPS when available. The current state is 224. ClientLocation 6/10/2016 11:02:43 a. m. 3744 (0x0EA0)

    Thursday, October 6, 2016 5:34 PM
  • ccmsetup switches (those prefixed with a forward slash) should appear before properties (those in all caps) on the command-line. This could be throwing the above command-line off.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, October 6, 2016 7:33 PM
  • Dear Sir,

    Try "ccmsetup.exe  /logon SMSMP=SERVERNAME.FQDN.COM SMSSITECODE=P03"

    And please be sure there isn't any group policy out there setting the site code.

    Best regards

    Frank


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, October 13, 2016 8:22 AM
  • You could always re-run the schema extension in case this is the issue. Then try again. Make sure all delegation is in place in the Systems Management container.

    Cheers Paul | http://sccmentor.com


    Thursday, October 13, 2016 3:34 PM