![]() In Lync Server 2013 the following subfolders will appear by default under the “ 1-WebServices-1” folder. C:\LyncShare\1-ApplicationServer-1\AppServerFilesįrom the introduction of web service applications in LCS to the latest release of Lync the amount of new features and functionality provided by IIS has grown steadily.The AppServerFiles directory is configured when publishing the topology with the following file permissions. There may also exist an “ Rgs\Temp” folder which seems to store the originally uploaded music file. The “ Rgs\Instances” and “ Rgs\Queues” folders should contain a subfolder for each response group that is defined in the topology, but with nonsensical names reflecting a GUID associated to each one. The Rgs folder is used by the Response Group Service to store common data like Music On Hold audio files (.wav) configured on a Hunt Group.The PDP folder name stands for Policy Decision Point and is used by Call Admission Control (CAC) to distribute policies defining some of the CAC rules.The CPS folder is used by the Call Park Service.Within the child “ AppServerFiles” folder the following three subfolders will exist be default. The “ 1-ApplicationServer-1” folder contains data utilized by Lync applications like Call Park, Response Groups, and Call Admission Control. ![]() In the event that a second site was defined and any pools are deployed in that site then new folders starting with “ 2-“ would be instantiated as well. ![]() If a Director server was later added to the existing site then a new folder would be automatically created as “ 1-WebServices-2” and if a second pool was deployed then that would be called “ 1-WebServices-3” and so on. In the above example the minimum folder configuration would reflect a single Site (ID 1) and Pool instance. These folder names are encapsulated in digits which denote the Site and Pool instance that each folder belongs to. The root of the file share contains three primary folder used to store shared Server Application data, Central Management configuration data, and data used by the various Web Services in Lync. The following Access Control Entries (ACE) are assigned to the root directory of the Lync file share, in addition to any rights which might already assigned to that specific folder or any inherited from a parent folder. Thus if any undesired changes are made to any of the file structure permissions simply re-publish the topology in Lync to repair the configuration. The Lync Front End server itself was used in this environment which is allowed only for Standard Edition servers, Enterprise Edition pool servers can not be collocated with the file share data as it must be hosed on a separate server or servers.Īfter every successful instance of publishing the topology (regardless of what has changed) Lync will refresh the correct permissions (if needed) on the directory structure throughout the file share. Prior to publishing the initial configuration of the Lync Topology the pool or server file share in this example was created at the root of the C: drive on the desired server. Although Lync 2010 uses nearly the same configuration there are a few changes to the folder structure among the various Web Services subfolders. This will insure that the administrator account performing the Lync Server deployment will have sufficient rights to the file share and NTFS Access Control Lists (ACL) so that when publishing the Lync Topology the proper configuration is applied.įor the examples used in this article a single Standard Edition Lync 2013 Front End Server was deployed and the changes were captured to identify the default configuration for Lync. The general guidance is to manually create a new file share on the desired server and then set the share permissions to grant Full Control to the Administrators group. Optional Lync services (like Persistent Chat) can trigger the creation of additional folders in the directory but for the purposes of this article only the default folders for a Standard Edition server are covered. This article outlines the default folder structure and permissions created on the File Share when deploying a Lync 2013 Server Front End server or pool.
0 Comments
Leave a Reply. |