Tag Archives: CU

December 2012 cumulative update for Lync Phone Edition is out now – #Lync

Remember to test first, we don’t want all phones to be down on Christmas eve…

Download here:

And something to read here: http://support.microsoft.com/kb/2737911

This cumulative update fixes the following issues:

What was in Lync Cumulative Update (CU) 5 #Lync

Lync CU5 is out and there are some good stuff in it…

One of the most talked about new features is that Video Calling for RCC-Enabled Users was added. Great news for some orgs that still sits with PBX´s.
But there are still some caveats to this that can be read about in the NextHop post by Jamie Stark

It is also now possible to use DFS fileshares in topology builder, details here: 2666344  You cannot add a DFS file share as a file store in Topology Builder of Lync Server 2010.

Some other fixes of notice:

2621841 A Lync 2010 user can still send files that contain a long file name after the file transfer is blocked

2664650 Microsoft push notification messages are not delivered to Lync mobile clients

2658817 Calls do not always connect if you have a DNS balancer and multi-homed network deployed in a Lync Server 2010 environment

2675221 A Front End Server does not route network traffic to Lync 2010 Mobile clients if the Collocated Mediation Server option is enabled in Lync Server 2010

2670434 A user cannot sign in by using a mobile device in a Lync Server 2010 environment that has Mobility Service deployed

And many more fixes…

It can be downloaded from http://www.microsoft.com/download/en/details.aspx?id=11551

And one more thing: Don’t forget to update the Database. Best practices when updating Lync servers can be found here. http://www.ultimate-communications.com/2011/12/best-practices-when-updating-lync-server-with-those-cumulative-updates-lync/

Best practices when updating Lync Server with those cumulative updates – #Lync

Cumulative Updates (CU) are kind of a service pack that comes out quarterly for Lync Server and the clients. It includes fixes and some times new functionality is added.

The latest is Cumulative Update is CU4 (as of December 2011) and it can be downloaded here http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11551

image

As you can see there are a lot of files to download and you could just download and update specific components or you can download the LyncServerUpdateInstaller.exe package that includes all the latest updates. So go ahead and download it and then copy the file to your Lync Servers.

To start the update process log in to your server. And start the Lync Server Management Shell

  1. Check that no users are talking on the phone or are in a meeting before you start the update. You can do this by running Get-CsWindowsService (read more in this post http://www.ultimate-communications.com/2011/11/lync-powershell-tip-5/ )
    image
    1. In the screenshot above there are one active call in the call park service and it would be a bad idea to turn off the services right now as this would terminate the call.
  2. So the solution would be to prevent new sessions for a while and drain the active connections. This can be done running Stop-CsWindowsService –Graceful
    (Read more on server draining at http://voipnorm.blogspot.com/2011/03/lync-server-draining.html )
    1. image
      As seen in the picture the services is now stopped.
  3. Next thing would be to stop the World Wide Web service. By typing: net stop w3svc
  4. Now Close all Lync Server Management Shell windows.
  5. Install the cumulative update for Lync Server 2010 by running LyncServerUpdateInstaller.exe
    image
    This will start the update tool and you should se what updates are needed and what version is already installed. (As you can see in the picture I have already installed the latest update package and it shows a green checkmark at every line. If there were some services that wouldn’t be updated this would show a red stop mark instead.)
    1. Restart the computer if you are prompted to do so
  6. The next step is something that is almost always forgotten. To update the Lync Server Databases (this step is normally not done if you just used Windows Update to update your Lync server and should then be done manually after Windows Update has updated your server.)
    1. Start the Lync Server Management Shell: (Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.)
    2. To apply the changes made by LyncServerUpdateInstaller.exe to the SQL Server databases do one of the following:
      1. On Standard Edition Server and Enterprise Edition: Front end servers, once you have installed update for core components, the updated sql files will be dropped on the server. Then run the following cmdlet to apply the changes:
        Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn <EEBE.Fqdn> -UseDefaultSqlPaths

        Notes

        • In a Lync Server 2010 Standard Edition environment, run the cmdlet from the Standard Edition server.
        • In a Lync Server 2010 Enterprise Edition environment in which the archiving/monitoring services are collocated with an Enterprise Edition back-end server, run this cmdlet from the Enterprise Edition back-end server.
        • In a Lync Server 2010 Enterprise Edition environment in which the archiving/monitoring services are not collocated with an Enterprise Edition back-end server , run this cmdlet from the Enterprise Edition front-end server.

        If the RTCDyn databases are removed after you run the cmdlet without the UseDefaultSqlPaths parameter, run the following cmdlet to restore the RTCDyn databases:

        Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn < EEBE.Fqdn > -DatabasePaths <RtcDyn log path>, <RtcDyn data path>
  7. Now when the database is also up to date, its time to start the IIS & Lync Server services. At the command line, type:
    net start w3svc
    Start-CsWindowsService

And that’s it Open-mouthed smile you should now be up to date and ready to roll out the client updates to your Lync clients and phones.

Have I missed something that you considerer being a best practice when updating your server? Please comment bellow.