SQL backend and File Store pitfalls

I just returned from a job that first failed monumentally, but that I was able to recover from through some hard research. Better share it for others to avoid.

Short resume of the scenario: Customer is migrating from Lync Server 2010 Standard to Lync Server 2013 Enterprise edition. We did the schema, forest and domain prep, which went well. Then did the prerequisites on a Windows Server 2008R2 (thanks to Mattias for a great write-up on that, http://kressmark.blogspot.no/2012/11/prerequisites-for-lync-2013-on-windows.html). Customer wanted two adaptations from what I consider a “standard” installation:

  1. They wanted SQL backend to run on a named clustered instance (active-active, not supported I know and have pointed it out)
  2. They wanted the File Store to be located on a sub-directory of the share itself

I requested that the admin account used for installation be given SA permissions for the SQL instance and also having Full Control permissions on the share and destination folder.

Upon Topology Publishing we encountered numerous warnings. Both from SQL database installation and File Store not being able to assign the ACL’s. Nevertheless, in the SQL backend both the “rtcxds” and “rtcshared” databases were created and in the File Store the “WebServices” and “ApplicationServer” folders were created.

To wrap it up and summarize; even though we were able to complete the install and even move a user over to the new pool and sign in, it was a broken install. We decided to remove and reinstall rather than spending time troubleshooting. What made the trick the second time around was:

  1. When installing on a clustered SQL backend, make sure that you run the installation using SQL server defaults (or manually assigning locations), and NOT applying Lync server algorithms for database location. We did this through PowerShell to make sure we could Control it:
    Install-CsDatabase -ConfiguredDatabases -SqlServerFQDN <server FQDN> -ForInstance <named instance> -UseDefaultSQLpaths
  2. Make sure that the destination folder for the Fire Store is a share itself and that the admin installing it has all the necessary permissions (Full Control).

One thought on “SQL backend and File Store pitfalls

  1. Mars Blog artikler fra Atea konsulenter – LyncAtea.no

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s