Updating address book lync 2016

6854933580_2c8b688306_z

The reason for this was that I didn’t check if they were running on the Primary SQL instance back in Step 3 (I did this for the example to show what happens when you don’t do this.

Really you should have done this check back in Step 3).

In the real world you should actually do this at this point.

updating address book lync 2016-85updating address book lync 2016-2updating address book lync 2016-51updating address book lync 2016-60

From the screenshot above we can see that on the secondary server, the rgsconfig database has been automatically deleted.With the release of Lync 2013 CU2 (July 2013) the upgrade process has changed from what is documented here.The new process in CU2 does not include the requirement to break the database mirror anymore.Note: In the future the need to remove the database mirror for other database types may become a requirement as well.So if you are coming to this post for a newer CU update, please refer to the specifics of the KB article relating to your specific CU release.So now when I check the status of the Persistent Chat databases with the Database Mirror Manager I notice that they are both on the Secondary SQL instance: To change these back over I just clicked on the Primary check boxes for both of these databases and then click the Invoke button.

You must have an account to comment. Please register or login here!