Update databases after Core Component Cumulative Update on Lync Server 2010 Standard

Hello, 

I've installed several Cumulative Updates in the past on my Lync 2010 Server through Windows Updates but I just found out that I have to update the Lync Server databases. I've never updated the database after I've installed the Cumulative Updates. In how much trouble am I? I haven't had any issues with my Lync Servers everything seems to be working fine so far. 

Now I have another cumulative update in my Windows Update queue and I want to make things right this time and update the Lync database as well. I know I have to run the following cmdlet:

 Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn <EEBE.Fqdn> -UseDefaultSqlPaths

Probably a dumb question but here it goes: My Lync databases are hosted in my SQL server, they are not on the Lync server. Due to this fact, do I have to change the -SqlServerFdqn parameter from EEBE.fqdn to my SQL server's FQDN? And do I run the cmdlet from my Lync front-end server or from my SQL server? 

Will it cause too much trouble to update the databases this late in the game? 

Thanks!


  • Edited by Rarakane Monday, June 01, 2015 7:45 PM
June 1st, 2015 7:39pm

I think that you are asking "I have Lync Standard Edition - what FQDN do I use for the 'Install-CSDatabase' command?"  Right?

You need to run the update as soon as you complete patching. 

The format for the command will be as you stated but the FQDN will be the FQDN of the Lync STD FE server (e.g. LyncSTD1.domain.local)

Install-CsDatabase -Update -ConfiguredDatabases

-SqlServerFqdn LyncSTDfeFQDN.domain.local -UseDefaultSqlPaths

http://blogs.technet.com/b/dodeitte/archive/2013/02/27/how-to-apply-lync-server-2013-cumulative-updates.aspx

http://itcalls.blogspot.com/2013/11/how-to-update-lync-2013-standard.html

If I misunderstood, and you were asking about Enterprise, than it's the command as mentioned but the SQL Server FQDN instead.  

Thanks!




Free Windows Admin Tool Kit Click here and download it now
June 1st, 2015 8:22pm

Also, EEBE (Enterprise Edition Back End) = 'SqlServerFqdn' - I reread your post - i think you have enterprise?  Right?  So you can typically use the SQL fqdn that is in your topology, and as long as you have the expected rights, the command will finish.  
June 1st, 2015 8:28pm

it's the same command that we have been advising you to run above.

If you have default paths configurd on SQL, the defaultpath flag will work ... if you don't, you can specify.    Use the FQDN of the sql server that in your topology.


Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2015 1:24pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics