

Let me say it this way, i believe the trouble stems from the missing lis.mdf database which i regrettably recreated on the 2010 server after i had went live with the 2013 server, somehow recreating this database threw off both my servers. Would really love to get it working again without needed to scrap everything. In short I messed up my lync 2013 upgrade, and now need to republish my topology so that i can manage my Lync Server. This SQL Server is major version 10, minor version 0, and build 5500." Minimum SQL Server must be major version 10 and minor version 50 and build 1600 (2008 R2) or higher. Publish Topology on the 2013 server fails with this message: Get-CsConfigurationStoreLo cation on either server only sees the local server not the coexisting server. So i have to open from the last good file everytime. Which succeeded on my 3rd retry of the command.įrom this point i am unable to manage my site using CS Control panel, when i download existing topology from Topology Builder it sees completely nothing as if its a brand new setup. Unfortunately i do not have a backup of this database file so i went about to recreate the file using this command: “Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn .za –SqlInstanceName” to re-create the store database lis.mdf Since the 2010 setup has been working for a long time, it has not complained about this database and was just working. When i checked on SQL instance the database would not open, checked the path to verify and found it to be missing.

The command "Move-CsManagementServer" failed every time with "unable to open lis.mdf"

The problem came in when i needed to start to remove the old server by reassigning the CMS to the new server as described on.

Was also able to migrate users from 2010 to 2013, internally Lync is functional and on mobile devices. I was able to successfully install Lync 2013, configure my new pools and download and configure the 2010 Topology and also Publish the changes for a coexisting setup. Lync 2010 setup has had its issues but was functional in the last couple of months. I was in the process of migrating from Lync Server 2010 to Lync Server 2013 on a brand new server, I have a problem publishing my Lync Server 2013 Topology
