locked
SCCM client doesn't seem to be communicating with the server. RRS feed

  • Question

  • I have set up a new installation of SCCM 2012r2 and pushed the client out via group policy.

    But the client doesn't seem to be communicating with the server.

    Is there any tool for troubleshooting why this might be occuring?

    Wednesday, November 27, 2013 2:12 PM

All replies

  • Start with the logs on the client.

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Wednesday, November 27, 2013 2:31 PM
  • Where are they located and or called?
    Wednesday, November 27, 2013 2:35 PM
  • http://technet.microsoft.com/en-us/library/hh427342.aspx


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Wednesday, November 27, 2013 2:55 PM
  • In the event logs I receive a event id 4909

    On 27/11/2013 16:48:28, component SMS_HIERARCHY_MANAGER on computer DC02 reported:  Configuration Manager could not locate the "System Management" container in Active Directory (welldon.local).  Nor could it create a default container.  This will prevent Site Component Manager and Hierarchy Manager from updating or adding any objects to Active Directory.

    Possible cause: The site server's machine account might not have the correct rights to update active directory.
    Solution: Either give the Service Account rights to update the domain's System Container, or manually create the "System Management" container in this domain's Active Directory system container, and give the site server computer account full rights to that container (and all children objects.)

    I have given the computer these rights but the message still pops up

    Wednesday, November 27, 2013 4:51 PM
  • Did you give it rights to the system management container and all child objects?


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Wednesday, November 27, 2013 4:56 PM
  • Yes as its a test domain I gave it Full Control
    Wednesday, November 27, 2013 4:59 PM
  • Looking in the event logs I get this message about the WSUS server. Is this because it is not truely compatible with Windows 2012r2

    On 28/11/2013 10:44:00, component SMS_WSUS_CONTROL_MANAGER on computer DC02.welldon.local reported:  WSUS Control Manager failed to configure proxy settings on WSUS Server "DC02.welldon.local".

    Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted.
    Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website.You can receive failure because proxy is set but proxy name is not specified or proxy server port is invalid.

    Thursday, November 28, 2013 10:53 AM