Hi all!!
I've been asked to install a primary ConfigMgr 2007 SP2 R3 site in an AD environment in which a disjoint namespace must be used and - since I've never dealt with this kind of configuration - I'd like to know some information :)
Supposing that the AD DNS name is "company.local" and the primary DNS suffix is "my.company.local", I'd like to know if:
1) the primary DNS suffix assigned to the ConfigMgr server can effectively be "my.company.local" or I must specify the AD DNS name as primary DNS suffix for the server
2) the FQDN name used for the management point role configuration must be configured with the disjointed DNS suffix or with the AD DNS name
3) there's any issue related to the usage of a disjointed namespace
If I'm not wrong, I've read somewhere that with a disjointed namespace some issue may arise with AD discovery. This should not be a problem for us because, as a final requirement, we won't be authorized to configure AD discovery, but only heartbeat discovery.
Thanks for any suggestion!
