locked
SCCM Cannot write to System Management container RRS feed

  • Question

  • AD functional level Windows Server 2008 R2

    SCCM 2012

    Extended and verified schema

    Created System Management container on the root of domain.com

    Site system computer account has full access to object and all children

    SCCM cannot write to this container.  Errors in the Site Component Status refer to not being able to find the container, create the container or have permissions to the container.  I have connected to different DC's and the container is on all as well as the one processing the login for the Site server.  No information is being written to this container.

    What am I missing.  I have deployed 2012 at least a half donzen times and have never run into this.

    Thanks

    Thursday, August 16, 2012 12:19 PM

Answers

  • Did you create the system management container at the root of the domain you said? It should be under the system container check out the SS.


    Justin | http://patchmypc.net


    • Edited by Justin Chalfant Thursday, August 16, 2012 12:26 PM
    • Marked as answer by B_Keller Thursday, August 16, 2012 12:32 PM
    Thursday, August 16, 2012 12:26 PM

All replies

  • Did you create the system management container at the root of the domain you said? It should be under the system container check out the SS.


    Justin | http://patchmypc.net


    • Edited by Justin Chalfant Thursday, August 16, 2012 12:26 PM
    • Marked as answer by B_Keller Thursday, August 16, 2012 12:32 PM
    Thursday, August 16, 2012 12:26 PM
  • Hi,

    "Created System Management container on the root of domain.com" do you have multiple domains in the forest?

    And I assume you created the System Management container under "System" and not in the root of the domain. Are there more detailed information in the Hman.log file?

    regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Thursday, August 16, 2012 12:31 PM
  • My bad.  Somone else created the container and did not place it in thes ystems container.  Should have caught that.  Won't happen again.  :)

    Thanks

    Thursday, August 16, 2012 12:36 PM