Domain – Setting up SCCM on multiple domains

domainsccmsccm-2007

In a lab environment, I am attempting to configure an SCCM server (2007) to be our patch solution across three different domains.

DOMAIN A (domA.sample):
The trusted domain. SCCM01 (Server) is on this network.

DOMAIN B (domB.sample):
One way trust between the two domains. DOMAIN B trusts DOMAIN A, but not the other way around.

DOMAIN C (domC.sample):
No trust between this domain and any other domain.

SCCM is set up and running on DOMAIN A. Any server on that domain will receive patches. I am currently working on Domain B (1-way trust). I am unable to add find the systems in my SCCM server. I am able to install the client manually on ServerA.domB.sample, and the site code comes back correct, even if I rediscover the site code, but somehow the ServerA is not communicating with SCCM01.

What I've tried:

http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/6f06bbf1-6ff4-4a41-9d42-894c1a6e13ea
http://scexblog.blogspot.com/2010/06/sccm-discover-another-trusted-domain.html

Any one have experience with SCCM?

Best Answer

I want to say that I don't think that the trust matter all that much. It's been a while since I went through this, so I don't want to give you any BS answers. But from what I vaguely recall, I think it has something to do with setting up an SCCM Network Access Account.

Here is some reading for you:

Related Solutions

Php – Run single php code using multiple domains

If you have control over your Apache configs on your server, just change the default virtual host's DocumentRoot to /your/site/root. As long as your domains' A records (or you can use CNAMEs) all resolve to your Web server's IP address, Apache will dish up the default website if there's no match for another virtual host.

This is a very common method of doing it, so unless you need to have separate Web servers for each domain, there's nothing more manual with this method than any other method (like using rsync to copy your PHP files to another server); DNS needs to be setup regardless.

You can setup wildcard DNS for sub-domains you control so that *.yourdomain.com (foo.yourdomain.com, bar.yourdomain.com, etc.) all resolve to the same A record, but not with TLDs (unless you happen to own the .com TLD).

SCCM 2007 managing hosts in non trusted forest

We have this setup for managing machines (mainly virtuals) in our development environment from our live environment's SCCM infrastructure. These are totally separate forests with a fairly stringent firewall between them. We mainly only use it for OS/app patching via SCCM Software Updates, and limited hardware/software inventory reporting.

Once we'd opened up the required ports in the firewall between the environments, all we needed was to use the correct command line when installing the SCCM client on the dev machines, we use this command line:

\\server\share\ccmsetup.exe /mp:siteserver.fqdn smssitecode=SMS ccmhttpport=50010 smsslp=siteserver.fqdn  FSP=fspservername

Obviously the fallback status point is optional (but highly recommended for troubleshooting, especially if you're currently having problems installing clients), and there's no need to specify the port if you're using the standard port.

We found that installs were failing to connect properly to the site until we properly specified the site code and SLP server in the install string.

Update See this new TechNet article Using ConfigMgr 2007 to Manage Clients in a Workgroup or Un-Trusted Domain

Related Topic