The C-spot

This guide will run through a consolidated Enterprise edition install (without voice gateway integration, whereby all roles will be deployed on virtual machines.

The guide will be split up in different chapters.

The first chapter is all about preparing your Lync 2010 environment.

Prepare the Lync 2010 Enterprise Edition Server Infrastructure

The following sections outline the step to prepare the Lync 2010 Enterprise Edition server infrastructure.

1. Set Up Enterprise Edition Hardware and System Infrastructure

2. Install Prerequisite Software

· Lync Server requires Microsoft .Net Framework 3.5 with SP1.

· Prerequisite software for database servers.

· Message Queuing. Message Queuing (also known as MSMQ) role components and Directory Service Integration should be installed on the Front End Server, the Archiving Server, and the Monitoring Server if you plan to deploy the Lync Server 2010 Archiving or Monitoring Server roles. The Message Queuing components can be found in Server Manager or can be deployed by using servermanagercmd.exe or the Add-WindowsFeature Windows PowerShell cmdlet.

· Configure IIS:

· Install the Remote Server Administration Tools

· Install Silverlight

Silverlight is required to run the Lync Server Control Panel. Although we won’t be using the Control Panel until everything is installed, you can install it now since we’re installing the prerequisite software. Silverlight needs to be installed on the Front-End servers.

· Install and Configure SQL Server

Lync Server 2010 leverages SQL Server for the back-end database and the Archiving and Monitoring databases. SQL Server needs to be installed before we can install Lync Server 2010. For this lab, SQL Server 2008 with Service Pack 1 will be used, and installed on the Back End Server as well as the Monitoring/Archiving Server.

3. DNS records

Lync Server 2010 leverages DNS for various features. Certain DNS records are required as part of the infrastructure preparation. Each server within this lab will already have an A record in DNS. This is attributed to the fact that I am using Active Directory-Integrated DNS, which has Dynamic DNS enabled by default. However, there are additional DNS records that are required before we proceed, including:

4. Grant Administration Permissions

Follow these steps to grant Administration permissions:

1. Ensure you are in the Users Container in Active Directory Users and Computers.

2. In the details pane, locate the CsAdministrator group, right-click on it, and select Properties.

3. On the CsAdministrator Properties page, click on the Members tab.

4. Click Add.

5. On the Select Users, Contacts, Computers, Service Accounts, or Groups dialog box, type Administrator in the Enter the object names to select field, and then click OK.

6. On the CsAdministrator Properties page, click OK.

5. Create the Lync File Share

The user account that we will use to publish the topology must have full control (read/write/modify) on the file share in order for Topology Builder to configure the required permissions. Because I’m going with an Enterprise Edition deployment, the file share cannot be located on the Front End Server. As a result, We prefer to create the file share on the Monitoring/Archiving Server.

Log on to Lync Monitoring/Archiving server

2. Go Start, click Computer, and then click Local Disk (C:).

3. Right-click in the Details Pane, select New, and then select Folder.

4. Name the new folder LyncShare.

5. Right-click on the LyncShare folder, select Properties, click on the Sharing Tab, and then click Advanced Sharing.

6. On the Advanced Sharing dialog box, select the Share this folder option, leave the Share Name field as LyncShare.

/Tim