It publishes to the same FOREST the ConfigMgr site servers are in.  The 
information is available forest-wide.  So agents in one child domain would see 
and access the published information for a site that lives in another child 
domain in the same forest.

-Phil

From: [email protected] [mailto:[email protected]] On 
Behalf Of Daniel Ratliff
Sent: Thursday, September 26, 2013 2:26 PM
To: [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]] 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.
________________________________

PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are 
privileged and confidential and intended solely for the use of the individual 
or entity to whom they are addressed. If you have received this email in error 
please notify the sender. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail or any of its attachments.




Reply via email to