Seems like Microsoft recently updated the Database Software support for Lync Server 2013 to include Failover clustering as a supported Database high availability solution in addition to SQL
We can directly notice that SQL failover Clustering support has been introduced without the need to apply any Server side updates. which confirm that this recent statement is the result of the extensive tests applied by Microsoft and the clients that participated in the testing program.
it is good to note that active passive failover clustering is only supported, so I believe that doesn’t include SQL always on availability groups.
For my opinion this is another important update introduced to Lync sever 2013 product which will be most welcomed by database administrators, which doesn’t encourage using SQL mirroring and also in organizations where SQL consolidations are a required.
After issuing the Lync Server 2013 Cumulative Updates (CU2) July 2013 installation workflow article, i have been requested to include a bigger copy of the embedded installation flowchart, therefore i have decided to make it available for download in two flavors pdf and vsdx at this location CU2FlowChart
feel free to update or use this flow chart upon your needs
If you happen to need to reset the search index for an Microsoft Exchange 2013 mailbox database you would have noticed that the "ResetSearchIndex.ps1" script that used to be present in Exchange 2010 was removed. So this is what you should do to reset the search catalog of an Exchange 2013 mailbox database
- Stop-Service HostControllerService (you can simply run this command from powershell or stop the service in the services mmc
- go do the folder hosting your mdb file and delete the folder named with a long GUID
- Start-Service HostControllerService
That's about it
The July 2013 Lync 2013 Client update introduced some interesting features, but the time the update was released there was no official statement that includes the newly introduced features, however thanks to many people like Justin Morris and Matt Landis and others that they pined out about the newly features that are introduced with this update at that time. 2 days ago Microsoft Lync Program Manager II Debbie Arbeeny has release an official statement that explain the newly introduced features with the July 2013 Desktop client updates
You can find the Client updates at this location
Note that Lync Server 2013 Cumulative Updates July 2013 is required to get all the new client features working, for more details about the server side update please refer to my post that i have published earlier in this respect Lync Server 2013 Cumulative Updates (CU2) July 2013 installation workflow
The Second Cumulative update package for Lync Server and client has been released,
It seems like the Server update package improves the reliability, stability and performance of Lync server 2013 Different roles,
installing Lync Server Cumulative updates, is two split on two main processes:
- Applying updates for various Lync roles/services
- Applying database updates
- It is advised to plan installing the Cumulative updates off business/non peak business hours, since services restart is required as part of the installation process
- The process of Applying the updates for various Lync roles is common for all Lync installations and role combination \
In part I of this tutorial I have introduced a bit of theory behind the new Exchange 2013 feature of AutoReseed, today we will apply this theory in the LAB and see how it behaves.
For this lab I will be using
- 2 nodes Exchange 2013 DAG (hosting all roles) running on Windows 2012 datacenter edition. On a side note, even though I am running this LAB on Windows datacenter this is no longer a requirement and a DAG can now run on Windows 2012 standard edition.
- 2 mailbox databases on the same volume with names DB1 and DB2
- One spare disk
- AutoDagVolumesRootFolderPath will be set C:\ExchVol
- AutoDagDatabasesRootFolderPath will be set C:\ExchDBs
- AutoDagDatabaseCopiesPerVolume will be set to 2