No T-Rex love in Skype for Business (sadface)

Today the Skype for Consumer blog posted that a funky new emoticon was available to celebrate the launch of Windows 10 (and related to Ninja Cat of course).

Unfortunately its not available in the stuffy Skype for Business client :-(

Lync Server 2013 Updates - July 2015 (CU13)

July's updates have the following new items in them:

Participants cannot see your video when you join an online meeting through B2BUA in a Lync Server 2013 environment	https://support.microsoft.com/en-us/kb/3070720
Response group usage report takes longer time to run or cannot complete in a Lync Server 2013 environment	https://support.microsoft.com/en-us/kb/3070713
Call park orbit number is not displayed when you park a call in a Lync Server 2013-based environment	https://support.microsoft.com/en-us/kb/3070717
Lync Mobile Client call is dropped immediately when you dial 0 for an operator	https://support.microsoft.com/en-us/kb/3051963
Lost data when Lync Server 2013 directories move to Skype for Business	https://support.microsoft.com/en-us/kb/3062801
Event ID 1000 is logged and RTCSrv.exe crashes when the process is selected in Resource Monitor tool in Lync Server 2013	https://support.microsoft.com/en-us/kb/3070715
CPU usage percentage of the RTCSrv.exe process is high on a Lync Server 2013 front-end server	https://support.microsoft.com/en-us/kb/3070718

Updates available from: https://www.microsoft.com/en-us/download/details.aspx?id=36820

Changing SQL Database Owner for Lync 2013

When you install SQL back end the mirroring endpoint is set to the person who ran the installer (so in our case Domain\XXXXRichXXXX)

If you use the following SQL:

SELECT [PrincipalName] = sp.name, [PrincipalId] = sp.principal_id, me.*

FROM sys.database_mirroring_endpoints me with(nolock)

inner join sys.server_principals sp with(nolock)

on me.principal_id = sp.principal_id

SELECT EPS.name, SPS.STATE,

CONVERT(nvarchar(38),

SUSER_NAME(SPS.grantor_principal_id))AS [GRANTED BY],

SPS.TYPE AS PERMISSION,

CONVERT(nvarchar(46),SUSER_NAME(SPS.grantee_principal_id))AS [GRANTED TO]

FROM sys.server_permissions SPS , sys.endpoints EPS

WHERE SPS.major_id = EPS.endpoint_id

ORDER BY Permission,[GRANTED BY], [GRANTED TO]

You will get back the current endpoint owner (PrincipalName), what other endpoints can interact with the mirror (GRANTED TO) and who granted those rights (GRANTED BY)
This example is from XXX-SQL01 Principal, its partners are XXX-SQL02 mirror and XXX-SQL03 Witness:

As the Domain\XXXXRichXXXXX account is being removed we created a new Service Account called “DOMAIN\svc-lync-sqlmirror” (standard windows user).

Then on each endpoint in the SQL mirror (Principal, Mirror, Witness) ran the following (changing the server names as appropriate in the final SQL block):

USE [master]

GO

CREATE LOGIN [DOMAIN\svc-lync-sqlmirror] FROM WINDOWS WITH DEFAULT_DATABASE=[master]

GO

ALTER SERVER ROLE [sysadmin] ADD MEMBER [DOMAIN\svc-lync-sqlmirror]

GO

ALTER AUTHORIZATION ON ENDPOINT::mirroring_endpoint TO [DOMAIN\svc-lync-sqlmirror]

GRANT CONNECT ON ENDPOINT::mirroring_endpoint TO [DOMAIN\XXX-SQL02$]

GRANT CONNECT ON ENDPOINT::mirroring_endpoint TO [DOMAIN\XXX-SQL03$]

1. The first block adds the Service Account in as a SysAdmin
2. Next block changes the owner to be the Service Account
3. Last block grants permissions back to the other two SQL servers to be part of the mirror again (running the second block wipes this out - http://blogs.perficient.com/microsoft/2014/03/changing-the-sql-mirror-endpoint-owner-breaks-mirror-in-lync-2013/)

After running the above the owner has now changed:

Once all three mirror partners changed rebooted the servers in the following order:

1. Witness  -  (XXX-SQL03)
2. Mirror  -  (XXX-SQL02)
3. Principal  -  (XXX-SQL01)

(note that your DB's will be on the Mirror at the end of this procedure so use Invoke-CsDatabaseFailover to fail back - https://technet.microsoft.com/en-us/library/jj204991(v=ocs.15).aspx or reboot the mirror again!)

Ensure you wait between each reboot to allow the mirror state to become stable again (all green ticks):

(to run this, Open SQL Server Management Studio > Right click a mirrored database > Tasks > Launch database Mirroring Monitor

Edited 12/07/2015 to note that the db's will be on the mirror server after performing this procedure