A lot of people may know them; share and ntfs permissions on a folder. Because Lync uses a share to store data incorrect permissions can result in big problems.
The folder contains the following information
- data which must be replicated to/from the CMS
- the addressbook
- phone client updates and logs
- several application related files: for example custom voice prompts
- data which is shared during a meeting
When one of the features isn’t working users will see this very soon.
But which share permissions are needed on the Lync Share? The administrator(s) account(s) which are responsible for managing Lync need to have full control on this folder. When they don’t have these permissions you will get warnings during the Lync installation.
The other permissions are set during the Lync installation. But it might happen that changes have been made in the share permissions which results in failures.
But how can you fix this? Well, it’s not that hard use the enable-CsComputer. To simulate the process I removed all permissions from the share excluding the administrator.
This will cause errors in the event log after a few minutes:
The event displayed above will tell you that the File Transfer Agent can’t access the share on the Front End Server. This has as a result that the configuration changes won’t be distributed anymore to, for example the Edge Server.
By executing the Enable-CsComputer cmdlet by using the Lync Management Shell it will restore the share permissions. Because this cmdlet doesn’t give any output by default you can add the -v parameter to see what happens.
When completed you can open the log file which is created during the process. As you can see several ACL’s have been configured.
When having a look at the share permissions on the Lync Share you will see that permissions have been configured correctly again: