Transcript Module 04 - Microsoft Lync Server 2010

Microsoft® Lync™ Server 2010
Setup and Deployment
Module 04
Microsoft Corporation
Session Objectives and Takeaways
Session Objectives:
•
Prerequisites: Software and Hardware requirements
•
Changes in Setup and Deployment in this release
•
Overview of End-to-End Setup and Deployment process
•
Central Management Server and Store
•
Planning Tool and Topology Builder Demo
Takeaways:
•
Microsoft® Lync™ Server 2010: what has changed and why
•
Purpose of Planning Tool, Topology Builder, and Setup and how it
integrates
2
Agenda
•
Hardware recommendations and software requirements
•
Changes in setup and deployment
•
Central Management Store and data in
Microsoft Active Directory® Domain Services (AD DS)
•
Setup components and setup flow
•
Prepare AD DS
•
Setup and deploy demo
•
Database setup
•
Other setup tasks
3
Software Requirements
Lync Server 2010
Lync Server 2010 roles
•
•
•
Windows Server® 2008 SP2 x64
Windows Server 2008 R2 x64
Windows PowerShell™ V2
SQL Server® Backend
•
•
•
SQL 2005 (SP3) x64
SQL 2008 (SP1) x64
SQL 2008 R2 x64
Admin Tools, and Core Component AD DS Forest/Domain level
•
•
•
Windows 7 (x64 only)
Windows Vista® SP2 (x64 only)
PowerShell V2
•
•
•
Windows Server 2003
Windows Server 2008
Windows Server 2008 R2
4
Hardware Recommendations
“Frontend” (FE) Spec
“Directors” Spec*
“Backend” (BE) Spec*
CPU - 8 cores (Dual Quad-Core) 2.00
GHz+
CPU - 8 cores (Dual Quad-Core)
2.00 GHz+
CPU - 8 cores (Dual Quad-Core)
2.00 GHz+
Memory - 16 GB*
Memory - 4 GB*
Memory - 32 GB*
Attached storage - 72 GB+ 10K rpm
Attached storage - 72GB+, 10Krpm
Attached storage - 72GB+, 10Krpm+,
multiple spindles
1 Network Adaptor required (2
recommended),1 Gbps+
1 Network Adaptor required (2
recommended),1 Gbps+
1 Network Adaptor required (2
recommended),1 Gbps+
Applicable to other roles (Edge,
Monitoring/Archiving)
* Baseline for 80,000 user pool with 8 FEs and 1 BE
Server Virtualization support including Audio/Video/AppSharing roles
5
Operating System Component Prerequisites
•
PowerShell V2 RTM
•
•
Not supported are PowerShell V1 and PowerShell V2 prerelease versions
Internet Information Services (IIS) rewrite module 2.0 (redistributable)
Selected IIS modules
.NET 3.5 (SP1)
Visual C++ (redistributable)
Microsoft Message Queuing (MSMQ)
•
•
•
•
•
•
required for selected roles if Monitoring and/or Archiving functionality is deployed
Active Directory Domain Services Tools
•
•
optional for AD Prep
SQL 2005 Back Compatibility module
•
required by Install-CsDatabase cmdlet
6
Changes in Setup and Deployment
Lync Server 2010
7
Microsoft Office Communications Server 2007 and 2007 R2
Improvements from previous releases
•
Configuration Data in AD DS, SQL, Windows Management
Instrumentation (WMI)
•
•
Changes to Office Communications Server (OCS) 2007 and
OCS 2007 R2 configuration required changes to the AD DS schema
•
•
•
Required schema changes delayed or blocked deployment
Little or no schema changes moving forward
Edge server with local configuration
•
•
Now centralized with Lync Server 2010
Edge configuration will not get out of sync
Service User Accounts and password expiration
•
Lync Server 2010 services run as Network Service
8
Microsoft Lync Server 2010
Configuration data moved to custom store
•
Introducing Central Management Store
•
•
•
•
Central Management Server
•
•
•
•
XML documents stored in SQL Server® database
Contain all data: topology, policies, configuration
Single master/multiple replica database (DB) per deployment
Runs on one Pool per deployment
Pushes (replicates) changes to configuration to each server
Replication via HTTPS to Edge servers in Perimeter Network
Replica
•
•
Each server has replica copy of master database
Servers continue to operate without access to master database
9
Data Remaining in Active Directory
Lync Server 2010
•
•
Active Directory User extensions
Back Compatibility Schema
•
Office Communications Server 2007 and 2007 R2 schema
extensions
•
Enables interoperability and migration from previous versions
•
Lync Server 2010 will create back compatibility entries for
previous versions
•
Third party application compatibility
•
Will be discontinued in future releases
10
Central Management Store
Impact on setup and deployment
•
•
Topology document contains
•
Pools, server (fully qualified domain name (FQDN)/Internet Protocol (IP)
addresses/Ports)
•
Server roles/components and dependencies
Local Setup uses Topology document to install and activate
•
•
Topology document needs to be authored before any server role can be installed
A SQL DB is required for initial deployment
•
Enterprise Edition Pool requires full SQL instance deployed
•
Standard Edition uses a SQL Express instance which has to be installed in a
separate step
11
Setup Components
What is new?
•
•
•
•
Lync Server 2010 Core (OCSCore.msi)
•
Core component and DLLs
•
PowerShell Provider (PowerShell V2 is required)
Planning Tool
Topology Builder
Setup User Interface (UI) - local Setup
12
Setup Flow
A
D
Domain Joined System
Lync Server 2010
Local Setup
AD Setup
Add/Remove
If first pool is Standard
Edition: SQL instance
is SQL Express
Retrieve
Topology
Install Topology
Builder
Install Components
Author desired
Topology
Publish
Topology
Installs Core
SQL Backend
Activate
Certificate
Maintenance
Certificates
SQL
SQL
SQL
SQL Instance
Central Management
topology and configuration
store
13
Standard Edition Setup
Single Server “All-in-one” deployments
•
•
•
Is the Standard Edition Server being deployed the first
pool in this deployment?
Use “Prepare First Standard Edition Server” from the
Setup main menu to install a SQL Express instance
For subsequent Standard Edition Server pools the above
step is not necessary
14
Setup UI Main Screen
15
Prepare Active Directory – Overview
16
Prepare Active Directory
Powershell cmdlets
•
Schema Prep
•
•
•
Forest Prep
•
•
•
Install-CSADServerSchema –ldf <PathtoLDFfiles>
Current state: Get-CSSchemaState
Enable-CSAdForest
Current state: Get-CSForestState
Domain Prep
•
•
Enable-CSAdDomain
Current state: Get-CSDomainState
17
Demo: Topology Builder
18
Local Setup
Running “Install or Update Lync Server system”
Lync
19
Setting Up Databases
Cmdlet install-CsDatabase and when to use
•
Cmdlet Install-CsDatabase
•
•
•
•
•
Run by Topology Builder
•
•
•
Reads Topology document and configures SQL Stores based on assigned roles (remotely)
Access SQL instance and check for connectivity and permissions
Creates databases and table
Creates database roles and store procedures
Integrated in Topology Builder
Requires admin to have SQL admin
Run as standalone cmdlet
•
•
•
SQL admin may be separate from Lync Server 2010 Admin
More flexibility
Special usages: custom path, SQL cluster
20
Other Setup Tasks
Kerberos Authentication option
•
•
•
•
•
•
IIS as Network Service, service principal name
(SPN) for Pool
Solution using a computer account in AD DS
Computer account password does not fall under
password expiration policies
PowerShell cmdlet available to create, assign, and
manage account name and password
Optional configuration
If not configured, NTLM authentication is used
21
Q&A
22
© 2011 Microsoft Corporation. All rights reserved.
Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft
must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any
information provided after the date of this presentation. This document may contain information related to pre-release software, which may be substantially modified before
its first commercial release. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious,
and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.
23