Running UCMA trusted application in a different domain?

Question

Is it possible to run a UCMA trusted application in a domain different from the Lync Server?

If so, what are the specific steps that are required to set up the application host?

I ran the Bootstrap and got the SQL store setup. However I still cannot access cmdlets like Get-CsSite because it complains my domain user does not have access.

Any ideas?

 

Thanks,

Vivek

Answer 1

From the 1st note in the help for activating a UCMA  3.0 Core Trusted Application - http://msdn.microsoft.com/en-us/library/gg437205.aspx

 Note
It is recommended that the computer running the trusted application be joined to the domain in which Lync Server 2010 is running. However, if there is no intent to run Lync Server 2010 PowerShell cmdlets from the application server or to make use of UCMA auto-provisioning capabilities, then the application can be run on a computer that is not joined to the domain.

So you can run the application, you just can't use any of the cmdlets.

---

-- How To Ask a Question: http://support.microsoft.com/kb/555375 -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Answer 2

And just to add a quick note, from my understanding, you also can't using auto-provisioning when creating a ColaborationPlatform instance.  You'll need additional information like a GRUU.

---

http://donahoo-development.com

Answer 3

So now the original question of "If so, what are the specific steps that are required to set up the application host?" remains. When you try to add an FQDN as a trusted application server/pool in Lync it complains when you publish the topology that the machine is missing from the domain. Can you safely ignore that warning and go ahead anyway?

Answer 4

Yes, you can ignore the warning.  As a rule though, if you're going to be manually provisioning an app, use -RequiresReplication $false on the new-cstrustedapplicationpool to keep it from trying to replicate the config DB.