Hi,
From your 1st Post:
Ok, don't get the wrong idea when there's a trust relationship between different forest. Yes, although it allows you to view and grant access towards to resources e.g. File shares, however, take note that it doesn't allow cross-services sharing e.g. Exchange Services, Office Communications Servers 2007 as each domains holds is own unique SIDs, covering from user objects to machines within the environment.
For information about changes to the schema by OCS 2007:
http://technet.microsoft.com/en-us/library/dd425088(office.13).aspxSome key features that you may be interested to know:
http://technet.microsoft.com/en-us/magazine/2009.03.ocsr2.aspx?pr=blog :)
As per my earlier posting, the reason why I've suggesting to migrate the users over is to allow the enable the users to have the capability to use OCS, since they're residing under the forest that has OCS enabled.
For Your 2nd Post:
By adding the additional domain into the Global Settings, it only allows OCS to support additional SIP domains. For example: my company holds to different address space which is publicly known, MyDomain.com and MyUC.com. Both of this namespace is registered under the Public DNS, hence, I've 2 users,
James@MyDomain.com &
Jack@MyUC.com, both of this users are located under the same Active Directory forest called MyCompany.local.
So, when someone attempts to sign-in from the outside or inside, it'll refer to the SRV records that the DNS server holds, allowing the SIP traffic to be directed to the OCS Infrastructure.
You may extend the schema at your other child company and host a seperate OCS Server, however, you may not be able to extend and get the users at the other end to leverage on your current OCS infrastructure.
Hope this clarifies your enquiries above.
