As I mentioned before and the others have expanded upon, it has nothing to do with domains. Clients query the global catalog which is part of the forest for ConfigMgr objects. That's why it's important to actually address my first statement, are you really talking about separate forests or just multiple domains within a single forest. It makes a big difference.
J From: [email protected] [mailto:[email protected]] On Behalf Of Elias Leal Sent: Thursday, September 26, 2013 4:24 PM To: [email protected] Subject: Re: [mssms] Issues with System Management container in other domains JRIT, In my experience, you do need a SYSTEM MANAGEMENT container in each domain where you have clients. Make sure under "Admistration -> Hierarchy Configuration -> Active Directory Forest" that you have an entry for each child domain in your forest. For each entry, you need to enable publishing under the "Publishing" tab. This is essentially telling your site server to publish info into the SYSTEM MANAGEMENT container for that specific domain. >From my understanding, domain clients will look only in the SYSTEM MANAGEMENT >container of their own domain. I don't believe domain clients can look at the >SYSTEM MANAGEMENT container of other domains or some root domain in the same >forest. I manage a multiple domain environment within a single forest and this is how I have site publishing configured in SCCM2012. If you are talking about multiple domains across multiple forests, then I am not certain since I haven't done that. Elias On Thu, Sep 26, 2013 at 3:47 PM, JRIT <[email protected]<mailto:[email protected]>> wrote: So, I dont need SYSTEM MANAGEMENT container in the other domains? Just on the same domain of SCCM? 2013/9/26 Jim Parris <[email protected]<mailto:[email protected]>> Two things, I'm not sure, but I think you can only publish to one domain/forest, but I haven't verified that. However, what you can do in all the domains besides ABC is when you install the client, use the command option /DNSSUFFIX=abc.com<http://abc.com>. This will tell the workstations to check the System Management container in that domain instead of the domain of the workstation. Hope this helps! James Parris Tech Consultant | Acquisition Integration and Configuration Management Humana 123 East Main Street | Louisville, KY 40202 T 502.428.9129<tel:502.428.9129> [email protected]<mailto:[email protected]> www.humana.com<http://www.humana.com> Sent with Good (www.good.com<http://www.good.com>) -----Original Message----- From: Daniel Ratliff [[email protected]<mailto:[email protected]>] Sent: Thursday, September 26, 2013 02:29 PM Eastern Standard Time To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Issues with System Management container in other domains If I remember correctly ConfigMgr only publishes to the same domain the site servers are in? Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of JRIT Sent: Thursday, September 26, 2013 2:19 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Issues with System Management container in other domains Folks, I have SCCM 2012 deployed in a domain ABC. I need to dicover computers from domains ABC, DEF, and GHI. All the discovery was fine, but now I have an issue. I have created the container SYSTEM MANAGEMENT in domain ABC, grated the right permission to SCCM Computer account, and all SCCM objects was created fine inside SYSTEM MANAGEMENT in domain ABC. But, I did the same process for domains DEF and GHI and SCCM create no objects inside their respectives SYSTEM MANAGEMENT containers. Please, can someone help me troubleshoot that? I dont know how to start. Tnx The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
