Lync Server 2010 - Configure Multi-Site Simple URL`s

Simple URL ScopeYou can configure your simple URLs to have global scope, or you can specify different simple URLs for each central site in your organization. If both a global simple URL and a site simple URL are specified, the site simple URL has precedence.
In most cases, Microsoft recommend that you set simple URLs only at the global level, so that a user’s Meet simple URL does not change if they move from one site to another. The exception would be organizations that need to use different telephone numbers for dial-in users at different sites. Note that if you set a one simple URL (such as the Dial-in simple URL) at a site to be a site-level simple URL, you must also set the other simple URLs at that site to be site-level as well.
You can set only global simple URLs in Topology Builder. To set a simple URL at the site level, you must use the Set-CsSimpleURLConfiguration cmdlet.

Example

We have 3 Global Sites, Each site requires to be autonomous from each geographical region. (i.e. if  the UK had a major failure, US, HK would not be effected.......

so we want to set each region with its local meeting and Dialin URL`s

Site 1 (USA) = https://lync.us.abc.com
Site 2 (UK)   = https://lync.uk.abc.com

Site 2 (HK)   = https://lync.hk.abc.com

Using Lync Powersehell we would need to run the following commands to create our site specific url`s.  (Red TXT = Change as required)

 $simpleUrlEntry1 = New-CsSimpleUrlEntry -Url "https://lync.uk.abc.com/dialin"
 $simpleUrlEntry2 = New-CsSimpleUrlEntry -Url "https://lync.uk.abc.com/meet"
 
 $simpleURL1 = New-CsSimpleUrl -Component "dialin" -Domain "*" -SimpleUrlEntry $simpleUrlEntry1 -ActiveUrl "https://lync.uk.abc.com/dialin"
 $simpleURL2 = New-CsSimpleUrl -Component "meet" -Domain "abc.com" -SimpleUrlEntry $simpleUrlEntry2 -ActiveUrl "https://lync.uk.abc.com/meet"
 
 New-CsSimpleUrlConfiguration -Identity site:LYNC-UK -SimpleUrl @{Add=$simpleUrl1, $simpleUrl2}


 ---------------------------------------------------------------------------

 $simpleUrlEntry1 = New-CsSimpleUrlEntry -Url "https://lync.hk.abc.com/dialin"
 $simpleUrlEntry2 = New-CsSimpleUrlEntry -Url "https://lync.hk.abc.com/meet"
 
 $simpleURL1 = New-CsSimpleUrl -Component "dialin" -Domain "*" -SimpleUrlEntry $simpleUrlEntry1 -ActiveUrl "https://lync.hk.abc.com/dialin"
 $simpleURL2 = New-CsSimpleUrl -Component "meet" -Domain "abc.com" -SimpleUrlEntry $simpleUrlEntry2 -ActiveUrl "https://lync.hk.abc.com/meet"
 
 New-CsSimpleUrlConfiguration -Identity site:LYNC-HK -SimpleUrl @{Add=$simpleUrl1, $simpleUrl2}



 ---------------------------------------------------------------------------


 $simpleUrlEntry1 = New-CsSimpleUrlEntry -Url "https://lync.us.abc.com/dialin"
 $simpleUrlEntry2 = New-CsSimpleUrlEntry -Url "https://lync.us.abc.com/meet"
 
 $simpleURL1 = New-CsSimpleUrl -Component "dialin" -Domain "*" -SimpleUrlEntry $simpleUrlEntry1 -ActiveUrl "https://lync.us.abc.com/dialin"
 $simpleURL2 = New-CsSimpleUrl -Component "meet" -Domain "abc.com" -SimpleUrlEntry $simpleUrlEntry2 -ActiveUrl "https://lync.us.abc.com/meet"
 
 New-CsSimpleUrlConfiguration -Identity site:LYNC-US -SimpleUrl @{Add=$simpleUrl1, $simpleUrl2}

Lync 2010 - error publishing SQL Reporting HTTP 401 Unauthorised

Problem
When trying to publish Lync 2010 SQL reports to a Windows 2008 R2 / SQL 2008 R2 server.
you receive error "HTTP 401 Unauthorised"

Cause
This is because by Default SQL 2008 R2 / Windows 2008 R2 is set to auto negotiate the authentication method. The problem is, that it will try and use "kerberos" authentication which by design is far more secure, which in turns can cause restrains on certain actions .
Full Details

http://msdn.microsoft.com/en-us/library/cc281253.aspx

Resolution
Force SQL Reporting to use NTLM Authentication.

Use NTLM. NTLM will generally work in cases where Kerberos authentication fails. To use NTLM, remove RSWindowsNegotiate from the RSReportServer.config file and verify that only RSWindowsNTLM is specified. If you choose this approach, you can continue to use a domain user account for the Report Server service even if you do not define an SPN for it.