Here is the summary for Lync Workshop Day 1: Will post the Video Soon in my YouTube Channel and also here.
Server Roles Discussion
Roles and their brief description:
Provides most of Lync Services. There are two types of Front End Server, Standard Edition and Enterprise Edition. To achieve high availability, deploy an enterprise edition front end pool.
AV Conferencing Service / Server
To provide audio video conferencing to Lync users. This server is installed on the front end server but can be separated out onto a standalone server.
Mediation Service / Server
To translate codec between Lync internal clients (RTA–RealTIme Audio) and PSTN clients (G711). This server is installed on the front end server but can be separated out onto a standalone server. You do not need this service if you do not want to use enterprise voice.
To archive mainly – instant messages, meeting contents.
To capture call detail records and quality of experience details.
To “link” the mediation service/server to the PSTN cloud (via E1 or T1 line). Media gateway may not be required if you setup a SIP Trunk to your telco provider. This is only required if there is a need to have Enterprise voice capabilities.
Survivable Branch Appliance/Server
Deployed when there is a need to have high availability for user’s PSTN Calling in branch sites.
Deploying the Director role is not mandatory (although it is recommended to have a director). Directors are generally more important in environments with multiple front end pools. Directors only directs/connects to proper front end pool where the user profile resides; in a multi front end pool server scenario.
To allow connections from internet. It is recommended to deploy this even if you have VPN. This is because VPN Lync connections have double layer of encryption which can have the possibility of affecting call quality.
To provide HTTPs services to Lync clients on internet. To provide Lync mobility services to Lync clients on mobile phones.
Stores bulk to information on Lync, user’s contact list, central management store etc…You will typically also host your file shares on the SQL servers, especially when the SQL server is clustered for high availability.
File Stores contain data such as meeting content metadata, meeting compliance logs, update logs for device updates, and audio files for the Response Group, Call Park, and Announcement applications.
- Application Server files. (CPS, RDP and Rgs)
- Archiving Server.(DataConf, MeetingConf)
- CMS File Store. (Including all all Lync server and roles)
- Web Services. (ABFiles, CollabContent, CollabMetadata, DeviceUpdateLogs, DeviceUpdateStore, LMStaticData, MeetingComplianceData, MeetingContent, MeetingContent, MeetingFiles, MeetingMetaData and WebAuthStore.)
Active Directory Requirements
Windows Server 2003 native mode active directory functional level is required for the forest and domains.
Lync User Model
Capacity Planning Using the User Models
Lync client impact on Exchange
SQL Database Growth Rate
Recommended Hardware Config
Virtualization Host and Guest Hardware Config
Can be used to determine how to scale down:
Refer to documents from other hardware vendors on Lync Virtualization:
What are some of the virtualization considerations?
- Supported VMHost:
- VMWare ESX 4.0
- Hyper V 2008 R2
- Users that can be supported is approximately halved (50%)
- Do not mix VM and physical servers for same server roles
- Do not allow VM Host to be the single point of failure
- Virtualization is not supported for Large Meeting Pools (1000 users in a meeting):
- Follow best practices when for deploying a Virtualized environment:
- When considering Client Virtualization review the document, not all client virtualization products are supported.