HI - mSSMSRoamingBoundaries atribute value for the object CN=SMS-Site-XXX is not getting published in the child domain. Scenario a) Have 3 domains in ine forest . Domain names are A, B & C. Forest is F. AD schema is extented on forest level. TRUST relation is already in place for all three. Only 1 SCCM primary server for the forest and rest all SCCM secondary servers span across the three domains. b) Central primary server is installed on B domain. Hence all the SMS-Site-XXX & SMS-MP objects are getting created under two domains ( Domain B and the relevent domain in which the secondary server is present). c) We have noticed that mSSMSRoamingBoundaries atribute value for the object CN=SMS-Site-XXX is not getting published in the relevent domains if the SCCM server is in A or C domain. However if you loo at the object which is created in B domain then the above mentioned attribute value is present. So my query is whenever client query AD from A or C domain controller then it should go B domain controller and get the MP and other details right? This can create delays in client and SCCM performance? What is the best possible way to get the attribute values published in A & C domains? Anoop C Nair

Have you manually created the Systems Management container in the child domains and granted the appropriate security to the container?

I didn't create any System Management container manually. It should get automatically created right ? If there is anything like, we need to create the container manually for above mentioned scenario ? Please adviceAnoop C Nair

It could get created automatically if you granted the siteservers permissions on the 'System' container. You have to create that container in each domain where there's a siteserver: http://technet.microsoft.com/en-us/library/bb632591.aspx and http://technet.microsoft.com/en-us/library/bb633169.aspx

torsten is correct the permissions have to be set for this to happen automatically. You can verify in the hman.log on the site server to see where its getting hung up. I have seen where the permissions are set but they were not set to inherit down and lower objects were not able to update.

@ Torsten & Brandon - Thanks for the inputs. I have checked the permissions on the secondary servers and those servers have FULL rights on the “System Management” container on their respective domain. Just explain my problem in some more details so that it is better to understand. 1. There are 3 domains in my environment A, B & C. 2. The Primary server is installed in domain B. 3. All the secondary servers reporting to Primary server are span across the domains A, B & C. 4. In B domain (on which Primary server is installed) – all the active directory objects (CN=SMS-Site-<sitecode>)are created under “System Management” container is having all the required attributes including “mSSMSRoamingBoundaries” and it is set to proper value. 5. In B domain (on which Primary server is installed) – we can see all the active directory objects (CN=SMS-Site-<sitecode>) for all the secondary sites coming under my primary server with proper value for all the attributes as explained above. 6. In domain A & C if you look at active directory objects (CN=SMS-Site-<sitecode>) for the respective secondary sites (located in domains A & C) then we can see that the attribute “mSSMSRoamingBoundaries” is not assigned to any values. Am just wondering this is normal behavior of something needs to be done. Please advice. Anoop C Nair

Thanks . No there is no errors and the clients are able to fetch the proper details from AD like PMP and MP details.Anoop C Nair